Curriculo ATS MCP Server

The Curriculo ATS MCP server is a remote, hosted server — nothing to install or run locally. Point any MCP client at the endpoint, authenticate once, and the client gains a set of tools that read and act on your hiring data in real time.

Quickstart #

Connect in under a minute. Use this endpoint everywhere:

The fastest path is Claude’s one-click connector flow:

1. Open Claude → Settings → Connectors.
2. Click Add custom connector and paste the server URL above.
3. Complete the OAuth sign-in when prompted — Claude connects to your organization.
4. Start a chat and ask, e.g. “What’s sitting in each stage of my open roles?”

Connect a client #

The server speaks Streamable HTTP and supports both interactive OAuth and a Personal Access Token via an Authorization: Bearer header. Pick your client below.

# Custom connector URL
https://mcp.curriculo.me/mcp

claude mcp add --transport http curriculo https://mcp.curriculo.me/mcp

claude mcp add --transport http curriculo https://mcp.curriculo.me/mcp \
  --header "Authorization: Bearer YOUR_CURRICULO_PAT"

{
  "mcpServers": {
    "curriculo": {
      "url": "https://mcp.curriculo.me/mcp"
    }
  }
}

{
  "mcpServers": {
    "curriculo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.curriculo.me/mcp"]
    }
  }
}

"args": ["-y", "mcp-remote", "https://mcp.curriculo.me/mcp",
        "--header", "Authorization: Bearer YOUR_CURRICULO_PAT"]

Authentication #

Two ways to authenticate. Both resolve to a user in one organization with scoped permissions.

OAuth 2.1 (recommended)

Interactive clients (Claude, Cursor) use OAuth with dynamic client registration. You sign in to Curriculo, approve the connection, and the client stores a short-lived token it refreshes automatically. No secrets to copy or rotate by hand.

Personal Access Token (PAT)

For CLI or headless setups, generate a token in the ATS and send it as a Bearer header:

1. Sign in at ats.curriculo.me.
2. Go to Settings → API & Integrations → Personal Access Tokens.
3. Create a token, choose its scopes, and copy it (shown once).
4. Pass it as Authorization: Bearer <token> as shown in the setup tabs.

Scopes

Tokens carry one or both scopes. Grant only what you need:

• ats:read  List and read jobs, applicants, inbox, interviews, analytics.
• ats:write  Create and change data: move stages, send email, schedule interviews, update jobs.

Tools reference #

25 tools across six groups. read tools never change data; write tools create or modify records and may trigger emails, calendar events, or automations.

Example prompts #

Once connected, ask in plain language. The client picks the right tools.

• “Show me what’s sitting in each stage of my open roles, and flag anything stalled.”
• “Find senior React engineers with team-lead experience and summarize the top five.”
• “Move Priya to Second Interview and draft a reply asking for her availability next week.”
• “Schedule a 45-minute video interview with this candidate on Thursday 2pm ET and add a Google Meet link.”
• “How did applicant volume change vs last month, and which job is converting best?”

FAQ & troubleshooting #

Security #

• Scoped access. Every token is bound to one user and organization and carries explicit ats:read / ats:write scopes.
• Least privilege. Grant the narrowest scope that does the job; prefer read-only tokens for analysis.
• Revoke anytime. Personal Access Tokens can be revoked in Settings → API & Integrations; OAuth connections can be removed from your client’s connector settings.
• Transport security. All traffic is HTTPS over Streamable HTTP. Never paste a token into untrusted clients or share it in plain text.