Skip to main content
The CompanyEnrich MCP server lets AI clients like Claude, Codex, Cursor, and VS Code use our data directly. Ask in plain English to enrich companies, search companies and people, find lookalikes, or get work emails.

Hosted or local?

There are two ways to connect. Both have the same tools. Not sure? Use hosted and sign in. Use local if your client only runs stdio servers, or you want calls to go straight from your machine to our API. You only need an API key if you skip sign-in or run locally. Create one at app.companyenrich.com/access-keys.

Connect your client

Find your client and pick a tab. Replace your-api-key with your real key.

Claude Code

If you picked Sign in, open /mcp in Claude Code and finish logging in.

Codex CLI

Sign-in starts right after codex mcp add. If you close it, run codex mcp login companyenrich. With the API key option, the variable has to be set in the shell where you run Codex.

Claude Desktop

Hosted: open Customize > Connectors, click + Add, then Add custom connector. Give it a name, paste https://mcp.companyenrich.com/mcp, and follow the steps to sign in. On Team and Enterprise plans, an Owner adds it under Organization settings > Connectors. To use an API key instead, add a request header named Authorization with the value Bearer your-api-key when it asks. Local: open Settings > Developer > Edit Config, add this, then fully quit and reopen the app.

Cursor

Add this to ~/.cursor/mcp.json. You can use .cursor/mcp.json to set it up for one project, but don’t commit that file with your key in it.

VS Code

Add this to .vscode/mcp.json. To use it in all your projects, run MCP: Open User Configuration and add it there. With the API key and Local tabs, VS Code asks for your key once and stores it, so it stays out of your repo.

Raycast

API key

Other clients

Add a remote or Streamable HTTP server with the URL https://mcp.companyenrich.com/mcp and sign in when asked. To use an API key, send the header Authorization: Bearer your-api-key. To run it locally, use npx as the command and -y @companyenrich/mcp as the arguments, then set COMPANYENRICH_API_KEY in the server’s environment.

Check that it works

Ask your client this:
What’s my CompanyEnrich credit balance?
It runs get_current_user, which is free. If you see your balance, you’re connected. If you don’t, see Troubleshooting.

What you can ask

Tools and credits

Your client finds these tools by itself, so you don’t have to remember them. The costs are here so you know what you’re spending.
The npm MCP server uses the V1 API. Its workforce pricing differs from the V2 API and the official SDKs.
A few things to watch:
  • Search tools charge per result. A default page has 20 results, so one find_similar_companies call can cost up to 100 credits and one search_people call up to 40. Say how many results you want.
  • includeWorkforce adds 5 credits per company, including every company in a search.
  • Your client can make several calls for one question. Most clients ask before running a tool, so keep that on while you’re testing.
Tool responses include your balance under creditInfo. See Credits for how credits work.

Install or pin the npm package

The Local tabs use npx, which runs the package without you installing it. Lock a version: keep npx and put the version in args: ["-y", "@companyenrich/mcp@2.0.0"]. Install as a Node module: use this if you don’t want your client going through npx every time it starts.
Then run it with node. Replace /path/to/node_modules with what npm root -g printed, or with the full path to your project’s node_modules folder.
In VS Code, use servers as the top-level key and add "type": "stdio". To update, run npm install @companyenrich/mcp@latest, with -g for a global install. The package only ships the server, so there’s nothing to import in your own code. It reads COMPANYENRICH_API_KEY (required) and COMPANYENRICH_API_URL (optional, defaults to https://api.companyenrich.com).

Troubleshooting

The tools don’t show up Restart your client after changing its config. Then check that your JSON is valid and in the right file. To see what’s connected:
  • Claude Code: run claude mcp list
  • Codex CLI: run codex mcp list
  • Cursor: open Customize and make sure the server is on. Logs are in the Output panel under MCP Logs.
  • VS Code: run MCP: List Servers
  • Claude Desktop on macOS: check the logs in ~/Library/Logs/Claude
Authentication failed. Please check your API key. Your key is wrong, or the config still says your-api-key. Fix it and restart your client. We only check the key when a tool runs, so the tools can show up even with a bad key. COMPANYENRICH_API_KEY is not set The local server can’t find your key. Add it to the env block for this server and restart your client. Insufficient credits. Please check your account balance. Your account is out of credits. Tool calls will fail until you add more. Rate limit exceeded. Please try again later. You’re sending too many requests. Wait a bit and try again. See Rate Limit. env: node: No such file or directory, or your client can’t find npx Run node -v and make sure you’re on Node.js 20 or newer. Desktop apps often can’t see Node if you installed it with nvm or Homebrew. Two changes fix it:
  1. Run which npx and use that full path as the command. If you installed the package as a Node module, use the full path from which node instead.
  2. Run dirname $(which node) and add that folder to PATH in the env block.
To test the package without a client, run this in a terminal:
It prints nothing and waits for a client, which is normal. Press Ctrl+C to stop it. If you get an error, it’s a Node or npm problem. 401 from the hosted server, or your client keeps asking you to sign in The server didn’t get your login or key. Finish signing in through your client, or send your key as Authorization: Bearer your-api-key. Your config points to /sse We don’t serve the old SSE endpoint anymore. Switch to https://mcp.companyenrich.com/mcp.

Privacy

Once it’s running, the local server only talks to the CompanyEnrich API. It stores nothing and has no telemetry. The hosted server doesn’t store an API key you send as a bearer token. For OAuth sign-ins, we keep your grant with the API key encrypted.