enrichmentapi-mcp

Give Claude (or any other AI assistant that speaks MCP) the ability to look people and companies up for you — enrich a profile, find and verify a work email, turn a company name into a domain, pull funding history, and more — just by asking in plain language.

This package is a small connector built on the Model Context Protocol (MCP), the open standard that lets AI assistants use external tools. Once it's connected, your assistant can call EnrichmentAPI on your behalf. You never have to write code or make HTTP requests yourself.

Table of contents

1. What you can do with it
2. The tools it adds
3. Step 1 — Get your EnrichmentAPI API key
4. Step 2 — Pick how you want to run it
5. Step 3 — Connect it to your assistant
6. Step 4 — Start using it
7. Troubleshooting
8. FAQ
9. License

What you can do with it

After it's connected, you can ask your assistant things like:

• "Find the website domain for the company Stripe."
• "Enrich this profile: satyanadella"
• "What's a likely work email for Jane Doe at acme.com, and is it deliverable?"
• "Who is behind the email [email protected]?"
• "List some employees at Notion."
• "Show me Figma's funding rounds."

Your assistant reads your request, picks the right tool, fills in the details, calls EnrichmentAPI, and shows you the result — all in the same conversation.

The tools it adds

Ten tools, one per EnrichmentAPI endpoint:

| Tool | What it does | Typical input | |---|---|---| | enrichmentapi_person | Turns a profile into structured data (name, headline, experience, education, skills, …) | A profile URL or handle | | enrichmentapi_company | Turns a company page into structured company data | A company page URL or name | | enrichmentapi_employee_finder | Finds people who work at a given company | A company name or domain | | enrichmentapi_email_finder | Works out the most likely work email for a person | A full name + company domain | | enrichmentapi_verify_email | Checks whether an email address is real and can receive mail | An email address | | enrichmentapi_reverse_email | Finds the person an email address belongs to | An email address (or a name) | | enrichmentapi_company_to_domain | Resolves a company name to its website domain | A company name | | enrichmentapi_company_funding | Returns a company's funding and investment history | A company name or domain | | enrichmentapi_post_enrichment | Turns a post into structured data | A post URL | | enrichmentapi_image_to_person | Tries to identify a person from a photo | An image URL |

This connector is read-only — it only looks things up. It can't change anything in your EnrichmentAPI account, your billing, or your CRM.

Step 1 — Get your EnrichmentAPI API key

An API key is a secret password that proves the requests are coming from your account. You need one before anything else will work.

1. Go to https://api.enrichmentapi.io/login.
2. Sign in, or create a free account if you don't have one yet.
3. Once you're signed in you land on your dashboard. Near the top you'll see a card labelled "YOUR API KEY".
4. Click the eye icon to reveal the key, then click Copy.
5. Keep it somewhere safe for the next steps. Treat it like a password — don't paste it into public chats, screenshots, or commits.

