Curriculo ATS MCP server

Connect your Curriculo ATS to Claude, Cursor and any MCP client that speaks Streamable HTTP, or to ChatGPT through a Custom GPT. Ask in plain language to review candidates, move pipelines, reply to applicants, schedule interviews and pull analytics. Your AI client does the work directly in your ATS.

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

A different product from the public API, with different authentication. MCP talks to Curriculo ATS and the user signs in. A public API key_ does not reach these tools, and the public API does not reach your ATS.

What is the Curriculo ATS MCP server?

The Curriculo ATS MCP server is a hosted endpoint, https://mcp.curriculo.me/mcp, that lets Claude, ChatGPT, Cursor and other MCP clients read and act on your Curriculo ATS. You sign in once with OAuth or a personal access token, then ask in plain language to review candidates, move stages, reply to applicants or schedule interviews.

Quickstart

Use this endpoint everywhere:

https://mcp.curriculo.me/mcp

The fastest path is Claude's connector flow:

1. Open Claude, then Settings, then 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, for example, "What's sitting in each stage of my open roles?"

New here? Follow the step-by-step tutorial: run your ATS in Claude, with screenshots that walk through connecting, ranking candidates by AI fit and scheduling interviews from a chat.

Connect a client

Any client that speaks Streamable HTTP works. Authenticate with OAuth 2.1 or with a personal access token sent in an Authorization: Bearer header. Setup for common clients follows.

Claude

In Claude (web or desktop), go to Settings, Connectors, Add custom connector, then enter:

https://mcp.curriculo.me/mcp

Click Add, complete the OAuth sign-in, then open the connector to enable the specific tools you want Claude to use.

Claude Code

Add the server with a single command. OAuth opens in your browser via /mcp:

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

Or pass a personal access token directly with a header:

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

Run /mcp inside Claude Code to check status or trigger the OAuth login.

Cursor

Open Cursor Settings, Tools & MCP, New MCP Server and add this to mcp.json:

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

Cursor shows Needs login. Click it to run the OAuth consent flow, and the tools turn green.

VS Code and other clients

Any client without native remote MCP support can use the mcp-remote bridge:

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

To authenticate headlessly, append a header argument:

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

ChatGPT (Custom GPT Actions)

ChatGPT connects through a Custom GPT with Actions, using a REST surface that mirrors the 25 MCP tools.

1. In ChatGPT, create a GPT and open Configure, then Actions, then Create new action.

2. Import the schema from this URL:

   https://mcp.curriculo.me/api/v2/mcp/openapi.json

3. Set Authentication to OAuth, with these values from the schema:

   Setting	Value
   Authorization URL	https://mcp.curriculo.me/api/v2/ats/oauth/authorize
   Token URL	https://mcp.curriculo.me/api/v2/ats/oauth/token
   Scope	ats:read ats:write (or only ats:read)

4. Save, then sign in to Curriculo ATS and approve access when the GPT first calls an action.

Authentication

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

OAuth 2.1 (recommended)

Interactive clients (Claude, Cursor, ChatGPT) use OAuth 2.1 with the authorization code flow. Dynamic client registration is supported, PKCE (S256) is required for public clients, and redirect URIs must be https. You sign in to Curriculo ATS, approve the connection, and the client stores a short-lived token it refreshes automatically. There are no secrets to copy or rotate by hand. Server metadata is published at https://mcp.curriculo.me/.well-known/oauth-authorization-server.

Personal access token

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. It is shown once.
4. Pass it as Authorization: Bearer <token>, as shown in the setup steps above.

Scopes

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

Not sure who a token is acting as? Call the whoami tool. It returns the authenticated user, organization, auth method and granted scopes.

Tools reference

Twenty-five tools. The access type tells you the risk:

• Read only looks.
• Write changes ATS data.
• Write+ changes data and reaches outside: an email leaves, an invite is sent, or an AI job starts.

Seventeen of the twenty-five tools are read-only. The six Write+ tools have outside consequences, and the assistant confirms intent before using them. No tool deletes anything.

Jobs

Applicants

Inbox and email

Interviews

Analytics

Automations and imports

Account

Email tools send from Curriculo's sending mailbox, so they work without a connected mailbox. Interview scheduling also works without a calendar: it still saves the interview and reports that invites were not sent.

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 at 2pm ET and add a Google Meet link."
• "How did applicant volume change vs last month, and which job is converting best?"

Write tools have real side effects: sending email, changing pipelines, closing jobs. Keep tool approvals on for write actions until you trust a workflow, and grant only ats:read if you just want analysis.

Security

• Scoped access. Every token is bound to one user and organization and carries explicit ats:read or ats:write scopes. Everything the assistant sees is limited to your own organization.
• 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.

Part of the Curriculo ATS MCP hub, which links the setup guides, the tools reference and the connector docs.

Next steps

• Slack through MCP: use these tools from Slack.
• Email Agent setup guide: connect your hiring inbox and calendar.
• Curriculo ATS MCP hub: setup guides and the connector docs.