OUTREACH IN CLAUDEEarly access
Run LinkedIn outreach from Claude, safely.
Connect your own LinkedIn account and run recruiting outreach from Claude through the RecruitMCP MCP server. Claude drafts the sequence and enrolls the people you choose; RecruitMCP handles send limits, timing, approvals, suppression and stopping on reply. Outreach is in early access.
Early access. Outreach is in early access. Sign up and we'll enable it for your workspace. LinkedIn is the first channel; more channels will follow later.
Who this is for
Recruiters, sourcers and recruitment teams who already work in Claude, and developers who want outreach to be one more set of MCP tools next to candidate search and lists.
The challenge
Illustrative example. Harbour Talent and Mira Claes are fictional. This is an example workflow, not a real customer, testimonial or measured result.
Mira is a recruiter at Harbour Talent. She builds a shortlist for a backend role in Claude, then switches to another tool to send connection requests and follow-ups by hand. She has to remember who she already contacted, keep her own account within safe sending behaviour, check the do-not-contact list, and notice replies in time to stop the next message. When any of these slips, the same person gets contacted twice, or a follow-up goes out after someone has already answered.
Outreach where you already work
With RecruitMCP, Mira stays in Claude. She asks Claude to draft a short sequence for the shortlist, reviews every rendered message in the preview, and enrolls the people she has chosen. RecruitMCP sends from her own connected LinkedIn account, at a natural pace, inside business hours, and within the account's limits. When a candidate replies, their sequence stops and the conversation is waiting for her in Claude.
Workflow
Where RecruitMCP fits is marked with (RecruitMCP).
- Connect your account. Connect your own LinkedIn account to RecruitMCP (connect_outreach_account). Newly connected accounts warm up gradually.
- Pick the people. Find candidates with search_people and keep them in a list with save_to_list, or start from a list you already have (RecruitMCP).
- Write the sequence. Claude drafts the steps with you, such as a connection request and a follow-up message, and saves the sequence (save_sequence). Nothing is sent at this stage.
- Preview and enroll. enroll_candidates first shows a preview: every rendered message, who is scheduled, and who is skipped or refused, for example because they are suppressed or already in the sequence. You confirm before anyone is enrolled (RecruitMCP).
- Approve and send. With approval turned on, each message waits until a person approves it (approve_message). RecruitMCP sends within the account's limits, in business hours for the account's timezone, with natural spacing (RecruitMCP).
- Reply and stop. A reply stops that person's sequence automatically. You read the conversation and answer it yourself from Claude (list_replies, send_reply). There is no auto-reply.
Safety built in
This is how outreach protects your account and the people you contact.
- Daily and weekly send limits per account. Every connected account sends within daily and weekly limits (get_outreach_limits).
- Gradual warm-up. A newly connected account starts slowly and builds up over time.
- Business hours and natural spacing. Actions are sent only within business hours in the account's timezone, spaced out the way a person would work.
- No double sends. Each action is sent at most once, even after an error or a retry, and duplicate invites to the same person are refused.
- Human approval, when you want it. Turn on approval and every message waits for a person to approve, edit or skip it.
- Suppression checked every time. The suppression list is checked before every send, so people who asked not to be contacted stay out (add_suppression).
- Stop on reply. A reply stops that person's sequence automatically.
- Automatic pause and a global pause switch. Sending pauses automatically when the network signals a problem with the account, and one switch pauses all outreach at once.
- Audit log. Every action is logged, including who approved what (get_outreach_activity).
What RecruitMCP provides and what you own
What RecruitMCP provides:
- Outreach tools over MCP: connect an account, save sequences, preview and enroll, approve, replies (connect_outreach_account, save_sequence, enroll_candidates, approve_message, list_replies, send_reply)
- Sending within limits, warm-up, business hours and spacing
- No double sends, suppression checks, stop on reply, pauses and an audit log
- Candidate search and lists to build who you contact (search_people, save_to_list)
What you own:
- Your own LinkedIn account and what you say from it
- Who you choose to contact and why
- Message content and approval
- Your recruiting process and follow-up
Example approval card
Illustrative example. All details below are synthetic. Names are fictional and this is not live RecruitMCP output.
Text version of this example
| Field | Illustrative display |
|---|---|
| Candidate | Jonas Verbeke, Backend Engineer, Antwerp, Belgium |
| Sequence step | Follow-up message after an accepted connection request |
| Sending account | Mira Claes (connected LinkedIn account) |
| Message preview | "Hi Jonas, thanks for connecting. I'm working on a backend role at a product company in Antwerp and thought of your work on event-driven systems. Open to a short chat?" |
| Status | Waiting for approval. Next send window: business hours, account timezone. |
| Actions | Skip, Edit, Approve |
Tools and endpoints
| MCP tool | REST route | What it does |
|---|---|---|
search_people | POST /v1/people/search | Search people: profiles for a filter set. |
save_to_list | POST /v1/lists | Save people to a list. |
add_suppression | POST /v1/suppressions | Suppress a person. |
Base URL https://api.recruitmcp.com. Full reference: MCP tools Quickstart
What changes
Outreach moves into the same place where the shortlist was built. Recruiters keep control of who is contacted and what is said, while send limits, timing, duplicate protection, suppression and stopping on reply are handled for every account by default.
FAQ
Is outreach live?
Outreach is in early access. Sign up and we'll enable it for your workspace. Candidate search, profiles, email and phone lookup and lists work once you have an API key.
Which channels are supported?
LinkedIn first, from your own connected account. More channels will follow later.
Does RecruitMCP send email?
No, not in the first release. Outreach starts with LinkedIn.
Is LinkedIn where the candidate data comes from?
No. LinkedIn is only the channel you send from, through your own connected account. For candidate data, we aggregate public professional data and don't disclose our providers.
Does Claude send messages on its own?
Claude prepares sequences and enrollments through MCP tools. You confirm every enrollment after a preview, and with approval turned on, every message waits for a person. Replies are never answered automatically.
What keeps my account safe?
Daily and weekly send limits per account, gradual warm-up for new accounts, sending in business hours with natural spacing, automatic pause on network signals and a global pause switch.
What happens when someone replies or asks not to be contacted?
A reply stops their sequence automatically. Add the person to your suppression list and they are kept out of every future send.
Can I use it from Cursor or my own code?
Yes. The same MCP server works in Cursor, and the tools are designed for agents and developers alike.
Run LinkedIn outreach from Claude
Outreach is in early access. Sign up and we'll enable it for your workspace. Candidate search and lists are ready when you sign up.