Pearch-ai/mcp_pearch

MCP server for Pearch.AI: natural-language search over **people** and **companies/leads** (B2B). Use it from Claude, Cursor, VS Code, or any MCP-compatible client.
> Evaluating AI Recruitment Sourcing Tools by Human Preference
Tools
| Tool | Description |
|------|-------------|
| **search_people** | People search with a natural-language query or structured search_requirements. Supports fast/pro/superfast search types, contact reveal & contact filters, real-time profile refresh, insights, and thread-based pagination/follow-ups. |
| **search_company_leads** | Find companies and leads/contacts within them (B2B). Example: company *"AI startups in SF, 50–200 employees"* + leads *"CTOs and engineering managers"*, with optional personalized outreach messages. |
| **get_profile** | Look up and enrich a single person by LinkedIn slug or email (contact reveal, real-time refresh, GitHub enrichment). |
| **get_user_info** | Authenticated user info: email, remaining credits, pricing plan. Free. |
Structured people search
Pass search_requirements to search_people when you already have a list of criteria:
- search_requirement: required, non-empty text. Keep each criterion short and self-contained.
- must_have: true for mandatory criteria, false for nice-to-have preferences (the default).
The list must contain at least one requirement. query is optional when using
search_requirements; if both are supplied, the API gives search_requirements
precedence. See the Pearch search API contract.
Both inputs support the same search options: search type, insights and scoring,
profile refresh, contact reveal and filters, strict filtering, low-confidence
results, time budget, pagination, response fields, profile exclusions, and free
masked results. Search-type restrictions are the same for both inputs; for example,
superfast does not support insights, profile scoring, or high freshness.
For pagination, send the returned thread_id with limit and optionally offset,
omitting query and search_requirements. To change criteria, start a new search
without thread_id. Existing query calls and thread follow-ups are still forwarded
as before; the API decides which follow-up parameters it accepts.
custom_filters is not exposed by this MCP server. Express criteria in query or
search_requirements instead.
Remote server (recommended)
The hosted server lives at https://mcp.pearch.ai/mcp and supports two auth schemes at once:
OAuth (no key handling)
Add the server without any headers — OAuth-capable clients (Claude, Cursor, VS Code) discover the flow automatically and open a Google sign-in. Sign in with the Google account whose email matches your Pearch account:
Your searches bill credits against your own Pearch account. If your Pearch account has no API key yet, create one first in the Pearch.ai Dashboard.
API key
Pass the same Pearch API key as api.pearch.ai:
Use **test_mcp_key** for **masked (sample) results** — no sign-up required.
Local (stdio) installation
Requires **Python 3.10+** and pip install -r requirements.txt (or pip install fastmcp).
Claude Desktop / Claude Code