MCP server

Tools for Claude, and for any client that speaks HTTP MCP.

Streamable HTTP at https://mcp.recruitmcp.com/mcp. This process also accepts the protocol at /mcp and /api/mcp. Spend and sends stay behind confirm.

Clients with a setup page

Claude Desktop

mcp-remote, with the API key in the Authorization header.

Claude Desktop

claude.ai

Custom connector. OAuth discovery, then a one-hour access token.

claude.ai

Claude Code

claude mcp add against the HTTP endpoint.

Claude Code

What the server exposes

Toolsets

sourcing and outreach are on by default. Add advanced, or ask for all, with ?toolsets= on the URL. There is no scoring tool. Candidates are facts.

Confirm

start_search without confirm returns the summary and the estimate. Call it again with confirm=true to run. A repeated confirmed call replays and does not charge twice.

Claude Code
claude mcp add --transport http recruitmcp https://mcp.recruitmcp.com/mcp --header "Authorization: Bearer $RECRUITMCP_KEY"
start_search
start_search({
  job_description: "Senior backend engineer in Ghent, Belgium. Go, 5+ years.",
  target: 40
})

{
  "requires_confirm": true,
  "cost": {
    "credits": 0
  },
  "target": 40,
  "summary": "Backend Engineer, Senior Backend Engineer (then 2 adjacent titles); within 30 km of Ghent, Belgium, then the rest of the country; 5–10 years of experience first; profiles mentioning Go first; excluding people already seen. Target 40 candidates across 4 tiers (10 queries). Estimated 1–120 credits; balance 1250.",
  "estimate": {
    "credits_min": 1,
    "credits_max": 120,
    "requires_confirm": true
  },
  "next_step": "Show the summary and estimate. To run it, call start_search with this search_id and confirm=true."
}

Tested examples · MCP overview · REST API