跳过安装。2 分钟内即可运行。
在 cloud.anythingmcp.com 开始免费试用，一键添加 Recruitee，然后将你的 AI 客户端（Claude、ChatGPT、Copilot 或 Cursor）指向生成的 MCP 端点。无需 Docker，无需 git clone，无需任何工程经验。
摘要
Recruitee（Tellent Recruitee）招聘管理：职位和人才库、支持全文搜索的候选人、招聘流程和阶段、placement、备注、标签、部门、地点、面试和评估、任务以及动态。它还能在阶段之间移动候选人，并创建和发布职位。通过个人 API 令牌连接 Recruitee ATS API。
试试这样问
Recruitee 的示例提示
点击任意提示即可复制，然后粘贴到 Claude、ChatGPT、Cursor、Gemini、Copilot 或 OpenClaw 中，在该连接器上运行。
Claude 是 AI，可能会出错。请核对回答。
💡 无需安装? 直接使用 cloud.anythingmcp.com。 登录、点击 Connectors → Recruitee、粘贴凭证、生成 MCP API key，即可完成。无 Docker、无
git clone、无本地服务器。
Recruitee + Cursor
Recruitee（Tellent Recruitee）招聘管理：职位和人才库、支持全文搜索的候选人、招聘流程和阶段、placement、备注、标签、部门、地点、面试和评估、任务以及动态。它还能在阶段之间移动候选人，并创建和发布职位。通过个人 API 令牌连接 Recruitee ATS API。
前提条件
完整的设置说明已内置在连接器中 (在 store 中选择连接器时可见)。所需环境变量:
RECRUITEE_COMPANY_ID, RECRUITEE_API_TOKEN
步骤 1 — 获取凭证
设置大约需要 3 分钟。
- 在 Recruitee 中打开 Settings > Apps and plugins > Personal API tokens（
https://app.recruitee.com/#/settings/api_tokens），点击 Add new token，填写标签并确认密码。把令牌复制到RECRUITEE_API_TOKEN；令牌无法再次显示。 - 把同一页面显示的 company ID（一个数字）复制到
RECRUITEE_COMPANY_ID。也可以使用公司的子域名。 - 安装连接器：
recruitee_get_current_admin用于安装检查。
令牌以你的身份、按你的角色、只在这一家公司内操作；其他公司需要各自的令牌。Recruitee 无法缩小令牌的权限范围，所以请用角色与 AI 要做的事情相符的用户来创建。
个人数据：候选人是求职者，带有简历、联系方式、评估，有时还有出生日期或国籍。只请求任务需要的内容，遵守公司的 GDPR 设置，不要无故把候选人数据复制到其他工具。
Recruitee 的术语：职位叫 offer（kind 为 job；人才库是 kind 为 talent_pool 的 offer）。候选人在某个职位中叫 placement，记录该职位下的阶段和淘汰信息。团队成员叫 admins。
读取内容：
- 团队：
recruitee_get_current_admin和recruitee_list_admins（任务负责人和筛选所需的 ID）。 - 职位：
recruitee_list_offers（按 published 等statuses、类型、部门、地点、标签、招聘专员或用人经理筛选）、recruitee_get_offer（描述、要求、招聘团队以及带 ID 的流程阶段）和recruitee_list_offer_notes。 - 候选人：
recruitee_list_candidates（简单筛选）、recruitee_search_candidates（用filters_json全文搜索）、recruitee_get_candidate（联系方式、简历和求职信链接、来源、标签、自定义字段、评分、placement 和问题回答）、recruitee_list_candidate_notes、recruitee_list_candidate_tasks和recruitee_list_candidate_activities。全公司动态：recruitee_list_activities。 - 职位的招聘流程：
recruitee_list_placements（谁在哪个阶段）、recruitee_list_pipeline_templates、recruitee_get_pipeline_template和recruitee_list_disqualify_reasons。 - 参考列表：
recruitee_list_departments、recruitee_get_department、recruitee_list_locations、recruitee_get_location、recruitee_list_tags和recruitee_list_sources。 - 面试：
recruitee_list_interview_events（默认为即将进行的）、recruitee_get_interview_event和recruitee_list_interview_results（评估和评分卡）。任务：recruitee_list_tasks。
写入内容：
- 候选人：
recruitee_create_candidate（可同时申请职位；会解析remote_cv_url）、recruitee_update_candidate、recruitee_add_candidate_tags（不存在的标签名会被创建）、recruitee_remove_candidate_tags、recruitee_add_candidate_field（例如技能、语言或国籍）和recruitee_create_candidate_note（招聘团队可见，候选人不可见）。 - 招聘流程：
recruitee_assign_candidate把候选人放入某个职位（第一阶段）或人才库；recruitee_change_stage把 placement 移到另一个阶段（placement ID 来自候选人，阶段 ID 来自recruitee_get_offer；录用阶段可能需要hired_at、work_location_id，使用招聘需求时还需要opening_id）；带原因的recruitee_disqualify_candidate和recruitee_requalify_candidate可以互相撤销。 - 职位：
recruitee_create_offer创建草稿，recruitee_update_offer修改字段，recruitee_publish_offer发布到招聘网站和为其设置的招聘平台，recruitee_unpublish_offer下线职位并保留候选人，recruitee_close_offer停止接收新申请。 - 任务：
recruitee_create_task和recruitee_complete_task（把completed设为 false 可重新打开任务）。
自动化：在职位上创建候选人、用 run_actions true 变更阶段或淘汰候选人，都可能触发公司在 Recruitee 中配置的邮件和操作，候选人可能会因此收到消息。对大量候选人执行前，AI 会先说明这一点。
安装时关闭：recruitee_delete_candidate（删除候选人及其全部数据）和 recruitee_remove_placement（把候选人连同该 placement 的阶段历史一起移出职位）。它们无法撤销；团队需要时由工作区管理员开启。淘汰是把候选人移出职位的可恢复方式。
搜索筛选：recruitee_search_candidates 的 filters_json 是字符串形式的 JSON 数组，例如 [{"field":"all","query":"java"},{"filter":"tags","id":{"in":[12]}},{"field":"created_at","gte":"2026-10-01"}]。状态和来源：{"field":"status","in":["qualified"]}；阶段：{"filter":"stages","name":{"in":[...]}}。
数据格式：ID 为整数；日期和时间为 UTC 的 ISO 8601（2026-10-19T11:02:32Z）。候选人的 placements 为每个职位列出一条记录，含 offer_id、stage_id 和 disqualify_reason；变更阶段和资格时使用 placement 的 id。adminapp_url 链接到 Recruitee 中的候选人。
分页：recruitee_list_candidates 用 limit（最多 1000）和 offset 分页；职位、搜索、地点、动态、面试事件和任务用 limit 和 page（从 1 开始）分页。当某页返回的条数少于 limit 时，AI 停止翻页。
常见错误：401 invalid_token 表示令牌错误、已吊销或属于其他公司；403 表示角色缺少相应权限；404 表示 company ID 或记录 ID 错误；422 表示校验错误，响应体中会指出字段。
连接器不会直接给候选人发邮件，不会安排面试，也不会撰写评估。
步骤 2 — 安装 adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
步骤 3 — 在 Cursor 中添加连接器
你的服务器 URL： 在 AnythingMCP 中打开 MCP Servers → 此连接器所在的服务器，复制它的 URL（
https://cloud.anythingmcp.com/mcp/…）。本指南中出现YOUR_SERVER_ID的地方都用它替换。
Cursor 从 ~/.cursor/mcp.json 读取 MCP 服务器。添加以下条目：
{
"mcpServers": {
"anythingmcp": {
"url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- 在 AnythingMCP 的 MCP Servers → 你的服务器 → API keys 中创建 MCP API 密钥，并用它替换
YOUR_MCP_API_KEY。 - 保存文件并重启 Cursor。
- 打开 Cursor → Settings → MCP，确认
anythingmcp已列出并处于已连接状态。 - 开始对话，智能体现在可以调用
Recruitee的工具。
可用工具
| Tool | What it does |
|---|---|
recruitee_get_current_admin | The team member (admin) the token belongs to: id, name, email, role and time zone |
recruitee_list_admins | Team members (admins) of the company with id, name, email and role; ids are used for task assignees, interview participants and followers |
recruitee_list_offers | Jobs and talent pools (Recruitee calls them offers): id, title, status, kind, department, locations, recruiter, candidate counts, pipeline… |
recruitee_get_offer | One job or talent pool by id with description, requirements, locations, department, hiring team and its pipeline stages (ids used to move… |
recruitee_list_offer_notes | Internal team notes on a job (offer), with author, text and time of each note |
recruitee_list_candidates | List candidates with name, emails, phones, source, tags, rating, placements (job, stage, disqualified) and creation date |
recruitee_search_candidates | Full candidate search across the database with filters on text, tags, sources, stages, ratings, dates, custom fields, education and… |
recruitee_get_candidate | One candidate by id: contact details, CV and cover letter links, sources, tags, custom fields, ratings, placements (job, stage… |
recruitee_list_candidate_notes | Team notes on a candidate with author, text, pinned flag and time of each note |
recruitee_list_candidate_activities | Activity history of a candidate: applications, stage moves, emails, notes, evaluations and events, newest first |
recruitee_list_activities | Company-wide activity feed (applications, stage changes, notes, emails, evaluations), filterable by candidates, offers, event names and… |
recruitee_list_placements | Candidates in a job's pipeline (placements): placement id, candidate, stage, disqualification, rating, upcoming event and overdue date |
recruitee_list_pipeline_templates | Pipeline templates with their stages (id, name, category such as apply, interview, offer, hire) |
recruitee_get_pipeline_template | One pipeline template with all its stages in order (stage id, name and category) |
recruitee_list_disqualify_reasons | Reasons a candidate can be disqualified with (id and name), for recruitee_disqualify_candidate |
recruitee_list_departments | Departments of the company with id, name and offer counts, to filter or create jobs |
recruitee_get_department | One department by id with its name and translations, to resolve the department_id of a job |
recruitee_list_locations | Job locations with id, name, address, city, country and active flag |
recruitee_get_location | One job location by id with its full address, translations and active flag |
recruitee_list_tags | Candidate tags of the company with id, name and how many candidates carry them |
recruitee_list_sources | Candidate sources (where applicants came from) with id and name |
recruitee_list_interview_events | Scheduled interviews and other events: candidate, job, participants, start and end, location or video link, status |
recruitee_get_interview_event | One interview event with participants, times, location and the candidate |
recruitee_list_interview_results | Evaluations and scorecards written about candidates, with reviewer, rating and answers |
recruitee_list_tasks | Recruiting tasks of the company: title, description, candidate, assignees, due date and completion |
recruitee_list_candidate_tasks | Tasks linked to one candidate with assignees, due date and completion |
recruitee_create_candidate | Add a candidate, optionally applied to jobs |
recruitee_update_candidate | Change a candidate's profile: name, emails, phones, links, cover letter or sources |
recruitee_delete_candidate | Delete a candidate with all their data |
recruitee_add_candidate_tags | Add tags to a candidate by name; tag names that do not exist yet are created |
recruitee_remove_candidate_tags | Remove tags from a candidate (the tags stay in the company list) |
recruitee_add_candidate_field | Add a profile field to a candidate, e.g. skills, languages, nationality or a single-line value |
recruitee_create_candidate_note | Write a team note on a candidate's profile (visible to the hiring team, not to the candidate) |
recruitee_assign_candidate | Put an existing candidate into a job's pipeline (first stage) or a talent pool |
recruitee_change_stage | Move a candidate's placement to another pipeline stage |
recruitee_disqualify_candidate | Disqualify a candidate in one job (placement) with a reason |
recruitee_requalify_candidate | Requalify a disqualified candidate in one job (placement), back into the pipeline |
recruitee_remove_placement | Remove a candidate from a job's pipeline, with that placement's stage history |
recruitee_create_offer | Create a job (or talent pool) as a draft; publish it with recruitee_publish_offer |
recruitee_update_offer | Change a job's fields, e.g. title, description, requirements, department, locations or salary |
recruitee_publish_offer | Publish a job on the careers site and job boards set up for it |
recruitee_unpublish_offer | Unpublish a job: it leaves the careers site but keeps its candidates |
recruitee_close_offer | Close a job: no new applications, candidates stay in the pipeline |
recruitee_create_task | Create a recruiting task for team members, optionally linked to a candidate and with a due date |
recruitee_complete_task | Mark a task as completed, or reopen it with completed false |
示例提示
- “本周哪些候选人申请了 Senior Backend Developer 职位，他们各在哪个阶段？”
- “查找 10 月 1 日之后申请、带有 java 标签的候选人。”
- “明天安排了哪些面试？附上候选人、职位和参与者。”
- “把 Laura Rossi 移到 Product Designer 职位的 Interview 阶段，并添加一条备注说电话初筛很顺利。”
- “在 Support 部门创建一个地点为柏林的 Customer Support Specialist 职位草稿。”
FAQ
Cursor 免费套餐支持自定义 MCP 服务器吗？ 支持，Hobby、Pro 和 Business 套餐均可使用 MCP。
下一步
这份指南对你有帮助吗?