Claude Desktop

API key via a custom connector header, or mcp-remote in the Desktop config.

Claude Desktop uses an API key. Two setups talk to the same endpoint. The server accepts Authorization: Bearer rmcp_live_… and rejects a token with no Bearer prefix.

Custom connector

Settings → Connectors → Add custom connector.

• URL: https://mcp.recruitmcp.com/mcp. The same process also serves https://recruitmcp.com/mcp and https://recruitmcp.com/api/mcp.
• Authentication: no sign-in.
• Request header name: Authorization
• Request header value: Bearer rmcp_live_… (the word Bearer, a space, then the key)

Add ?toolsets=all to the URL for the advanced tools. The default is sourcing and outreach.

This connection is brokered by your Claude account. It does not use your laptop's network.

Config file

Paste this into claude_desktop_config.json. On macOS that file is ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it is %APPDATA%\Claude\claude_desktop_config.json.

{
  "mcpServers": {
    "recruitmcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.recruitmcp.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer rmcp_live_..."
      }
    }
  }
}

Replace rmcp_live_.... The key sits in AUTH_HEADER so the space after Bearer is not split on Windows. Restart Desktop.

mcp-remote is a local bridge from Desktop's stdio process to the HTTP endpoint. For http://127.0.0.1:43123/mcp, put that URL in the same args position and add --allow-http before --header.

Confirm the process can list tools with the MCP check.

API reference