Claude for Recruiters: Run Your ATS by Conversation (MCP)

You just hung up with a candidate and you have two paths. The usual one: open the ATS, find her profile, write the note, open the calendar, pick a slot and fill in the invite. Or the new one: tell Claude in one sentence and it's done. You can now connect Hilancer to Claude, Anthropic's AI assistant, and run your processes by conversation. This article covers what an MCP is in plain words, what you can ask for, what it deliberately won't do, and how to connect it in two minutes.

What an MCP is, and why it matters to a recruiter

MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to the tools you already use. Without it, Claude only knows what you paste into the chat. With the Hilancer connector, Claude can look up your real candidates, positions and interviews, and make changes to your account when you ask.

You don't need any technical knowledge to use it. There's no code and no API keys: you add the connector once, authorize with your Hilancer account, and from then on you talk to Claude the way you'd talk to a colleague with your ATS open next to them.

An example: the note and the interview in one sentence

You just finished a call with Ana García, who applied for Full Stack Engineer. You write to Claude:

Just talked to Ana García. Note that she's great at React but her English needs work, and book her technical interview Thursday at 3pm.

Claude finds Ana in your Hilancer account and adds the note to her process. Before scheduling, it stops and confirms the date, time, time zone, duration and who will receive the invite, because scheduling an interview sends the candidate a real email. You reply "go ahead" and the interview is booked in Hilancer, with the invite in Ana's inbox. If you have Google Calendar connected, the event includes a Meet link.

What used to take five screens is now a thirty-second conversation.

What you can ask Claude for

Half the value is in asking. Claude reads your pipelines and answers with data from your account:

• "Do I have interviews tomorrow?"
• "Who has been stuck for more than two weeks in the Accountant search?"
• "Who in my talent pool fits this new Product Designer role?"
• "How are my metrics looking this month?"

The other half is taking busywork off your plate. Claude can create and update candidates and positions, add internal notes to a candidate's application (the candidate never sees them), and schedule or reschedule interviews. Positions created by Claude start paused, so nothing goes live that you haven't reviewed.

Something that surprises people the first time: Claude also flags things you didn't ask about. If it sees an interview booked at 4 a.m., it suggests checking the time zone before the candidate gets the wrong time. If candidates have been sitting without movement for days, it points them out.

What Claude won't do, and why

We designed the connector so decisions that affect a person stay yours. Claude doesn't move candidates between stages, reject, delete, share profiles or cancel interviews. You do those from Hilancer, where you see the full context.

The only thing that reaches a candidate is the invite when you schedule or reschedule an interview, and Claude always confirms the details with you before sending it. If you ever want to cut access, disconnect it from Settings → Integrations in Hilancer.

How to connect Claude to Hilancer, step by step

1. In Hilancer, go to Settings → Integrations. The Claude card there has the connector URL.
2. In Claude Desktop, go to Settings → Connectors and choose "Add custom connector".
3. Paste the URL: https://mcp.hilancer.io/mcp
4. Click "Connect" and authorize access with your Hilancer account.

That's it. In your next conversation, ask something about your pipelines. When Claude checks your account you'll see a line saying it used the Hilancer integration.

What you need

On the Hilancer side, the connector is included in the Pro plan, and you need your own Pro account: if you're an invited user in an organization on the Lite plan, you won't be able to connect it. On the Claude side, it works with any plan, including the free one, which allows one custom connector. On Claude Team and Enterprise plans, an organization Owner has to add the connector first.

For now the integration works with Claude only. Other assistants, such as ChatGPT, aren't supported.

FAQ

Can Claude message my candidates on its own?

No. The only thing a candidate receives is the invite when you schedule or reschedule an interview, and Claude confirms the date, time and recipient with you before sending it.

Do I need to know how to code?

No. You connect it by pasting a URL and authorizing with your Hilancer account. After that, you just type in the chat the way you'd write to a colleague.

Can candidates see the notes Claude adds?

No. They're internal notes on the application, just like the ones you write by hand in Hilancer.

Less busywork, more conversations

AI doesn't replace your judgment about a person, which is why Claude doesn't make decisions about candidates. What it does is take the busywork off your plate: logging notes, scheduling and digging for data across screens. If you've already automated candidate notices with WhatsApp and Google Calendar, this is the next step: a recruitment CRM that understands you when you talk to it.