API docs MCP (for coding)

Let your coding assistant search the LeadBoxer developer docs and API reference while you build an integration.

📘

Looking for company and contact lookups in your AI assistant?

Use the LeadBoxer MCP server at https://mcp.leadboxer.com/mcp. This page is about a different server for developers writing code.

The API docs MCP gives AI coding tools such as Cursor, Windsurf and Claude Code access to this developer portal: it searches the guides, lists the API endpoints and shows their specs, so your assistant can write correct integration code. It can also send a request to the LeadBoxer API on your behalf, which is handy for trying an endpoint while you build.

Server URL: https://developers.leadboxer.com/mcp

Searching the docs needs no key. To try endpoints, send your API key in the x-api-key header, configured the way your MCP client sets headers. Never put your API key in the URL or a query parameter: URLs end up in logs and browser history. Requests made through this server use credits and can change data like any other API call, so check what your assistant sends.

Add to ~/.cursor/mcp.json:

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

Try it

Open your editor's AI chat and ask, for example:

  • "How do I look up the company behind an IP address with the LeadBoxer API? Show a Python example."
  • "Which LeadBoxer endpoint returns firmographics for a domain, and what does the response look like?"
  • "Write a TypeScript function that enriches a work email with the LeadBoxer API."

Did this page help you?