Building a Recruiting Copilot That Looks Up Contacts via MCP
Building a recruiting copilot that looks up contacts via MCP – wire Claude/Cursor agents to profile-URL find or burning seats.
A recruiting copilot should shortlist, summarize JDs, and – when asked – look up contact fields from person profile URLs. It should not scrape, or hide billing. MCP (Model Context Protocol) is how agents call typed tools without you building a custom plugin for every model host.
Invenitor exposes lookup as MCP tools: Connecting people; a lookup API, not a sales cloud. Start at /mcp.md – agent-readable docs, same Credit B pool as REST.
Parent: MCP for Recruiting Agents. Definition: What Is an MCP Server for Hiring Product Teams?. Claude/Cursor: Claude / Cursor Agents: Calling a Contact Lookup MCP Endpoint. Docs why: Agent-Readable Docs: Why MCP.md Matters.
Copilot architecture (honest scope)
| Layer | Job | Not the job |
|---|---|---|
| MCP lookup tool | URL → email/phone when found | Scrape LinkedIn HTML |
Layer clarity: Contact Lookup API vs CRM vs Sequencer. ATS notes: Adding Contact Lookup to an ATS. Webhook-free: Webhook-Free Enrichment.
Tool contract the copilot must respect
- Input: person LinkedIn or GitHub URL (optional full name later).
- Output: primary email/phone/links when found.
- Billing: same Credit B as REST – found-only.
- Soft mesh: coverage varies; no brochure %.
Hub: LinkedIn or GitHub Profile URL → Contact Lookup API. Definition: What Is a LinkedIn Profile URL Lookup?.
Prompt refusals that keep copilots safe
Forbid retry-until-found loops that ignore soft mesh. Forbid pasting API keys into the chat. Put those refusals next to /mcp.md in your runbook. Primer: What Are API Credits.
Production twin: REST still matters
Agents and servers should share auth hygiene – Rate Limits and Keys, REST Enrichment Inside a Hiring Product, /docs. OpenAPI: OpenAPI Hygiene for Enrichment Endpoints.
Desk reality
India freelancers and WhatsApp-first desks can use a copilot for batch shortlists – then message only on found contacts: Freelance Recruiter Workflow, WhatsApp-First Recruiters, Night-Shift Freelance Recruiters, Contract Recruiters in India.
Commercial
Prepaid INR packs – /pricing, 25 to 1,000 Credits, INR Credit Packs. Trust: Trust Checklist.
What should you do next?
Read /mcp.md. Wire Claude or Cursor per the Claude/Cursor post. Confirm the ledger. Keep /docs and /pricing in the same onboarding doc.
Copilot one-liner
Our recruiting copilot looks up contacts via MCP – typed find, same credits as REST – never a scraper in a trench coat.
Copilot eval set (honesty first)
Primer: What Are API Credits. Pay-per-lookup: What Is Pay-Per-Lookup Pricing?. Trust: Trust Checklist. Hub: LinkedIn or GitHub Profile URL → Contact Lookup API. Builders: Rate Limits and Keys, OpenAPI Hygiene, Webhook-Free Enrichment. Desks: WhatsApp-First Recruiters, Night-Shift Freelance Recruiters. Docs twin: Agent-Readable Docs, Claude / Cursor Agents, MCP for Recruiting Agents. Commercial: /pricing, 25 to 1,000 Credits. /docs · /mcp.md.
Ship checklist
Secrets in env. Concurrency capped. Prompt refusals committed. Ledger reviewed weekly. Category: What a Contact Lookup API Actually Does. Layer: Contact Lookup API vs CRM vs Sequencer. Margins: Modeling Cost per Placed Candidate. India: India Boutique IT Staffing. Packs: INR Credit Packs.
Questions
What is a recruiting copilot in this context?
An agent that helps shortlist and can call a contact lookup tool – not a dialer and not a CRM replacement.
Why MCP instead of a custom plugin?
MCP gives typed tools across hosts (Claude, Cursor, and others) without rebuilding integrations per vendor.
Where do I start?
/mcp.md for agent docs, /docs for REST twin, /pricing for packs.
Do MCP finds use different credits than REST?
No – one pool, same Credit B found-only rule.
Can India desks use this with WhatsApp?
Yes: look up, then WhatsApp only when found – see WhatsApp-First Recruiters.
How do rate limits apply to agents?
Same as REST – back off on 429; see Rate Limits and Keys.
More in this cluster
Multi-Agent Hiring Pipelines: Who Calls Lookup, Who Calls Outreach
Multi-agent hiring pipelines: who calls lookup, who calls outreach – keep find tools separate from sequencers so empties stay empty and credits stay honest.
Read
Agent-Readable Docs: Why MCP.md Matters for Contact APIs
Agent-readable docs: why MCP.md matters for contact APIs – typed tools for Claude/Cursor agents, same Credit B as REST.
Read
Claude / Cursor Agents: Calling a Contact Lookup MCP Endpoint
Claude and Cursor agents calling a contact lookup MCP endpoint: tool calls instead of scrapers – same credits as REST.
Read