Private beta — 0/10 founder seats (-50% for life) Join the waitlist
Leadmaps

The Leadmaps MCP server — European business data for any agent

Any MCP-capable client — Claude, Cursor, n8n, VS Code, custom agents — can drive Leadmaps through one HTTP endpoint. Responses use a compact “lead” field set (~60 tokens per listing) and every reply carries credits_charged, credits_remaining and a hint for the agent.

Setup

  1. Create your API key at app.leadmaps.io/keys (lm_test_ for the free sandbox).
  2. Point your client at https://mcp.leadmaps.io/mcp (Streamable HTTP, stateless).
  3. Authenticate with the header Authorization: Bearer <your key>.
  4. Best practice for agents: call count_places (free) before search_places; use create_export beyond 200 results.
{
  "mcpServers": {
    "leadmaps": {
      "type": "http",
      "url": "https://mcp.leadmaps.io/mcp",
      "headers": { "Authorization": "Bearer lm_live_xxx" }
    }
  }
}

3 copy-paste prompts

MCP tools

ToolCost
count_placesFree — always call first
search_places1 credit per place returned (30-day dedup free)
get_place1 credit (dedup)
list_categoriesFree
create_export1 credit per delivered row
get_export_statusFree

FAQ

Which transport does the MCP server use?

Streamable HTTP, stateless, at https://mcp.leadmaps.io/mcp — authentication via the Authorization: Bearer header with your lm_test_ or lm_live_ key.

Which MCP clients are compatible?

Any client speaking the Streamable HTTP transport: Claude (Desktop, Code, claude.ai), Cursor, VS Code, n8n, and your own agents via the official MCP SDKs.

How does the server help my agent control its budget?

count_places, list_categories and get_export_status are free; every paid response carries credits_charged, credits_remaining and an agent hint; create_export is recommended beyond 200 results — and the account spending cap bounds everything.