MCP Guide
Why Your MCP Connector Is Only Working With 9% of Your Recruiting Data (And How to Fix It)
Webinar
See how to use these MCP connectors together to find team bottlenecks and build coaching plans
MCP Guide
CoRecruit now connects directly to Claude and other AI chat applications through MCP.
MCP Setup Guide
This is where you'll find the exact server code you need in step 4.
Search for connectors in whatever LLM you use. You should find these in your settings.
CoRecruit isn't a listed integration yet (that queue is a long one), so you'll add it manually: click Add, then Custom Connector. Name it Corecruit.
Head back to the knowledge base article, scroll down to find the MCP server code, and paste it into your assistant. Click Continue.
You'll be prompted to authenticate and review permissions.
It's a direct link between CoRecruit and your AI assistant, Claude, ChatGPT, Copilot, or others. Once connected, you can ask your assistant questions about your calls, candidates, and conversations directly, without opening CoRecruit itself.
No. The whole setup runs through your assistant's own connector settings, name it, paste in one piece of server code from our knowledge base article, sign in, and you're done. Most people finish in a few minutes.
No, the setup is almost identical for ChatGPT, Copilot, and other assistants that support custom connectors.
No. Access is entirely read-only. Your assistant can query calls, transcripts, and summaries, it can't edit, delete, or write anything back into your account.
Private meetings stay private. Your assistant has no access to them at all. One trade-off worth knowing: a private meeting also won't sync back to your ATS, privacy is all or nothing on that call.
Book a demo and find out why recruitment agencies trust CoRecruit to reduce admin and move candidates faster.