Ask your recruitment data questions in plain language
This MCP connector lets a recruiter query pipeline, candidate and task records conversationally instead of building a report or hunting through screens.
You describe what you need, and the assistant returns a structured answer based on live data.
How setup works
The connector is remote, so there is nothing to install locally and no terminal commands to run. Setup is three steps: add the remote server address to your assistant's connector settings, authenticate with your CRM login, and start asking questions. Because the server is hosted, improvements reach every connected assistant automatically.
Access follows your existing roles
Each person connects with their own login, so access follows existing permissions rather than creating a separate data copy. If a record is not visible or editable for someone in the CRM, the same limit applies through the assistant. Administrators control rollout by enabling MCP Access on the roles that should have it.
What you can ask
Useful questions cover the everyday workflow: where a role stands in the pipeline, how a candidate is progressing, which tasks or follow-ups are due, what call activity has happened, and summaries that would otherwise need a report. The pattern that works best is to name the job, name the stage, and state the output you want.
Worked example: an executive search report
Take a named role, look at everyone currently sitting in Shortlist, and produce a polished executive search report with a summary up front plus anything unusual you notice. Replace the job title with your own and keep the stage and requested output explicit; that specificity is what makes the answer structured rather than generic.
Telling a setup gap from a permissions gap
Two failures look similar but need different fixes. If the connector cannot be added or sign-in fails, the problem is at the setup layer: check the server address and the OAuth sign-in. If the connector works but a record is missing or an edit is refused, the problem is at the permissions layer: the person's CRM role does not grant that access, and an administrator needs to review MCP Access for that role. Testing with a single narrow question, such as pipeline status for one job, separates the two quickly.
Rollout checklist
Before connecting a team, check these points: confirm which roles need MCP Access, confirm each user signs in with their own account, confirm the assistant you use supports MCP connectors, and confirm plan inclusion with {{OWNER_PLAN_INCLUSION}}. Then test one narrow question, such as pipeline status for a single job, before rolling out report prompts to the wider team.
Frequently asked questions
Do I need to be technical to set this up?
No. There is no local setup or terminal work. Add the remote server address in the assistant's connector settings, sign in, and the connection is ready in a few minutes.
Can multiple people on my team use this?
Yes. Every teammate signs in with their own account through OAuth. What they can view or change through the assistant mirrors what their role allows in the CRM itself. Administrators decide who gets access by turning on MCP Access for the relevant roles.
What kind of questions can I ask?
Questions about the recruitment workflow in plain language, including pipeline status, candidate progress, tasks, call activity and report generation. The response is structured and drawn from live CRM records.
Which AI assistants does this work with?
Any MCP-compatible assistant, including Claude.ai on web and mobile, ChatGPT, Claude Desktop and other supported platforms. Because the server is remote, functionality stays current across those tools without manual updates or a local install. One OAuth sign-in covers access from any connected platform.
Does this work on mobile or web apps?
Yes. It works on Claude.ai, ChatGPT, Claude Mobile and other MCP-compatible platforms on web and mobile. Enable the connector in the app you prefer, then ask about recruitment data.
Which plans include MCP access?
{{OWNER_PLAN_INCLUSION: Confirm which paid plans include MCP access and how it is described on the pricing page.}}