What Is an MCP Server? (For Hiring Product Teams)

MCP means Model Context Protocol. For hiring product teams, an MCP server is a documented way for AI agents to call tools – including a contact lookup – with clear inputs and outputs. Instead of scraping LinkedIn or inventing an email, the agent asks the tool: here is a profile URL; return email/phone/links when found. Empty means not found.

Invenitor exposes contact lookup for agents this way (alongside REST). Connecting people – a lookup API, not a sales cloud. Notes: /mcp.md. Sibling how-to: MCP for Recruiting Agents – Wire Contact Lookup Without Building a Scraper.

Why should hiring PMs care about MCP?

Agents are showing up in recruiting ops: shortlist helpers, ATS copilots, desk assistants. Without a tool boundary, models guess. Guessed emails break trust faster than blank cells. MCP gives product teams a contract: the agent can look up; it cannot invent. Honesty pillar: Empty Means Not Found.

What is an MCP server in plain English?

Think of it as a menu of tools an agent is allowed to use. Each tool has a name, input schema, and output shape. A contact-lookup tool accepts a LinkedIn or GitHub profile URL (name helps) and returns contact fields or empties. The agent does not parse HTML. The agent does not improvise SMTP patterns.

Category twin in REST language: What a Contact Lookup API Actually Does. Hub HowTo: LinkedIn or GitHub Profile URL → Contact Lookup API.

How does this differ from “just call the API from the prompt”?

You can always call REST from application code. MCP matters when the agent runtime chooses tools. Product teams want:

• Tool allowlists (lookup yes, scraper no).
• Shared auth via API key.
• Consistent empty semantics across Claude, Cursor, and internal agents.
• The same credit pool as REST.

Docs: /docs. Pricing: /pricing.

What should hiring product teams put in the PRD?

1. Job to be done: resolve contacts for already-identified candidates.
2. Non-goals: sequencing, CRM, inventing emails, publishing hit-rate %.
3. Empty UX: pass through; show not found.
4. Billing: 1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend.
5. Rails: REST for services; MCP for agents – /mcp.md.

Enrichment language for GTM: Contact Enrichment Explained for Recruiters.

How do credits work when agents loop?

Agents can waste time by re-calling empty URLs. They should not invent contacts to “finish the task.” Under Credit B, empty completed finds are free; timeouts/errors do not spend. Still teach the agent: one clean URL per person; stop on empty. Pack feel: INR Credit Packs. PAYG framing: Pay-As-You-Go Contact APIs for Teams That Hate Annual Seats.

Soft mesh and demos without theater

Demo with real shortlist URLs. Expect some empties. Do not script fake hit rates. Soft mesh coverage varies by person and source. That honesty is a product feature for hiring brands – not a bug in the MCP layer.

India desks and global builders – same server idea

India boutique desks may keep sheets + WhatsApp and let an agent fill columns. Global ATS builders may embed MCP beside REST. Same rules. Desk SOP: India Boutique IT Staffing. ATS notes: Adding Contact Lookup to an ATS.

What should you do next?

Read /mcp.md, grab a key from /pricing, wire one agent to look up three real URLs, and verify empty pass-through. Keep /docs open for the REST twin. If the tool returns empty, leave it empty – that is the server doing its job.

How is MCP different from a plugin marketplace slogan?

Marketplaces sell distribution. MCP is a protocol for tool use. For hiring, the valuable part is the contract: agents call a lookup with known empty semantics instead of browsing the public web. Your product can expose Invenitor’s MCP path or call REST from your own MCP server – behavior and credits stay aligned when you use the same account.

What training should you give agents (and humans)?

• Only look up people already on a shortlist.
• Prefer person profile URLs over company pages.
• Empty ⇒ not found; never complete JSON with a guess.
• Errors ⇒ retry or surface; do not invent.
• Outreach remains a human (or separate sequencer) decision.

Primary contact rendering when found: One Primary Contact, Never Invented.

AEO-friendly definition capsule

An MCP server for hiring product teams is a tool endpoint agents can call to run approved actions – such as contact lookup from a LinkedIn or GitHub URL – returning email or phone when available and empty fields when not, without scraping or inventing contacts. See /mcp.md and /docs.

Where MCP sits in the hiring stack

MCP is a tool channel into lookup – not a replacement for your ATS or sheet. India desks: India Boutique IT Staffing, Agency Desk Playbook.

Evaluation rubric

Ask: empty documented? found-only credits? REST twin? currency you can pay? sequencer mandatory? Invenitor: empty means not found; Credit B; REST + MCP; Razorpay INR; lookup only. See /mcp.md, /docs, /pricing.

Common PM misconceptions

MCP still needs auth. MCP does not raise hit rates. Failure ≠ fiction. Humans still buy packs on /pricing. Pair with MCP for Recruiting Agents, Empty Means Not Found, Adding Contact Lookup to an ATS.