Use cases
Who uses RecruitMCP, and for what.
Each workflow says who it is for, the problem, the steps, prompts you can copy, a sample transcript, the tools it calls, and an example credit cost computed from current prices.
Sourcing in your agent
Find people. Estimate first, raw profiles back.
- Agency recruiter, new mandateTurn a job note into a sourced shortlistPaste the brief into your agent. Get raw profiles with distance, experience, and tenure, after you approve the cost.start_searchrefine_searchget_search_resultsRead the workflow →
- In-house TA, niche tech rolesRerun a search every week without paying for the same peopleKeep a role warm. Reruns skip pages you already paid for and people already in your seen register.extend_searchset_candidate_statuscheck_candidatesRead the workflow →
- Recruiter who calls firstGet personal contact details for your top picks onlyAsk for email and phone on the few people you will call. The price is shown before it runs, and a miss is free.find_contact_detailslookup_peoplesave_to_listRead the workflow →
Outreach in your agent
Contact people. Your agent writes, we pace.
- Recruiter using Claude or Grok BotLet your agent write the invites, and RecruitMCP pick the send timesYour agent writes a short note per person. RecruitMCP schedules each send from your LinkedIn account under the caps.connect_outreach_accountget_outreach_limitssave_sequenceenroll_candidatesRead the workflow →
- Recruiter running sequencesFollow up without talking over a replyEvery follow-up checks the thread first. A reply stops the sequence, and your agent drafts the answer for you to confirm.list_repliesget_conversationsend_replyupdate_enrollmentRead the workflow →
From your code
REST, signed webhooks, and spend caps per key.
- Sourcer with own toolingRun sourcing from n8n or your own scriptsCall the same plan, estimate, and run steps over REST. A signed webhook tells your workflow when the run is done.POST /v1/search-plansPOST /v1/runsGET /v1/runs/{run_id}/candidatesGET /v1/eventsRead the workflow →
- Product teamBuild a recruiting product on the APIUse sourcing as a backend: an OpenAPI contract, dry-run estimates to show your users, and spend caps per key.POST /v1/runsGET /v1/runs/{run_id}/candidatesPOST /v1/seen:checkPOST /v1/suppressionsRead the workflow →
Try one with free credits.
Connect your agent or create a key, describe a role, and read the estimate. Nothing is spent until you confirm.