@syntarie/mcp

Connect an MCP-compatible AI agent to your leadmaps analytics. The server runs over stdio and calls the public leadmaps query API with your API key.

Package migration: new installations should use @leadmaps/mcp. This compatibility package remains supported for 60 days after the canonical stable release.

What you need

1. A leadmaps account at app.leadmaps.nl.
2. An API key created under Settings, then API keys.
3. Optionally, a default site ID.

Configure an MCP client

{
  "mcpServers": {
    "leadmaps": {
      "command": "npx",
      "args": ["-y", "@syntarie/mcp"],
      "env": {
        "LEADMAPS_API_KEY": "lm_your_key_here",
        "LEADMAPS_SITE_ID": "your_site_id"
      }
    }
  }
}

The server also accepts LEADMAPS_API_URL when you need to override the hosted API base URL. Tool access still follows the scopes, plan, and quotas attached to the API key. The MCP package stores no analytics data and does not bypass API authorization.

Move to the canonical package

Replace @syntarie/mcp with @leadmaps/mcp in the args array. Environment variables and tool names stay the same.

See the agent connection guide or contact [email protected] for help.