Skip to content

Use Curriculo ATS in Slack through MCP

On this page

Curriculo ATS does not have its own Slack app. You reach it from Slack through the Curriculo ATS MCP server: an AI assistant that runs in your Slack workspace and supports remote MCP connectors can call the same 25 tools that Claude, ChatGPT and Cursor use.

How do I use Curriculo ATS in Slack?

Add the Curriculo ATS MCP server, https://mcp.curriculo.me/mcp, as a connector in an assistant that works inside Slack and supports remote MCP servers over Streamable HTTP. Sign in with OAuth or a personal access token, then ask that assistant in a Slack message or thread to review candidates, move stages or schedule interviews.

What you need

  • A Curriculo ATS organization and a user who can sign in to it.
  • An assistant available in your Slack workspace that can add a custom remote MCP connector.
  • Permission in that assistant to add connectors. On a managed workspace this is usually an admin.

Connect

  1. In the assistant's connector or integration settings, add a custom MCP server.

  2. Enter the server URL:

    https://mcp.curriculo.me/mcp
  3. Complete the OAuth sign-in when prompted, or paste a personal access token as Authorization: Bearer <token> if the assistant asks for a header.

  4. Grant ats:read for read-only use, or ats:read and ats:write to let it act. See Scopes.

What you can ask

Everything the MCP tools cover, from a Slack message:

  • "Which applicants for the backend role scored highest this week?"
  • "Move Ada to the interview stage and draft a reply to her."
  • "What is sitting in each stage of my open roles?"

The full list is in the tools reference.

What it does not do

  • No automatic Slack notifications. Curriculo ATS does not post to Slack channels on its own. The assistant answers when someone asks it.
  • No separate Slack permissions. The assistant acts as the Curriculo ATS user who signed in, limited to the scopes on that token.

Anyone who can talk to the assistant in a channel may be able to use its connected tools. Prefer a read-only token in shared channels, and check how your assistant shares connectors between users.

Next steps

Was this page helpful?

Updated