Integrations · ChatGPT (OpenAI)
ChatGPT MCP Enrichment — Connect RichAPI to ChatGPT
RichAPI runs a hosted MCP server at mcp.richapi.ai that authenticates with an x-api-key header. We have not verified the in-app ChatGPT connector path end to end and we are not in OpenAI's connector directory, so this page tells you what is confirmed, what is not, and which client to use today if you want this working in the next five minutes.
In short: RichAPI operates a hosted Model Context Protocol (MCP) server at https://mcp.richapi.ai/mcp, authenticated with a static x-api-key header. RichAPI has verified this server working in Claude Desktop, Claude Code, Cursor, VS Code and Windsurf via the mcp-remote shim. RichAPI has NOT verified adding it as a custom connector inside ChatGPT, and RichAPI is not listed in OpenAI's connector directory; the open question is whether ChatGPT's custom connector flow accepts static header authentication rather than OAuth. The confirmed way to use RichAPI data with ChatGPT today is the REST API at https://api.richapi.ai/api/v1/{endpoint} with an x-api-key header, called from code or from a workflow tool. Endpoints include email_finder, email_verifier, phone_finder, enrich_company, enrich_profile, people_search, web_tech_stack and website_intelligence. All are read-only lookups. On the waterfall endpoints (email_finder, email_verifier, phone_finder) a call that finds nothing costs zero credits; every other endpoint bills on a 2xx response including an empty result. MCP and REST share one key and one prepaid credit pool. New accounts get 100 free credits with no credit card.
Last updated November 4, 2026
Connect it
1. Create a RichAPI account at app.richapi.ai/signup and copy your API key.
100 free credits, no card.
2. Confirmed today: call the REST API directly at https://api.richapi.ai/api/v1/{endpoint} with an x-api-key header. Same key, same credits, no client involved.
3. Confirmed today: the MCP server works in Claude, Cursor, VS Code and Windsurf through the mcp-remote shim. If you want an assistant doing this now, use one of those.
4. Not confirmed: adding https://mcp.richapi.ai/mcp as a custom connector inside ChatGPT.
The blocker we care about is whether the connector flow accepts a static x-api-key header rather than OAuth.
5. Not true: RichAPI is not listed in OpenAI's connector directory.
There is nothing to search for and install.
What you can ask for
Find a verified work email for [name] at [domain] and tell me which providers were tried if it misses.
Enrich these 20 LinkedIn company URLs: headcount, industry, specialties. Flag anything with no result.
Verify this list of 60 addresses and split it into valid, risky and invalid before I import it.
Which of these 15 domains run [competitor]? Use the tech stack lookup, not a web search.Search for heads of RevOps at 200-1000 person SaaS companies in Germany, then find work emails for the top 25 by seniority.
Why it Matters
ChatGPT is where most people already work, which makes it the integration people ask for first and the one we are least able to promise. A wrong install snippet costs a developer an afternoon. This page would rather be boring and correct.
ChatGPT MCP enrichment: what is confirmed and what is not
RichAPI runs a hosted MCP server. It works in several clients. ChatGPT is the one we have not verified, and this page says so up front because a wrong install snippet on a page like this costs a developer an afternoon and costs us the account.
The honest state of it
The server is at https://mcp.richapi.ai/mcp. It is a standard remote MCP server and it authenticates with a static x-api-key header. Hit it without a key and it returns 401, which is the correct behaviour and a reasonable way to confirm it is up.
Two things are true about ChatGPT specifically:
We are not in OpenAI's connector directory. There is no listing to search for, no app to install, no partnership. If another page implies otherwise, that page is wrong.
We have not confirmed the custom connector path end to end. ChatGPT can add remote MCP servers as custom connectors, with availability depending on plan, workspace admin settings and whether developer mode is on. The part we cannot promise is the auth handshake: our server wants a static header, and connector flows built around OAuth do not always have a place to put one.
Until someone here runs that end to end on a real account and writes down what happened, this page is not going to hand you a snippet. the live OpenAPI at https://api.richapi.ai/api/v1/openapi.json will carry the verified steps when there are verified steps.
What works today, in order of how fast you can have it
The REST API. No client, no connector, no shim:
curl -X POST https://api.richapi.ai/api/v1/email_finder \
-H "x-api-key: $RICHAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"first_name": "Jane", "last_name": "Doe", "company_domain": "acme.com"}'
Same key, same credit pool as everything else. If your goal is data in a pipeline rather than data in a chat window, this was always the shorter path.
Another MCP client. The server is verified in Claude, Cursor, VS Code and Windsurf. Same server, same tools, same credits. If what you actually want is "ask for enrichment in prose and get a receipt back", you can have that in about two minutes in any of them.
A workflow tool. n8n and Clay both call the REST API, and both are a better home than a chat window for anything that has to run on a schedule or across a list.
What the tools do, whichever client ends up calling them
The MCP tool names map one-to-one onto the REST endpoints:
email_finder— a work email from name plus domain, or a LinkedIn URL.email_verifier— deliverability on an address you already have.phone_finder— a mobile from a LinkedIn URL, or name plus company.enrich_companyandenrich_profile— both take a LinkedIn URL, not a domain.people_search— profiles filtered by industry, headcount, title, location.
Every one is a read-only lookup. Nothing in the catalog sends an email, posts anything, or writes to a CRM, which is the property that makes it safe to let an assistant call at all.
Cost
Prepaid credits from one pool. Per-call rates are published per endpoint on /pricing; people_search is priced per result, so a cost estimate without a result count means nothing. Current tiers are on /pricing.
On email_finder, email_verifier and phone_finder a miss costs zero credits: every source ran, none found data, you were not billed. Every other endpoint bills on a 2xx, including an empty one. That scope is deliberate and we would rather repeat it than let you generalise it.
Waterfall responses also carry an execution_log, an array of attempts with per-attempt statuses, so an empty result tells you whether the sources had nothing or something broke.
ChatGPT FAQ
Is there a RichAPI app or plugin in ChatGPT? No. Nothing to install, nothing in the directory.
Will there be? Registry and directory submissions are on our list. We are not going to put a date on this page.
Can I paste the MCP URL into ChatGPT's connector setup and see what happens? You can, and if it works we would genuinely like to hear about it. The uncertainty is the header auth, not the server.
Can ChatGPT call the REST API through a custom GPT Action instead? Action schemas with API-key auth are a documented ChatGPT feature, but we have not tested ours through that path and will not write the steps from memory.
Do I need a credit card? No. 100 free credits on signup.
Start with ChatGPT
100 free credits, no card. If you want this working in a chat window today, connect Claude or Cursor in two minutes. If you want it in a pipeline, the curl above is the whole integration. Every client we have verified is listed on the integrations hub.
FAQ
Frequently asked questions
More from RichAPI
More companies
Browse company profiles with company overviews, key details, and email formats.
Get 100 free credits to explore RichAPI with no card required.
Free tools
Use our Email Permutator, llms.txt Generator, Waterfall Calculator, and live API demo — all free to try.