Candidates go quiet in a pipeline long before anyone notices. This sweeps every
active job, finds anyone who's been parked in the same stage for more than ten days,
and hands the job owner a task instead of letting the clock keep running. Nothing
about a candidate's stage changes; this is purely about making sure no one gets
forgotten.
Before you begin:
You need to have access to Claude (web, desktop, or mobile app) with the Recruit CRM MCP connector added to your Claude account.
Recruit CRM MCP is available only on the Business and Enterprise plans.
You should know which job owner each active job is assigned to, since follow-up tasks will be routed to them.
By default, Account Owners and Admins have MCP access. Users on custom roles with access to MCP can also have MCP access.
📋 How to Generate a Pipeline Bottleneck Report Using Claude?
Step 1. Open Claude and Confirm the Recruit CRM MCP Connector Is Active:
Log into Claude and check that the Recruit CRM MCP connector appears as a connected source in Claude's settings.
If the Recruit CRM MCP connector isn't connected yet, add it from Claude's settings and follow the authentication steps.
Step 2. Ask Claude to Scan Active Jobs for Stalled Candidates:
Start a new chat with Claude and ask it to scan for candidates who have stalled. For example: "Find every candidate who's been sitting in the same hiring stage for more than 10 calendar days, across all active jobs. For each one, pull their stage history and tell me the last action taken. Don't move anyone's stage — just create a follow-up task for the job owner with the candidate's name, job, days stalled, and last activity.”
Claude will use the Recruit CRM MCP connector to check time-in-stage across active jobs.
Step 3. Review the Digest:
Claude will return a summary of how many candidates it found stalled, and confirm that a follow-up task was created for each one, routed to the relevant job owner.
Step 4. Follow Up on the Tasks:
Job owners can then act on the tasks created in Recruit CRM at their own pace, reviewing the stalled candidate and deciding whether to move them forward, reach out, or screen them out.
⚠️ Data Privacy - Please Read Carefully
When you use this MCP server, your Recruit CRM data is sent to the AI assistant you're using (e.g. Claude, ChatGPT). This means:
Candidate profiles, names, email, phone, job history, hiring stage, etc. will be exposed to the AI provider so that it can assist with the data.
Company and contact data, job details, notes, and call logs may also be exposed depending on what you ask.
The AI provider processes this data on their servers according to their own privacy and data retention policies.
What you should check before using:
Most AI providers (including Claude) have a data retention period - typically around 30 days for conversation data, though this varies by plan and provider. Always check the latest policies directly on their official websites:
If your team or organization has data residency, GDPR, or other compliance requirements, confirm that using an AI assistant with live recruitment data is permitted.
Use good judgment about what you query - only ask for data that's necessary for the task at hand.
By using this tool, you accept responsibility for ensuring its use complies with your organization's data policies and applicable regulations.
FAQs
Does this change anything in Recruit CRM?
Does this change anything in Recruit CRM?
It creates follow-up tasks, but it never changes a candidate's hiring stage.
Can I run this automatically on a schedule?
Can I run this automatically on a schedule?
Yes. This use case is intended to run daily or weekly as a scheduled task in Claude.
Conclusion:
The Recruit CRM MCP connector allows Claude to sweep every active job for candidates who've stalled in the same hiring stage, so no one gets forgotten while the pipeline keeps moving elsewhere.