🔍LeadSleuth Try free

Connect AI agents via MCP

Query your LeadSleuth leads, dossiers and ICPs from Claude, ChatGPT, Cursor or any Model Context Protocol client. Read-only, scoped to your own data.

Endpoint & tools

https://leads.zalize.com/api/mcp

Streamable HTTP transport. Two ways to authenticate, both read-only and scoped to your own data: OAuth 2.1 (with dynamic client registration — clients like ChatGPT, Claude custom connectors and MCP Inspector register automatically and open a LeadSleuth consent page) or a Bearer API key shared with the REST API (60 requests/minute per key). Tools:

  • list_leads — list leads with optional status, min_intent, page, per_page filters
  • get_lead — a single lead by id, including its latest dossier
  • list_icps — your ICP profiles with parsed criteria
  • search_signals — keyword search over signal quotes, names and handles

Step 1 — Create an API key (skip if your client supports OAuth)

OAuth-capable clients (ChatGPT, Claude custom connectors, MCP Inspector) don't need a key — they take you through a login + consent page instead. Use an API key for header-based setups like Claude Code, Claude Desktop config and Cursor below.

  1. Open Settings → API in LeadSleuth.
  2. Name a key (e.g. "claude") and click Create.
  3. Copy the lsk_… key now — the plaintext is shown exactly once. You can also copy a ready-made MCP config from the same page.

Claude Code & Claude Desktop

Claude Code (one command)

claude mcp add --transport http leadsleuth https://leads.zalize.com/api/mcp \
  --header "Authorization: Bearer lsk_your_api_key"

Claude Desktop

Settings → Developer → Edit Config, then add to claude_desktop_config.json (uses mcp-remote, since Desktop config launches local commands):

{
  "mcpServers": {
    "leadsleuth": {
      "command": "npx",
      "args": ["mcp-remote", "https://leads.zalize.com/api/mcp",
               "--header", "Authorization: Bearer lsk_your_api_key"]
    }
  }
}

Restart Claude Desktop, then ask e.g. "List my newest high-intent leads".

Claude custom connector (OAuth, no key)

On Claude plans with custom connectors: Settings → Connectors → Add custom connector, enter https://leads.zalize.com/api/mcp — Claude registers via OAuth and opens the LeadSleuth consent page; log in and click Approve.

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) — Cursor supports Streamable HTTP natively:

{
  "mcpServers": {
    "leadsleuth": {
      "url": "https://leads.zalize.com/api/mcp",
      "headers": { "Authorization": "Bearer lsk_your_api_key" }
    }
  }
}

Enable the server in Cursor Settings → MCP, then use it from chat/agent mode.

ChatGPT

ChatGPT connects to remote MCP servers as connectors in developer mode (Plus/Pro, or when your workspace admin allows it):

  1. Open ChatGPT → Settings → Apps & Connectors (web: chatgpt.com → profile → Settings) and enable Developer mode under Advanced settings.
  2. Still under Apps & Connectors, click Create (custom connector), name it "LeadSleuth" and set the MCP server URL to https://leads.zalize.com/api/mcp; leave authentication on OAuth.
  3. In a new chat, open the + menu near the composer → use the connector (under Developer mode / More) and select LeadSleuth.

When prompted to authenticate, ChatGPT registers itself automatically (OAuth 2.1 with dynamic client registration) and opens a LeadSleuth consent page — log in with your normal account and click Approve. No API key needed; access is read-only and scoped to your own data, and you can revoke it any time by denying future consents.

Security

  • All tools are read-only — no tool can modify or delete your data.
  • Each key is scoped to its owner's data only and can be revoked instantly in Settings → API.
  • Rate limit: 60 requests/minute per key, shared with the REST API.