Connect LeadBoxer to Claude

The LeadBoxer connector lets Claude look up companies for you while you chat or code. Ask "Who is behind IP 193.8.9.0?" or "Enrich acme.com" and Claude calls LeadBoxer with your account.

The connector runs at https://mcp.leadboxer.com/mcp and works in Claude (web, desktop and mobile), Claude Code and other MCP clients such as Cursor.

Tools

Tool	What it does	Credits
`lookup_ip`	Identifies the company behind an IPv4 or IPv6 address: organization, domain, ISP, usage type and location	20 per request (`/v1/ip-lookup`)
`lookup_domain`	Enriches a company domain with firmographics: industry, employees, description, address and LinkedIn	10 per request (`/v1/domain-lookup`)
`get_credit_balance`	Shows your remaining credits	Free

Every lookup result reports the credits used and the credits left. All tools are read-only: they never change data in your LeadBoxer account.

Before you start

You need your LeadBoxer API key. Find it in the LeadBoxer app under Integrations → API key. See Authentication & API Keys for more.

Connect in Claude

In Claude, open Settings → Connectors.
Click Add custom connector, name it "LeadBoxer" and enter https://mcp.leadboxer.com/mcp. Leave the advanced settings empty.
Click Connect. A LeadBoxer page opens.
Paste your API key. Optionally enter a dataset ID to charge credits to a specific dataset; leave it empty to use your account's default.
Click Connect. You're returned to Claude.

Turn on LeadBoxer in a chat's tools menu and ask something like "How many LeadBoxer credits do I have left?".

Your API key stays with LeadBoxer: Claude only receives a token that lets it call the tools. On Team and Enterprise plans, an owner may need to add the connector for the organization first.

Claude Code

Add the connector and sign in with the same Connect page:

claude mcp add --transport http leadboxer https://mcp.leadboxer.com/mcp

Then run /mcp in Claude Code and choose LeadBoxer to connect.

To skip the Connect step, for example in scripts or CI, send your API key as a header instead:

claude mcp add --transport http leadboxer https://mcp.leadboxer.com/mcp \
  --header "x-api-key: YOUR_API_KEY"

To share the connector with your team, check a .mcp.json into your repository. Each developer connects with their own key:

{
  "mcpServers": {
    "leadboxer": {
      "type": "http",
      "url": "https://mcp.leadboxer.com/mcp"
    }
  }
}

Other MCP clients

Clients that support remote MCP servers with OAuth, such as Cursor, can use https://mcp.leadboxer.com/mcp the same way. If a client can't run the Connect flow, send your API key in the x-api-key header (or as Authorization: Bearer YOUR_API_KEY). Add an x-dataset-id header to charge credits to a specific dataset.

Never put your API key in the URL: URLs end up in logs and browser history.

Example prompts

"Who is behind IP 193.8.9.0?"
"Enrich acme.com with company details."
"Here's my server access log. Identify the companies visiting my API and rank them by employee count."
"How many LeadBoxer credits do I have left?"

Disconnect

Disconnect LeadBoxer in Claude's connector settings, or remove it in Claude Code with claude mcp remove leadboxer. Rotating your API key in LeadBoxer also ends access for every connected app.

Troubleshooting

"That API key was not accepted": check that you copied the whole key from Integrations → API key.
Claude asks you to reconnect: your API key was rotated or revoked. Connect again with the current key.
Out of credits: lookups stop until you add credits. get_credit_balance still works.