search_peopleLABSCO SUMMARY
A working demo key means you can judge the results before you pay.
Most search APIs make you register before you can see whether the matches are any good; here the demo key returns real result structure with the values masked, so the evaluation costs nothing. The two search tools split cleanly — one hunts for individuals, the other for companies and then the people inside them — which is the difference between recruiting and prospecting.
What it is
The MCP interface to Pearch.AI, a natural-language search over people and over B2B companies and leads. Pearch recommends its hosted server — sign in with Google or send your Pearch API key — and it also runs locally over stdio from a clone.
What you get
search_peopletakes a request like "software engineers in California with 5+ years Python" and returns candidates with optional insights and profile scoringsearch_company_leadsfinds companies and the contacts inside them — "AI startups in SF, 50–200 employees" plus "CTOs and engineering managers"search_peoplealso follows up on an existing thread, andget_profileenriches a single person from a LinkedIn slug or email- The demo key
test_mcp_keyreturns masked sample results with no sign-up, so you can see the shape of the output first - Remote access over Streamable HTTP at https://mcp.pearch.ai/mcp, with
GET /healthfor liveness
Requirements
For the hosted server there is nothing to install: add https://mcp.pearch.ai/mcp and sign in with the Google account that matches your Pearch account, or send your API key as a Bearer header. To run it locally, clone the repository, pip install -r requirements.txt (Python 3.10+), then fastmcp install claude-desktop pearch_mcp.py --env PEARCH_API_KEY=test_mcp_key. PEARCH_API_KEY holds either the demo key or a real key from the Pearch dashboard; PEARCH_API_URL overrides the base URL, which defaults to https://api.pearch.ai.
Setup effort
One command, then sign in — claude mcp add --transport http pearch https://mcp.pearch.ai/mcp, then approve the OAuth sign-in
USE CASES
01
Sourcing candidates by description
Describe the role in a sentence instead of building a boolean string.
02
Building a prospect list
Find companies matching a profile, then the roles you want to reach inside them.
03
Narrowing a search that came back too wide
Follow up on the same thread rather than re-running a fresh query.
04
Deciding whether it is worth a key
Run the demo key first and look at the masked results before signing up.
4 tools
Listed in project docs. Your client may show a different list.
search_company_leadsget_profileget_user_infoBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- A Pearch.ai account for full results — the demo key test_mcp_key returns masked sample results with no sign-up
- Local stdio route only: Python 3.10+ and pip install -r requirements.txt (or pip install fastmcp)
INSTALLATION
Connect your client
Server setup
Setup
TERMINAL
git clone https://github.com/Pearch-ai/mcp_pearch
cd mcp_pearch
pip install -r requirements.txt
fastmcp install claude-desktop pearch_mcp.py --env PEARCH_API_KEY=test_mcp_keyclaude mcp add
TERMINAL
claude mcp add --transport http pearch https://mcp.pearch.ai/mcpHosted endpoint
ENDPOINT URL
https://mcp.pearch.ai/mcpAdd this hosted endpoint to your MCP client, then sign in.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"Pearch.ai": {
"command": "python",
"args": [
"<YOUR_PATH_TO_MCP_PEARCH>/pearch_mcp.py"
],
"env": {
"PEARCH_API_KEY": "test_mcp_key"
}
}
}
}Local route: <YOUR_PATH_TO_MCP_PEARCH> is the folder the clone step creates. test_mcp_key returns masked sample results; a key from the Pearch.ai dashboard gives full results.
Cursor
CURSOR · TERMINAL
fastmcp install cursor pearch_mcp.py --env PEARCH_API_KEY=test_mcp_keyLocal route: run this inside the mcp_pearch clone. test_mcp_key returns masked sample results; your dashboard key gives full results.
Cursor — remote
CURSOR — REMOTE · JSON
{
"mcpServers": {
"Pearch.ai": {
"url": "https://mcp.pearch.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:PEARCH_API_KEY}"
}
}
}
}Hosted server with an API key: set PEARCH_API_KEY to your Pearch API key, or to test_mcp_key for masked sample results. Leave the headers out to sign in with Google over OAuth instead.
