Enrichments.io

Enrichments runs a Model Context Protocol server, so an agent in Claude, ChatGPT, Cursor or Codex can find and enrich people and companies as ordinary tool calls — no glue code, no SDK. It authenticates with the same API key as the REST API and bills against the same credit balance, charged only for data actually returned.

The discovery document is the RFC 9728 protected-resource metadata for the endpoint. It is served for clients that look for it; nothing about connecting requires you to fetch it yourself.

Small requests answer inline. Larger ones are queued: the tool returns a job id withresults: null, and the agent pollsget_jobuntildoneis true. Polling is free.

emailis never returned unless it is named infields. It is the one expensive field and it is billed per address actually found, so the intended shape of a run is: discover without it, decide which rows you want, then make oneenrich_peoplecall asking for it on exactly those rows.

People fields:email,linkedin_url,title,seniority,department,location,country,company,company_domain,headline,phone,company_profile.

Company fields:company,company_domain,linkedin_url,location,country,headline, plus firmographics that ride along with any company row.

Each field is described on theAPI reference, which is generated from the same schemas these tools validate with.

{ "mcpServers": { "enrichments": { "url": "https://www.enrichments.io/api/mcp", "headers": { "Authorization": "Bearer ek_live_xxxxxxxxxxxxxxxxxxxx" } } } }

{ "mcpServers": { "enrichments": { "command": "npx", "args": [ "-y", "mcp-remote", "https://www.enrichments.io/api/mcp", "--header", "Authorization: Bearer ek_live_xxxxxxxxxxxxxxxxxxxx" ] } } }

Declare the server inline on a Responses API request and pass the key inauthorization. Deep Research calls onlysearchandfetch, which this server registers with the shapes OpenAI documents.

{ "model": "gpt-5", "tools": [ { "type": "mcp", "server_label": "enrichments", "server_url": "https://www.enrichments.io/api/mcp", "authorization": "Bearer ek_live_xxxxxxxxxxxxxxxxxxxx", "require_approval": "never" } ], "input": "Find heads of platform engineering at German fintech companies." }

Adding the server through the ChatGPT app's connector dialog is not supported yet: that flow expects the server to authenticate over OAuth, and the authorization-code flow is not available here. Use a client that can send a fixedAuthorizationheader.

Codex reads its servers from~/.codex/config.toml. The stdio form works on every version; a build with direct remote Streamable HTTP support can use the endpoint and header instead.

[mcp_servers.enrichments] command = "npx" args = [ "-y", "mcp-remote", "https://www.enrichments.io/api/mcp", "--header", "Authorization: Bearer ek_live_xxxxxxxxxxxxxxxxxxxx", ]

- Mobile numbers are available as the phone field and billed per number found. 15 common aliases — mobile, cell, direct dial, telephone and the rest — resolve to it rather than failing. Unlike an email address a number carries no deliverability verdict, because nothing checks a phone the way a mailbox can be checked.
- A phone number being available is not advice that it is lawful to call. Obligations under TCPA, DNC registries and local consent rules are the caller's.
- The field catalogue is closed. A request for anything outside the 12 people fields is a validation error, not an empty column.
- Email addresses are work addresses found from public sources. Personal contact details are not part of the catalogue.
- Enrichment is live rather than a licensed static database, so the same query can legitimately return different data tomorrow.

The refusals are validation errors at the edge with a sentence explaining them, not empty columns — an agent that asks for a phone number is told plainly that there is no phone field, which is what stops it retrying in a loop.

https://www.enrichments.io/api/mcp. It speaks the Model Context Protocol over Streamable HTTP and authenticates with an Enrichments API key sent as an Authorization: Bearer header.

Prices per delivered unit are onpricing; the REST contract is on theAPI reference.

Chat with any brand's Meta (Facebook/Instagram) ads inside Claude — research a competitor's ad library, surface their longest-running winners, extract hooks/formats, and clone winning ads for your own brand.