RECRUITMENT PLATFORM BUILDERS
Build the recruitment platform your users need.
RecruitMCP gives product teams candidate search, profile enrichment and email and phone lookup through API or MCP. Keep control of your interface, matching method, workflows and integrations, and build on candidate data and supported actions designed to be called by your application or agent.
1,250 free credits
Product example: Everyjob. Everyjob is shown as an example of the kind of product a team can build. This is not a testimonial, a result or a description of Everyjob's technical setup.
Conceptual integration pattern
Conceptual integration pattern. This is not a depiction of any specific production stack.
- Your product UI. Jobs, candidates, teams and review screens.
- Your product logic. Matching, workflows, permissions and tenancy.
- RecruitMCP (API or MCP). Candidate search, full profiles, email and phone lookup, lists and suppression.
- Your customer systems. ATS, inbox and reporting, connected by your integrations.
| Part | What it owns | Why it matters |
|---|---|---|
| Your recruitment product | Interface, job setup, role-specific matching, review screens, customer settings, team workflow and reporting | This is where your product becomes distinctive. |
| RecruitMCP API or MCP | Candidate search by title, company, location and free-text keywords (search_people, resolve_location), profile lookup and enrichment (match_person, enrich_profiles), find email and phone (find_contact_details), lists (save_to_list) | Reusable recruitment data and supported actions, not a complete ATS or product UI. |
| ATS and connected accounts | Existing candidate history, pipeline states and customer-controlled channels | Access and write-back depend on the integrations your team configures. |
Outreach is in early access: see Outreach in Claude.
Tools and endpoints
| MCP tool | REST route | What it does |
|---|---|---|
search_people | POST /v1/people/search | Search people: profiles for a filter set. |
resolve_location | GET /v1/lookups/locations | Resolve a place to a location filter. |
match_person | POST /v1/people:match | Match a person by name and company. |
enrich_profiles | POST /v1/people:enrich | Enrich profiles. The profile does not include email or phone. |
find_contact_details | POST /v1/people/contacts:fetch | Find email and phone. A dry run returns the estimate first. |
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
Who this is for
Founders and engineering teams building recruitment SaaS, vertical hiring products, sourcing tools, ATS extensions, talent intelligence products or recruitment workflows for a specific market.
The product-building problem
A recruitment platform needs more than a search box. It needs a usable way to turn a vacancy into candidate discovery, compare profiles against role requirements, let a recruiter see why someone is relevant, handle people already in an ATS, and support the steps that follow. Building all of the data access and profile enrichment in-house can pull engineering time away from the product experience customers actually choose you for.
From candidate data to a product experience
Everyjob shows the kind of focused recruitment experience a product team can create: external candidate sourcing, rediscovery of people already in an ATS, and explanations of candidate fit brought into one workflow. The product value is the way those capabilities work together for the recruiter, not the presence of another standalone search screen.
Build your differentiator, not every underlying capability
A product team still needs to decide how a vacancy is represented, how candidate relevance is assessed, what recruiters can review, how existing ATS records are handled and which actions need approval. RecruitMCP can provide the candidate data and supported actions. Your platform owns the experience and the rules that make it right for your customers.
Built for production use
- Server-side keys. Call RecruitMCP from your backend with API keys kept out of browser code and source control. Keep tenants isolated in your own application.
- Preview before spend. A dry run returns the cost estimate before a search or email and phone lookup runs, and calls above your key's approval threshold return approval_required instead of spending.
- Privacy controls. Suppress a person to keep them out of search, lists, email and phone lookup and future actions.
- Agent or code. The same capabilities are available as MCP tools for agents in Claude or Cursor, and as REST endpoints for your backend.
What changes
Your engineers spend their time on the recruiter experience, matching approach and workflow that set your product apart, while candidate search and profile data come from one documented API and MCP server.
FAQ
Is RecruitMCP a complete recruitment product?
No. RecruitMCP provides candidate data and supported actions through API or MCP. Your platform owns the interface, tenancy, permissions, ranking, ATS connections and any email you send.
Does Everyjob run on RecruitMCP?
Everyjob is shown here as an example of the product category. This page does not describe which services Everyjob uses.
Where does the profile data come from?
We aggregate public professional data and don't disclose our providers.
Does RecruitMCP send email or messages for my users?
Not email. Outreach from your users' own connected accounts is in early access (see Outreach in Claude). Any other messaging in your product is handled by your own implementation.
Does RecruitMCP return a fit score?
No universal fit score. Your product ranks and explains candidates using job-related criteria you define.
Can I store the data in my product?
Your platform decides what it stores and for how long. We recommend recording the source and refresh date of every profile and offering a clear removal path.