LeadBoxer MCP server

The LeadBoxer MCP server lets AI assistants and agents look up companies and contacts with your LeadBoxer account. Ask "Who is behind IP 193.8.9.0?", "Enrich acme.com" or "Who is [email protected]?" and your assistant calls LeadBoxer for you.

Server URL: https://mcp.leadboxer.com/mcp (remote, Streamable HTTP). Nothing to install.

It works with any client that supports remote Model Context Protocol servers, and it is listed in the official MCP Registry as com.leadboxer.mcp/leadboxer.

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`)
`lookup_email`	Returns the professional profile behind a work email: name, headline, LinkedIn, seniority, job function, location and work history. Optional name and company hints improve matching	50 per profile found, none when no one is found (`/v1/email-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 a LeadBoxer API key. Create a free developer account at signup.leadboxer.com and we email you a key with free credits. Existing users find their key in the LeadBoxer app under Integrations → API key. See Authentication & API Keys for more.

How connecting works

Most clients sign in with OAuth. When you add the server, your client opens the LeadBoxer Connect page:

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 your client.

Your API key stays with LeadBoxer: the client only receives a token that lets it call the tools.

Clients that can't run the Connect step, and scripts or CI, can send the key as a header instead: x-api-key: YOUR_API_KEY (or 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.

Connect your client

Claude

In Claude (web, desktop or mobile):

Open Settings → Connectors.
Click Add custom connector, name it "LeadBoxer" and enter https://mcp.leadboxer.com/mcp. Leave the advanced settings empty.
Click Connect and complete the Connect page.

Turn on LeadBoxer in a chat's tools menu and ask something like "How many LeadBoxer credits do I have left?". On Team and Enterprise plans, an owner may need to add the connector for the organization first.

Claude Code

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, add --header "x-api-key: YOUR_API_KEY".

To share the server 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"
    }
  }
}

ChatGPT

With developer mode turned on, add a custom connector (app) with the URL https://mcp.leadboxer.com/mcp and OAuth authentication, then complete the Connect page. Where to find developer mode depends on your ChatGPT plan; see OpenAI's help centre.

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

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

Cursor shows a Needs login button for LeadBoxer under Settings → MCP; click it to open the Connect page.

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your workspace:

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

Start the server from the file or the MCP view and sign in when VS Code asks.

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "leadboxer": {
      "serverUrl": "https://mcp.leadboxer.com/mcp"
    }
  }
}

Any other MCP client

Use the server URL https://mcp.leadboxer.com/mcp with the Streamable HTTP transport. If the client supports OAuth, it finds the sign-in details automatically; otherwise send the x-api-key header described above.

Example prompts

"Who is behind IP 193.8.9.0?"
"Enrich acme.com with company details."
"Who is [email protected]? Add her company details too."
"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

Remove LeadBoxer in your client's connector or MCP settings (in Claude Code: 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.
Your client 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.

Building against the API?

The separate API docs MCP lets coding assistants search this developer portal while you write code against the LeadBoxer API. For lookups in your assistant, use the LeadBoxer MCP server on this page.