openpeoplerouter
OfficialOpenPeopleRouter is an MCP server/CLI that finds and enriches people and companies by routing requests across your own configured data providers and API keys.
Search for people by description, role, company, location, skills, name, or source page.
Search for companies by name, domain, industry, technology, country, or free text.
Enrich a person or company from identifiers such as email, LinkedIn, GitHub, Scholar, domain, or website.
Find or verify contact details, including work email and phone when requested.
Read public profiles across social and developer platforms.
Resolve one person's profiles across multiple platforms into a single identity set.
Find where an image appears on the web and which profiles may belong to that person.
List unified capabilities and configured providers.
Discover, inspect, and call lower-level provider endpoints when unified tools are insufficient.
See routing details such as what was tried, ignored filters, failures, and raw provider data.
Run locally via CLI or as an MCP stdio/HTTP server, with provider charges billed directly to your accounts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@openpeoplerouter find contact info for the CTO of Acme Corp"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OpenPeopleRouter
An open-source MCP server that finds people and companies through the data providers you already pay for. Bring your own keys; nothing goes through a middleman.
7 job tools an agent can call without knowing any provider:
find_people,enrich_person,find_contact,verify_email,find_companies,enrich_company,read_profile.68 providers, 2,200+ operations — B2B people and company data, email finding and verification, phone data, research and developer profiles, social platforms, web search and scraping. See docs/providers.md.
Your keys, your bills. Each provider bills your own account. Keys stay in your environment and are scrubbed from every response.
One YAML file per provider. Adding one needs no Python.
中文说明 · Provider list · Provider file format · How routing works
Run it
Requires Python 3.11+ and uv.
git clone https://github.com/DINQ-labs/openpeoplerouter && cd openpeoplerouter
uv sync
cp .env.example .env # fill in only the providers you use
uv run openpeoplerouter providers
uv run openpeoplerouter run find_people audience=researchers "keywords=protein folding" limit=5 # works with no key
uv run openpeoplerouter run find_contact "full_name=Jane Doe" company_domain=example.com # needs an email provider's keySeveral sources work with no key at all (OpenAlex, ORCID, Crossref, Wikidata, GitHub, Hugging Face, Semantic Scholar, Stack Exchange, Bluesky, Jina), so the server is useful before you configure anything.
In an MCP client
The default transport is stdio:
{
"mcpServers": {
"openpeoplerouter": {
"command": "uv",
"args": ["--directory", "/absolute/path/to/openpeoplerouter", "run", "openpeoplerouter", "serve"]
}
}
}Over HTTP, for a server you share with your own tools:
OPENPEOPLEROUTER_TOKEN=change-me uv run openpeoplerouter serve --transport http --host 0.0.0.0 --port 8080Clients then connect to http://host:8080/mcp with Authorization: Bearer change-me.
The server refuses to listen beyond localhost without a token, because it spends
your provider credits. docker compose up does the same in a container.
Related MCP server: Nous MCP Server
Tools
Tool | What it does |
| People by title, employer, place, skills or a description. |
| One person from an email, LinkedIn URL, phone, or name with employer. |
| Work email and phone for one person. |
| Whether an address can receive mail. |
| Companies by industry, place, size, technology or a description. |
| One company from its domain, name or LinkedIn page. |
| One public profile on LinkedIn, X, Instagram, TikTok, YouTube, GitHub, Bluesky, Threads and more. |
| What is configured, and which variable each provider reads. |
| Find any provider operation by words. |
| Its parameters, price and docs. |
| Run it with the provider's own parameters and get the raw response. |
Every job result lists what was tried: the operation, whether it answered, how
long it took, and the error if it failed — so an agent can tell "nobody matched"
from "the key was rejected" from "out of credit". A search also lists as ignored
any filter that none of the providers it tried could apply, so the rows are not
read as filtered by it.
Choosing providers
# Only these providers may be called (default: every provider with a key, plus keyless ones)
OPENPEOPLEROUTER_PROVIDERS=hunter,apollo,openalex
# Try these first, in this order; the rest follow, cheapest first
OPENPEOPLEROUTER_ORDER=apollo,hunterA job call can also pass providers: ["pdl", "lusha"] to use only those, in that
order, and raw: true to get each provider's full record next to the mapped
fields.
Command line
openpeoplerouter serve [--transport stdio|http] [--host] [--port]
openpeoplerouter providers [--markdown]
openpeoplerouter check # validate every provider file
openpeoplerouter run <job> key=value ... # run a job once
openpeoplerouter call <provider.operation> key=value ...Values that parse as JSON are sent as JSON (limit=5, filters='{"x":1}').
Adding a provider
Write src/openpeoplerouter/providers/<id>.yaml as described in
docs/provider-format.md. For APIs with an OpenAPI
document, scripts/from_openapi.py drafts the operations. Run
openpeoplerouter check and uv run pytest, then open a pull request.
Provider definitions describe each provider's public API documentation. Most routes were checked against those documents and response schemas; keyless and test-key providers were also called live. If a provider changed its API, the fix is usually one line in its file.
Responsible use
You are responsible for using each provider within its terms and the law where you and the people you look up are, including data-protection rules such as the GDPR and CCPA. Some providers carry their own restrictions (for example, phone data that is not a consumer report and must not be used for credit, insurance, employment or housing decisions).
License
Apache-2.0
Available Tools
12 toolscall_toolB
Execute a discovered endpoint using your provider key. Provider charges may apply.
Inputs: endpoint_id (required), args. Returns: object
capabilitiesA
List unified capabilities, inputs and configured providers. No provider request.
Inputs: no named parameters. Returns: object
companies_enrichB
Enrich a company from its domain, name, LinkedIn URL or a work email — treg picks the provider and names the one that served Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: name, email, domain, vendor, +4 more. Returns: object
companies_searchA
Find companies by a free-text description, a name, an industry, a technology they use, or a domain — provider-native rows in companies Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: q, name, limit, domain, +5 more. Returns: object
endpointA
Inspect an endpoint's arguments, provider documentation and availability before calling it.
Inputs: endpoint_id (required). Returns: object
find_toolA
Find provider endpoints when unified capabilities cannot meet the need. Searches API metadata, not people.
Inputs: query (required), limit. Returns: object
people_contact_findA
How to reach one person: their work email, their phone when you ask for it, and whether an address you already hold is real. Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: want, email, domain, vendor, +8 more. Returns: object
people_enrichB
Everything known about one person: title, employer, location, profile links. Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: email, domain, vendor, company, +9 more. Returns: object
people_from_imageB
Where a photo appears on the web, and who it is: pages carrying the exact image, and the social profiles among them. Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: vendor, image_url, waterfall. Returns: object
people_identity_resolveA
Identity resolution: one person's profiles across platforms, resolved into a single set. Give any one of them — LinkedIn, GitHub, X, Hugging Face, Scholar, an email — and get the rest. Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: email, domain, vendor, company, +10 more. Returns: object
people_searchA
A list of people you did not have: from a description — a role, a company, a place — or from a source that names them, such as a repository, a paper, a Scholar profile or a company page. Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: q, limit, title, vendor, +9 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
The people_* family is mostly distinct, but social_profile, people_enrich, and people_identity_resolve all accept a single person identifier and return profile-related data, so an agent needs to read descriptions carefully. The meta tools (find_tool, endpoint, call_tool) are clearly separated.
Most domain tools follow a clear people_/companies_ prefixed snake_case pattern. Minor deviations include social_profile lacking the people_ prefix and meta tools mixing noun forms (capabilities, endpoint) with verb_noun forms (find_tool, call_tool).
12 tools is well within the ideal range for a multi-provider data router: 8 domain operations plus 4 discovery/execution tools. Each tool has a clear role, and none feel redundant.
People workflows are comprehensively covered: search, social profile, enrich, identity resolution, contact finding, and image-based lookup. Companies have search and enrich, and the capabilities/find_tool/endpoint/call_tool layer prevents dead ends by allowing access to provider-specific endpoints.
Maintenance
Related MCP Connectors
Search people and companies, enrich profiles, and find email and phone over MCP.
Real-time B2B professional profiles, company firmographics & org data MCP. OAuth or API key.
Real-time B2B professional profiles, company intelligence & jobs hosted MCP. OAuth or API key.
Unlimited B2B Contact Data for AI Agents, Starting from $29/mo. Remote MCP server with eight tools: search_people, search_companies, enrich_person, enrich_company, verify_email, scrape_jobs, scrape_company, get_usage. Results include match reasons, email verification status and checked_at dates. Sign in with OAuth. Flat pricing with a free tier of 1,000 records.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables B2B research by finding verified work emails, extracting contacts, detecting tech stacks, and profiling DNS and SaaS, all through a suite of MCP tools.-
- AlicenseNot gradedqualityBmaintenanceProvides a context graph for GTM teams, centralizing data from multiple tools into unified person and company records, and offers MCP tools to retrieve account context, full entity details, and filtered queries.14 npm10AGPL 3.0

Signaliz MCPofficial
FlicenseNot gradedqualityDmaintenanceProvides MCP clients with 60+ APIs for B2B data enrichment, lead generation, email verification, company intelligence, and agentic GTM workflows.-- FlicenseNot gradedqualityNot gradedmaintenanceEnables multi-provider waterfall data enrichment for B2B prospects, firmographics, and verified decision-maker corporate emails via MCP.-
social_profileA
One person's public profile on whatever platform a handle belongs to: LinkedIn, X, Instagram, TikTok, YouTube, GitHub and the rest. Give a profile URL, or a platform and a handle. Use vendor to pin a provider. Returns outcome, normalized output, raw provider data and _meta.tried. Provider API charges are billed directly to your provider account.
Inputs: handle, vendor, platform, waterfall, +1 more. Returns: object