Need to change it later? Go to Account → API Key (https://api.enrichmentapi.io/account-info). From there you can rotate or regenerate the key at any time. If you regenerate it, remember to update it in your assistant's config too.

Throughout the rest of this guide, wherever you see YOUR_KEY, replace it with the key you just copied.

Step 2 — Pick how you want to run it

There are two ways to connect. They do the same thing — pick whichever suits you.

| | Hosted | Local (npx) | |---|---|---| | Anything to install? | No | Node.js 20.12 or newer | | How it runs | We host the connector; your assistant talks to it over the internet | The connector runs on your own computer | | Best for | The quickest start, or clients that only support remote servers | People who prefer nothing leaving their machine except the API calls themselves | | Your API key | Sent as a header with each request; nothing is stored on our side | Stays in your local config file |

If you're not sure, start with Hosted.

Step 3 — Connect it to your assistant

Pick your assistant below, then follow the block for the option you chose in Step 2.

Claude Code (the CLI)

Hosted:

claude mcp add --transport http enrichmentapi https://mcp.enrichmentapi.io \
  -H "X-EnrichmentAPI-Key: YOUR_KEY"

Local (npx):

claude mcp add enrichmentapi -e ENRICHMENTAPI_KEY=YOUR_KEY -s user -- npx -y enrichmentapi-mcp

-s user makes it available in every project. Use -s local instead to add it only to the current folder.

Check it was added:

claude mcp list

Claude Desktop (the app)

You'll edit a file called claude_desktop_config.json. You can open it from the app: Settings → Developer → Edit Config. Or find it directly:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

If the file is empty or doesn't exist, create it with the whole block below. If it already has content, add just the "enrichmentapi" entry inside the existing "mcpServers" object.

Hosted:

{
  "mcpServers": {
    "enrichmentapi": {
      "url": "https://mcp.enrichmentapi.io",
      "headers": {
        "X-EnrichmentAPI-Key": "YOUR_KEY"
      }
    }
  }
}

Local (npx):

{
  "mcpServers": {
    "enrichmentapi": {
      "command": "npx",
      "args": ["-y", "enrichmentapi-mcp"],
      "env": {
        "ENRICHMENTAPI_KEY": "YOUR_KEY"
      }
    }
  }
}

Save the file when you're done.

Any other MCP client

Point it at https://mcp.enrichmentapi.io using the Streamable HTTP transport, and send your key in the header X-EnrichmentAPI-Key: YOUR_KEY. There's no login or session to set up — every request is independent and tied to whichever key sent it. Always use https://, not http://.

Step 4 — Start using it

1. Restart your assistant so it picks up the new connector:
   • Claude Code: start a new session (existing sessions won't see it).
   • Claude Desktop: fully quit the app (from the menu bar or system tray — closing the window isn't enough) and open it again.
2. Confirm the tools are there:
   • Claude Code: run claude mcp list, or ask "what enrichmentapi tools do you have?"
   • Claude Desktop: click the tools/plug icon under the message box; you should see enrichmentapi with its 10 tools.
3. Just ask. For example: "Find the domain for Stripe, then check whether press@ at that domain is a valid email." Your assistant will call the tools and answer.

Troubleshooting

The tools don't show up after connecting. Restart the assistant. Claude Code won't load a new connector into a session that's already running, and Claude Desktop needs a full quit, not just closing the window.

Unauthorized or "please make sure your API key is valid". The key didn't match an account. This is almost always a copy-paste slip — a leading/trailing space, a missing character, or the wrong value. Re-copy it from your dashboard (https://api.enrichmentapi.io/account-info) and update your config.

Hosted: 401 Missing EnrichmentAPI key. The X-EnrichmentAPI-Key header isn't reaching the server. Check the spelling of the header in your config, make sure the key isn't empty, and make sure the URL starts with https://.

Local option: "command not found" or nothing happens. The local option needs Node.js 20.12 or newer. Check with node -v. If it's missing or older, install a current version from nodejs.org and restart the assistant.

A specific lookup comes back empty. Some profiles and companies simply aren't publicly discoverable, and some data (like a personal email) may not exist to be found. An empty result isn't necessarily an error — try a different input, such as a full URL instead of just a name.

FAQ

Is my API key safe with the hosted option? Your key is sent as a header with each request and used only to forward that request to EnrichmentAPI. Nothing is stored on the connector side. If you'd still rather it never leave your machine, use the local (npx) option — the API calls to EnrichmentAPI happen either way, but the key stays in your local config.

Does this cost anything? The connector itself is free and open source. The lookups it performs use credits from your EnrichmentAPI account, according to your plan. Check your usage and plan on your dashboard.

Do I need the hosted and local options both? No. Pick one.

Which endpoints are covered? The ten customer-facing enrichment endpoints listed above. Account, billing, and admin functions are deliberately not exposed — this connector only reads data.

I regenerated my API key. What now? Update YOUR_KEY in your assistant's config (the claude mcp add command or the claude_desktop_config.json file) with the new value, then restart the assistant.

License

MIT