MCP Hub › Developer Tools › Leadbay

Leadbay MCP server

by leadbay · io.github.leadbay/leadbay-mcp

AI lead discovery, qualification, and outreach prep on your Leadbay account.

🛠 Developer ToolsRemotenpmv0.46.1
Open in MCP HubGitHub repository ↗Website ↗

How to install Leadbay

Remote (http)

claude mcp add --transport http leadbay-mcp https://mcp.leadbay.app/apps/mcp

Or add it to your MCP config (Claude Desktop, Cursor, VS Code):

{
  "mcpServers": {
    "leadbay-mcp": {
      "type": "http",
      "url": "https://mcp.leadbay.app/apps/mcp"
    }
  }
}

npm

claude mcp add -e LEADBAY_TOKEN=<your-leadbay-token> -e LEADBAY_REGION=<your-leadbay-region> leadbay-mcp -- npx -y @leadbay/[email protected]

Or add it to your MCP config (Claude Desktop, Cursor, VS Code):

{
  "mcpServers": {
    "leadbay-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@leadbay/[email protected]"
      ],
      "env": {
        "LEADBAY_TOKEN": "<your-leadbay-token>",
        "LEADBAY_REGION": "<your-leadbay-region>"
      }
    }
  }
}

Environment variables:
LEADBAY_TOKEN (required) – Bearer token, set by the installer. Run `npx -y -p @leadbay/mcp@latest installer` and sign in with your browser.
LEADBAY_REGION (required) – us or fr - Leadbay backend that owns your account.
LEADBAY_MCP_WRITE – Set to 0 to hide composite write tools (default: 1, ON).
LEADBAY_MCP_ADVANCED – Set to 1 to expose granular API tools.
LEADBAY_TELEMETRY_ENABLED – Product-usage telemetry (PostHog/Sentry). Set to false to opt out. On a local/stdio install this env var is the ONLY way to stop telemetry — the account-level toggle (leadbay_set_telemetry) governs the hosted connector, not a local process (default: true).

Replace placeholders in <angle brackets> with your own values. Review what a server can access before you enable it.

Details

Version
0.46.1
Published
2026-10-24
Updated
2026-10-24
Namespace
io.github.leadbay
Source
leadbay/mcp

Similar developer tools servers