Kula MCP connector

Last updated: September 22, 2026

The Kula MCP connector lets you connect Claude directly to your Kula account, so you can search candidates, check applications, review scorecards, and move candidates through stages by asking Claude — without switching to Kula. This setup takes about a minute: paste a URL into Claude and sign in with Kula. No package installs, no config files to edit.

Who can do this: Any Kula user can connect their own account — the connector only shows you what your existing Kula permissions already allow. On a Claude Team or Enterprise workspace, the workspace owner has to add the connector once for the organization before anyone else on that workspace can connect.

Where to find it: In Claude (web or desktop), add Kula as a custom connector and sign in with your Kula account.

Setting up the connector

  1. In Claude, go to Settings → Connectors.

  2. Click Add custom connector (Kula isn't in Claude's built-in connector directory yet, so it's added this way rather than picked from a list).

  3. Paste in the Kula MCP connector URL (get the exact URL from your Kula contact — not yet published at the time of writing).

    Here is the URL: 

    https://mcp.kula.ai/mcp

  4. Sign in with your Kula account when prompted.

  5. That's it — Claude can now use your Kula data, scoped to whatever your Kula permissions already allow.

On a Claude Team or Enterprise workspace, only the workspace owner needs to do this once; everyone else on the workspace can then connect their own Kula account without repeating the setup.

What you can do once it's connected

The connector gives Claude the same capabilities as the previous local setup:

  • Candidate search

  • Applications

  • Scorecards

  • Scheduling

  • Stage moves

Try asking Claude things like "show me candidates in the final interview stage for the Backend Engineer role" or "move Jane Smith to the next stage."

If you already set up the old (local) version

If you connected Kula to Claude before September 2026, that was the old local setup — a Node.js package (@kula-ai/mcp-server) added to Claude's config file with an API key. That version still works, but the new connector replaces it: no install, no config file, and it updates automatically.

To switch, set up the new connector as above, then remove the old one so the two don't run side by side.

Good to know

  • Running the old local setup and the new connector at the same time causes duplicate or odd results. If Claude seems to show Kula tools twice, or results look off, that's almost always the cause. Fix: open your Claude Desktop config file and remove the kula entry under mcpServers, then restart Claude.

  • Kula isn't listed in Claude's built-in connector directory yet, so you add it as a custom connector rather than finding it in a list.

  • The connector works on both Claude web and Claude desktop, and updates roll out automatically — there's nothing to manually reinstall or update going forward, unlike the old local package.

  • You only see what your Kula permissions already allow. The connector doesn't grant any access beyond your normal Kula account — it's scoped to your existing role and permissions.

FAQ

No confirmed customer questions found yet for the new MCP connector — it shipped the same week this article was written.

Need help?

If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.