How to Connect Recruitee to Claude (and Where It Stops)
Recruitee isn’t in Claude’s connector directory and doesn’t ship its own MCP server — the only path is a community bridge, most commonly Composio’s Recruitee MCP. With it, Claude can source candidates, list job offers, update candidate stages, and read notes through Recruitee’s public API. But like every Claude connector, it’s a thing you drive: Claude touches your pipeline the moment you ask in a chat, and does absolutely nothing between prompts — even though Recruitee itself fires webhooks the instant a candidate applies.
Below: what the community connector reaches, how to wire it, why chat-only leaves the best automation on the table, and how to make a candidate event trigger real work.
What you can connect today
Recruitee has a solid public API and webhooks, but no first-party Claude integration. The available route is a Model Context Protocol server run by a third party — Composio being the most established:
- Source and read. Search candidates, pull the pipeline for a job offer, and read candidate profiles and notes.
- Update stages. Move a candidate through pipeline stages by name.
- Structure queries. “List candidates in the ‘Screening’ stage for the Berlin marketing role and who added the last note.”
Two honest caveats. You’re handing a third party OAuth access to candidate data, so vet it like any vendor. And this is on-demand only — Recruitee will happily tell your systems a candidate applied via webhook, but the connector isn’t listening for that; it waits for you.
Setting it up
With Composio’s server and Claude Code:
- Get a Composio API key and connect your Recruitee account through OAuth.
- Register the server:
claude mcp add --transport http recruitee-composio "YOUR_MCP_URL" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY". - Confirm by asking Claude to list your open job offers.
On desktop Claude, adding it as a remote custom connector needs a paid Claude plan. Either way, you’re running a middleman between Claude and Recruitee and keeping it alive.
Where chat-only stops
Recruitee is built around events — new applicants, stage moves, disqualifications, notes — and even exposes them as webhooks. A chat-only connector ignores every one of them.
The application webhook fires; Claude doesn’t hear it. Recruitee can notify an endpoint the instant someone applies. The connector isn’t that endpoint. So the same-day acknowledgment that keeps a candidate warm only happens if you remember to ask Claude to help write it.
Disqualifications leave people hanging. Mark a candidate as rejected and they should get a prompt, gracious note. Claude can draft one — when you open a chat. Nobody has the bandwidth to do that per candidate, so silence wins.
It acts inside Recruitee, not across your stack. Even updating a stage, it stays in Recruitee. It can’t send the candidate an email through Gmail, hold interview times on the panel’s calendars, or post “5 new applicants for Designer” to your recruiting Slack channel.
So Claude is a fine way to poke at your pipeline on demand — and structurally unable to be the assistant that reacts to a candidate event while you’re focused elsewhere.
Candidate events that trigger real work: Carly
Recruitee already emits the events; the missing piece is something that listens and acts. Paste your Recruitee API key on dashboard.carlyassistant.com/integrations and Carly — an AI executive assistant that runs on triggers, in the cloud — becomes that listener:
- A new candidate applies → Carly sends a same-day acknowledgment through Gmail or Outlook and, for flagged roles, proposes screen times against your calendar.
- A candidate moves to “Interview” → Carly emails the logistics, books the calendar holds, and posts the details to the hiring team’s Slack channel.
- A candidate is disqualified → Carly sends a warm, on-brand decline so no one waits in silence.
- You describe it in plain English — “when a candidate is added to the Senior Developer job, email me their CV summary and add three interview slots to my calendar” — and Carly interviews you, then builds the workflow with you.
AI agents start at $35/month, and steps that don’t use AI — the email, the calendar hold, the Slack post — run free and unlimited. Recruitee is one of 200+ tools Carly connects to; see the full integrations list.
Side by side
| Claude + community MCP | Carly | |
|---|---|---|
| Search candidates, read notes | Yes | Yes |
| Update candidate stages | Yes | Yes |
| Acts when a candidate applies | No | Yes, on triggers |
| Sends a decline on disqualification | No | Yes |
| Emails candidates / books interviews | No | Yes |
| Posts to Slack, updates your calendar | No | Yes |
| Runs overnight with your laptop shut | No | Yes (cloud) |
| Setup | Self-hosted MCP + paid Claude plan | Paste API key, plain-English interview |
Frequently Asked Questions
Is there an official Recruitee connector for Claude?
No. Recruitee is not in Claude’s connector directory and does not publish its own MCP server. The route is a third-party MCP server such as Composio’s, which connects Claude to Recruitee’s public API.
What can Claude do with Recruitee once connected?
Via a community MCP server it can search and read candidates, pull a job’s pipeline, read notes, and update candidate stages — inside a chat, when you ask.
Recruitee has webhooks — can Claude use them?
Not through the connector. Recruitee fires webhooks on events like a new application, but the Claude MCP server doesn’t listen for them. To act on those events, use a trigger-based agent like Carly, which connects with your Recruitee API key.
What does automated Recruitee follow-up cost with Carly?
AI agents start at $35/month, and the non-AI steps — sending the acknowledgment, booking interview holds, posting to Slack — run free and unlimited.
More: Claude + Lever · Claude connectors · Can Claude send emails · AI agents for recruiters · Best AI tools for recruiters · Best AI executive assistants
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
