Key takeaways:
- FullEnrich MCP connects Claude, ChatGPT and other clients to a waterfall that queries 20+ enrichment providers in sequence, over OAuth with no API key to manage.
- Search is free to explore. You get the first 10 results plus the total count at no cost, and credits only apply when you export, at 0.25 per contact or company.
- Enrichment costs the same through MCP as through the app or API, and the assistant is designed to confirm with you before spending anything.
- Credits are weighted by data type: a work email costs 1 credit, a personal email 3, and a mobile number 10.
Most enrichment tools charge you money to find out whether they can help you at all. FullEnrich does not, and that single pricing decision is the most interesting thing about its MCP server.
You can run a search, see how many people match and preview the first ten, then refine your filters as many times as you like without spending a credit. Payment starts when you export.
This review covers the tool surface, the setup, the credit mechanics and the limits. Outreach is our patch rather than enrichment, and we maintain a connector for it, so we will be clear about which half is which.
What FullEnrich MCP Is
FullEnrich MCP is the company’s own Model Context Protocol connector, using the vendor-neutral standard that lets assistants reach software they did not ship with. It puts FullEnrich’s contact search and enrichment in front of any compatible client.
The underlying product is a waterfall. Rather than querying one data vendor and accepting whatever comes back, FullEnrich runs a request through more than 20 providers in sequence until verified data is found, which the company reports as an 80%+ fill rate. That architecture is the reason to use it over a single-source tool, and the MCP server inherits it unchanged.
Authentication is OAuth. You are redirected to sign in with your FullEnrich account in the browser, you authorize access, and the session is stored by the client. No API keys and no manual configuration are required for the supported assistants.
That choice puts FullEnrich on the safer side of a line this category is still arguing over. Several outreach and data vendors still ask you to paste a long-lived key into a config file, and a few pass it in the URL. An OAuth session that the client refreshes on your behalf leaves nothing sitting in a text file for someone to find later.
The waterfall is also what separates this from the single-source email enrichment APIs that dominate the cheaper end of the market. Those return nothing when their one database has a gap, which reads to a rep as “this person has no email” rather than “this vendor could not find it.” Querying twenty providers in sequence turns most of those misses into hits, and it is the reason a waterfall costs more per record than a single lookup.
What You Can Actually Do
Three jobs, and they are designed to run in that order.
| Job | What you ask for | Cost |
| Search people and companies | Natural language or filters across role, company, industry, location and company size | Free preview: first 10 results plus total count |
| Enrich contacts | Professional emails, phone numbers and more, one contact or a full list in batch | Credits, weighted by data type |
| Export results | CSV or JSON, ready for a CRM or outreach tool | 0.25 credits per contact or company |
FullEnrich’s own example prompts show the intended shape: “Find me marketing directors at software companies in the US,” then “Enrich these 50 contacts with work emails and phone numbers,” then “Export these results as a CSV.”
Batch enrichment is the part that makes the FullEnrich MCP server more than a lookup toy. Asking for fifty contacts in one instruction is a normal request rather than an abuse of the interface, and it is the shape most prospecting work actually takes.
How Credits Work
This is the section worth reading twice, because the model is genuinely different from its competitors and the difference is in your favor.
Search is exploratory and free. Running a search returns the first ten results and the total count at no cost. FullEnrich’s stated reasoning is that you might need three or four attempts to get filters right, and none of that should cost anything. Credits only apply when you pull actual data out.
Export is where you pay, at 0.25 credits per contact or company, the same rate as the API. There is no MCP surcharge.
Enrichment is priced by what you ask for, which is the part people miscalculate. The three field types sit an order of magnitude apart: work addresses at the base rate, personal addresses at three times that, mobile numbers at ten. Requesting phone numbers across a large list therefore costs roughly ten times the same list in work emails, so the shape of your request matters more than its size.
At the published rate of around $0.055 per credit on a 1,000-credit monthly plan, that puts a work email near six cents and a mobile number near fifty-five. FullEnrich starts you with 50 free credits and no credit card, which is enough to test real queries against your own market before deciding anything.
One behavior is designed in and worth relying on: the assistant confirms with you before running enrichment, so nothing gets charged without your go-ahead.
Compare that against the norm before deciding it is unremarkable. Most credit-metered tools charge for the attempt, which quietly penalizes exploration and pushes teams to write over-broad filters so that one expensive query has to do.
Charging on export instead means the cost lands on data you have decided you want, and it changes how people actually use the tool. It is the most buyer-friendly model we have seen across the AI prospecting tools we have reviewed this year.
How to Set Up FullEnrich MCP
Setup is short because OAuth does most of the work for you.
Claude and ChatGPT
Both use a custom connector and a browser sign-in, so the sequence is the same in either client.
- Open your assistant’s settings and go to the connectors section.
- Add FullEnrich as a custom connector.
- Complete the browser sign-in with your FullEnrich account and authorize access.
FullEnrich publishes separate step-by-step walkthroughs for Claude and ChatGPT, which are worth following rather than improvising, since connector menus move between client versions.
Claude Code and Other IDEs
Developer clients take the server through an MCP configuration block rather than a settings screen. The same OAuth flow then runs on first use.
Optional: The Skills Library
FullEnrich maintains an open-source library of skills that add higher-level guidance on top of the MCP tools, covering smarter confirmation flows, better search strategies and workflow templates.
The skills are genuinely optional and the server works without them. They matter most for repeatable multi-step prospecting, and FullEnrich also points to them as the fix if your assistant is skipping the confirmation step before enrichment.
If Something Goes Wrong
FullEnrich’s documented smoke test is the fastest diagnostic in this whole category: ask “Check my FullEnrich credits.” If that returns a number, the connection is fine and the problem is your prompt rather than your setup.
Two other documented quirks are worth knowing. Some clients do not auto-close the sign-in tab, so close it manually after the confirmation page appears. And if enrichment runs without asking first, being explicit (“show me the results before enriching”) restores the intended preview-confirm-enrich order.
Thin results usually mean over-tight filters rather than thin data. FullEnrich’s guidance is to broaden the criteria and use standard industry and job-title language, then narrow down, which is the opposite of how most people write a first query.
Non-standard titles are the common culprit, since a database indexes what companies actually publish rather than what a rep would call the role. The same discipline applies across B2B data APIs generally, where filter vocabulary decides hit rate more often than coverage does.