Enrich and search people and companies, resolve identities, and enrich IP addresses. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"peopledatalabs": {
"url": "https://peopledatalabs.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"peopledatalabs": {
"type": "http",
"url": "https://peopledatalabs.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your People Data Labs API key.
Find it at dashboard.peopledatalabs.com → API Keys. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your People Data Labs API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the People Data Labs connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
pdl_person_enrich | read | Enrich a person Find the single best-matching person profile for a set of identifying attributes (name, email, phone, profile URL, company, etc.). Returns one record plus a likelihood score (1-10), or a 404 'no match' body. Use uniquely-identifying inputs for best results. API: GET /person/enrich. |
pdl_person_identify | read | Identify a person Given broad, possibly-ambiguous attributes about a person, return up to 20 strongly-related profiles ranked by match score. Sits between enrich (1:1) and search (open-ended) — ideal when you can't uniquely resolve someone. API: GET /person/identify. |
pdl_person_search | read | Search people Search the full PDL Person Dataset with an Elasticsearch query object OR a SQL string over the Person Schema (e.g. everyone with job_title_role='engineering' at a company). Returns matching profiles sorted by completeness; paginate with scroll_token. Each returned record costs 1 credit. API: POST /person/search. |
pdl_company_enrich | read | Enrich a company Find the single best-matching company record. Requires a non-ambiguous input — name OR website OR ticker OR profile (website/ticker/profile resolve more reliably than name). Returns firmographics (industry, size, location, etc.) or a 404 'no match' body. API: GET /company/enrich. |
pdl_company_search | read | Search companies Search the full PDL Company Dataset with an Elasticsearch query object OR a SQL string over the Company Schema (e.g. all SaaS companies with 50-200 employees in the US). Paginate with scroll_token. Each returned record costs 1 credit. API: POST /company/search. |
pdl_ip_enrich | read | Enrich an IP address Enrich an IP address with its location, company, and (optionally) associated person data via a 1:1 match against PDL's IP dataset. API: GET /ip/enrich. |
pdl_autocomplete | read | Autocomplete search values Get suggested values for a search field along with the number of available records for each — useful for building valid Person/Company Search queries. Free on all plans. API: GET /autocomplete. |
pdl_job_posting_search | read | Search job postings Search PDL's Job Posting Dataset (millions of active & historical postings sourced from company career pages) with an Elasticsearch query object OR a SQL string. Beta — may require plan access (HTTP 403 if not enabled). Each returned posting costs 1 credit. API: POST /job_posting/search. |
peopledatalabs_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
peopledatalabs_request_feature | Request a missing feature Tell usefulapi that the user needs something the People Data Labs tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
peopledatalabs_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED People Data Labs tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
peopledatalabs_cancel_subscription | Cancel the Pro subscription Cancel the caller's People Data Labs Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run peopledatalabs_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this People Data Labs server only. Subscribe with peopledatalabs_upgrade (it returns a Stripe Checkout link). Cancel any time with peopledatalabs_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running peopledatalabs_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by People Data Labs. The server calls the People Data Labs API with your own People Data Labs access, so it sees only the data that your account can see.
The login page asks for your People Data Labs API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your People Data Labs API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the People Data Labs API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in People Data Labs.
All 8 People Data Labs tools are marked read-only.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this People Data Labs server only. Run peopledatalabs_usage_status to see how many calls you used.
Ask the AI to run peopledatalabs_upgrade: it returns a Stripe Checkout link. To cancel, run peopledatalabs_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with peopledatalabs_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.