Recruitee MCP by usefulapi is a remote MCP server that gives an AI agent 22 tools, among them recruitee_add_candidate_note, recruitee_add_candidate_tags, recruitee_assign_candidate_to_offer. It answers at https://recruitee.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
Search Recruitee candidates, jobs, pipelines and interviews, and add notes, tags and tasks.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
recruitee_add_candidate_note | WRITE: add a note to a candidate's profile, visible to the team. Recruitee: POST /c/{company_id}/candidates/{candidate_id}/notes. Inputs: candidate_id, body |
recruitee_add_candidate_tags | WRITE: add one or more tags to a candidate (existing tags are reused by name; new names create new tags). Recruitee: POST /c/{company_id}/candidates/{candidate_id}/tags. Inputs: candidate_id, tags |
recruitee_assign_candidate_to_offer | WRITE: put an existing candidate on a job (or talent pool) — creates a placement in the pipeline's first stage. Pass exactly one of offer_id or talent_pool_id. Recruitee: POST /c/{company_id}/placements. Inputs: candidate_id, offer_id, talent_pool_id |
recruitee_create_candidate | WRITE: add a candidate manually (as if a recruiter added them in the app — no auto-confirmation email is sent), optionally assigning them straight to one or more jobs in the job's default stage. Recruitee: POST /c/{company_id}/candidates. Inputs: name, emails, phones, social_links, links, cover_letter |
recruitee_create_task | WRITE: create a recruiting task, optionally about a candidate, assigned to team members (admin ids from recruitee_list_team_members), with an optional due date. Recruitee: POST /c/{company_id}/tasks. Inputs: title, description, candidate_id, admin_ids, due_date, timezone |
recruitee_get_candidate | Fetch one candidate's full profile: contact details, sources, tags, cover letter, CV URL, custom fields, ratings, and `placements` — one per job they are on, each with its placement id and current stage. The placement id is what recruitee_m Inputs: candidate_id |
recruitee_get_current_user | Fetch the Recruitee user the API token belongs to — name, email, role, role abilities and company id. A cheap way to confirm the token and company id are right. Recruitee: GET /c/{company_id}/admin. |
recruitee_get_offer | Fetch one job or talent pool by id with its full details: description, requirements, location, salary, employment type, candidate counters and pipeline_template_id. Recruitee: GET /c/{company_id}/offers/{id}. Inputs: offer_id |
recruitee_get_pipeline_template | Fetch a pipeline template with its ordered stages (id, name, group, category). A job's `pipeline_template_id` (from recruitee_list_offers / recruitee_get_offer) names its pipeline; the stage ids here are what recruitee_move_candidate_stage Inputs: pipeline_template_id |
recruitee_list_candidate_notes | List the notes on a candidate's profile, with replies, author admin_id and visibility. Recruitee: GET /c/{company_id}/candidates/{candidate_id}/notes. Inputs: candidate_id |
recruitee_list_candidates | List candidates, newest first, optionally filtered by job, search, qualification, ids or creation date. Default 25 per page. detail auto returns whole records where they fit; if one record or page metadata is too large, explicitly marked su Inputs: offer_id, query, qualified, disqualified, ids, created_after |
recruitee_list_departments | List the company's departments with their ids and job counts. Recruitee: GET /c/{company_id}/departments. |
recruitee_list_disqualify_reasons | List the company's configured disqualification reasons (id, name, position). Useful for reading why candidates were disqualified. Recruitee: GET /c/{company_id}/disqualify_reasons. |
recruitee_list_evaluations | List interview results — evaluations (rating + note) and questionnaire scorecards — optionally for one candidate or by selected reviewers. Recruitee: GET /c/{company_id}/interview/results. Inputs: candidate_id, kind, scope, admin_ids, limit, page |
recruitee_list_interview_events | List scheduled interview events (candidate_id, offer_id, stage_id, start time, duration, location, attendees). Defaults to upcoming events for the whole company; narrow by candidate, date range or interviewer. Recruitee: GET /c/{company_id} Inputs: status, scope, candidate_id, admin_ids, start_date, end_date |
recruitee_list_offers | List the company's jobs (Recruitee calls them offers) with id, title, status, slug, department_id, recruiter_id, hiring_manager_id and pipeline_template_id. Filter by status, department, location, recruiter, hiring manager, tag and more; ad Inputs: statuses, offer_ids, department_ids, location_ids, recruiter_ids, hiring_manager_ids |
recruitee_list_tags | List the company's candidate tags with ids and usage counts. Tag ids are used in recruitee_search_candidates filters. Recruitee: GET /c/{company_id}/tags. Inputs: query, sort_by, sort_order |
recruitee_list_tasks | List recruiting tasks (title, description, due date, completed, candidate_id). With candidate_id, lists that candidate's tasks (Recruitee: GET /c/{company_id}/candidates/{candidate_id}/tasks — only `status` applies). Otherwise lists company Inputs: candidate_id, status, scope, admin_ids, sort_by, sort_order |
recruitee_list_team_members | List the company's team members (memberships): admin_id, role, whether they are a recruiter or hiring manager, and the jobs they can access. Use admin_id values for task assignees and filters. User names/emails are in the `references` array Inputs: query, role_id, sort_by, sort_order, limit, page |
recruitee_move_candidate_stage | WRITE: move a candidate to another stage of a job's pipeline. Takes the PLACEMENT id (from recruitee_get_candidate → placements[].id, one per job) and the destination stage id (from recruitee_get_pipeline_template). Moving to a 'hired' stag Inputs: placement_id, stage_id, work_location_id |
recruitee_search_candidates | Search the company's candidates with Recruitee's candidate search (the same engine as the app's filters). `query` is a free-text search across name, emails, phones, tags, sources, job assignments, current stage, cover letter and CV content. Inputs: query, filters, sort_by, limit, page |
recruitee_update_candidate | WRITE: update a candidate's name or contact details. Only the fields you pass change; list fields (emails, phones, links) REPLACE the existing list, so pass the full list you want. Recruitee: PATCH /c/{company_id}/candidates/{id}. Inputs: candidate_id, name, emails, phones, social_links, links |
Every block below points at https://recruitee.usefulapi.io/mcp. Pick your client and copy.
claude mcp add --transport http recruitee-mcp-by-usefulapi https://recruitee.usefulapi.io/mcp
{
"mcpServers": {
"recruitee-mcp-by-usefulapi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://recruitee.usefulapi.io/mcp"]
}
}
}{
"mcpServers": {
"recruitee-mcp-by-usefulapi": {
"url": "https://recruitee.usefulapi.io/mcp"
}
}
}{
"servers": {
"recruitee-mcp-by-usefulapi": {
"type": "http",
"url": "https://recruitee.usefulapi.io/mcp"
}
}
}{
"context_servers": {
"recruitee-mcp-by-usefulapi": {
"url": "https://recruitee.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"recruitee-mcp-by-usefulapi": {
"serverUrl": "https://recruitee.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"recruitee-mcp-by-usefulapi": {
"url": "https://recruitee.usefulapi.io/mcp"
}
}
}name: Recruitee MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
- name: Recruitee MCP by usefulapi
type: streamable-http
url: https://recruitee.usefulapi.io/mcp{
"mcpServers": {
"recruitee-mcp-by-usefulapi": {
"httpUrl": "https://recruitee.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"recruitee-mcp-by-usefulapi": {
"type": "http",
"url": "https://recruitee.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"recruitee-mcp-by-usefulapi": {
"url": "https://recruitee.usefulapi.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Frecruitee.usefulapi.io%2Fmcp&type=streamable_http&id=recruitee-mcp-by-usefulapi&name=Recruitee%20MCP%20by%20usefulapi
It answered our last check on 15 November 2026 in 181 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by usefulapi.io and served from recruitee.usefulapi.io, the vendor's own domain: https://recruitee.usefulapi.io/mcp.
22, as returned by the server's own tools/list on 18 November 2026: recruitee_add_candidate_note, recruitee_add_candidate_tags, recruitee_assign_candidate_to_offer, recruitee_create_candidate, recruitee_create_task, recruitee_get_candidate, recruitee_get_current_user, recruitee_get_offer, and 14 more.
It answered our last check on 15 November 2026 in 181 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://recruitee.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.usefulapi. Endpoint host: recruitee.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:recruitee.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.