Guide
Connect an MCP server to Claude: custom connector guide
Step by step: create an API key, add EU Company Leads to Claude as a custom connector or in Claude Code, run a first query and fix common connection errors.
6 min read · updated
Once an MCP server is connected, Claude can call its tools directly in a conversation: you ask a question in plain words and Claude decides which tool to call and with which arguments. This guide walks through connecting EU Company Leads to Claude, in the Claude apps and in Claude Code, and how to fix the problems people usually hit.
What MCP is, briefly
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data. An MCP server publishes a list of tools, each with a name, a description and a JSON schema for its parameters. An MCP client, such as Claude, reads that list and calls the tools when they help answer a request.
EU Company Leads is a remote MCP server over Streamable HTTP. It exposes four tools for company data from official European business registers:
| Tool | Purpose |
|---|---|
lookup_industry |
Plain words or national codes → NACE Rev. 2.1 codes |
search_companies |
Filter by country, industry, size, founding date, region, city and legal form |
get_company |
Full record for one company |
export_companies |
Every match as a CSV, via a link valid for 24 hours |
You do not call these yourself. Claude reads the descriptions and uses them; the lead list guide shows what a session looks like.
Step 1: get access and log in
Access is by request. Fill in the form on the front page with who you are and what you want to find. Once the request is approved you receive a login for the web app.
Log in, and you will see the company search and the API keys & MCP page.
Step 2: create an API key
On API keys & MCP, create a new key and give it a label you will recognise later, for example "Claude – sales team" or "Claude Code – laptop". The page then shows the full connector URL:
https://companies.noahbohme.com/mcp?key=YOUR_KEY
Copy it straight away. The key is shown once and cannot be displayed again. If you lose it, revoke it and create a new one.
Keys belong to your organisation, not to a single user. Create one key per client or per person so you can revoke one without breaking the others, and so the usage table shows who is calling what.
Why is the key in the URL? Claude's custom connectors take only a URL, with no field for custom headers, so the server also accepts the key as a ?key= query parameter. Clients that can send headers should use Authorization: Bearer instead (see below).
Step 3: add a custom connector in Claude
In Claude on the web or in the desktop app:
- Open Settings → Connectors.
- Choose Add custom connector.
- Give it a name, such as EU Company Leads.
- Paste the connector URL from step 2, including
?key=…. - Save.
Custom connectors depend on your Claude plan. On Team and Enterprise plans, an owner or admin may need to add the connector for the organisation first, after which members can enable it. If you do not see the option, check with whoever manages your Claude workspace.
Claude connects, reads the tool list and shows the connector as available. No OAuth step is involved: the key in the URL is the authentication.
Turn it on in a conversation
Connectors can be switched on or off per conversation. In a new chat, open the tools or connectors menu below the message box and make sure EU Company Leads is enabled. Claude may ask for permission the first time it calls a tool; you can allow individual calls or allow the tool for the conversation.
Step 4: try a first query
Start with something concrete enough to show filtering:
Find Finnish engineering companies in Uusimaa founded after 2020.
How many Czech companies are in software publishing, and which are the largest?
Export all Estonian accounting firms with at least 5 employees as a CSV.
You should see Claude call lookup_industry first to translate the industry into NACE codes (for example 62.10 Computer programming or 69 Legal and accounting), then search_companies with those codes. Expand the tool calls to see the exact arguments and results; this is the quickest way to understand what Claude asked for.
A few tips that make answers better:
- Name the country. Each country's register publishes different fields; see companies by country.
- Be explicit about size and age if they matter. Some countries publish no headcount, and Claude will tell you when a size filter excludes companies without one.
- Ask for an export when you want more than about a hundred rows, rather than paging through the chat.
Claude Code and other clients
Claude Code
Claude Code supports remote MCP servers over HTTP and can send headers, so use the Bearer form and keep the key out of the URL:
claude mcp add --transport http eu-company-leads https://companies.noahbohme.com/mcp \
--header "Authorization: Bearer YOUR_KEY"
Run claude mcp list to check that it connected, and /mcp inside a session to see the server and its tools. Add --scope user if you want the server available in every project rather than just the current one.
Any other MCP client
Any client that speaks MCP over Streamable HTTP can connect. Send requests to:
POST https://companies.noahbohme.com/mcp
Authorization: Bearer YOUR_KEY
The server also accepts the key in an X-Api-Key header or as ?key= on the URL. Prefer the header wherever the client allows it, because URLs end up in logs and browser history more easily than headers.
Troubleshooting
401 Unauthorized / "Missing or invalid API key". The key is wrong, incomplete or revoked. Check that the whole key was pasted (including the eucl_ prefix) and that it still appears as active on the API keys page. If in doubt, create a new key and update the connector.
Too many requests. Each key is limited to 240 requests per minute. Normal conversations stay far below this; scripted clients that loop over thousands of companies may hit it. Slow down, or use export_companies to get many rows in one call.
"Unknown parameter" errors. The tools reject parameters they do not recognise and reply with the list of valid ones. This usually means a client or prompt used an outdated or guessed parameter name. Claude normally corrects itself on the next call.
No results for an industry. The search tools need exact NACE Rev. 2.1 codes. If a client skips lookup_industry and guesses codes, results can be empty or wrong. Ask Claude to look up the industry first. What is a NACE code? explains the code levels.
A size filter returns nothing. Sweden, Finland and Belgium publish no employee data, so size filters exclude every company there unless include_unknown_size is set. See the Finland and Sweden guides.
The connector does not appear in a chat. Check that it is enabled for that conversation, and on Team or Enterprise plans that an admin has allowed it.
Keeping keys safe
An API key gives access to your organisation's account, and usage is logged against it. Treat it like a password:
- Do not paste connector URLs into shared documents, tickets or chat channels.
- Use one key per person or client, with a clear label.
- Revoke keys on the API keys & MCP page as soon as someone leaves or a key may have been exposed. Revocation takes effect immediately.
- Check the usage table now and then for calls you do not recognise.
Every response from the server includes source attribution for the registers used. When you share results, keep it with them, and read prospecting under the GDPR before you use a list for outreach. The registers and their licences are listed on the sources page.