Skip to content
LeadMind
Start free

Connect LeadMind to Claude, ChatGPT, Gemini or Groq

Pick your app below for a step-by-step guide, or use the quick setup further down. LeadMind exposes 11 tools over MCP. For leads: create_lead_job, get_job_status, clarify_job, get_leads, export_leads_csv, get_credit_balance and list_sources. There is no estimate step: the job works out the cost itself and holds credits only up to your balance (or the budget you give the assistant), and each API key has a daily credit cap you control.

Step-by-step guide for your app

For the email verifier (paid plans, from a monthly verification quota rather than credits): verify_emails checks up to 25 addresses inline, start_email_verification and get_email_verification verify a whole list of up to 5,000 per job and return a CSV, and get_verification_quota shows what is left this period. See how the email verifier works.

Claude, ChatGPT and Gemini CLI sign in with OAuth, no key needed. Custom GPTs, n8n, CI and the REST API need an API key from Settings; it is shown once.

Get an API key
Building against the REST API instead of MCP? The API reference covers authentication, rate limits, the sandbox and signed webhooks.
  1. 1In Claude (web or desktop), open Customize → Connectors, click + and choose Add custom connector.
  2. 2Name it LeadMind and paste the MCP server URL: https://mcp.leadmindai.app/mcp
  3. 3Click Add, then Connect, sign in to LeadMind and approve access. No API key to copy: the connector uses OAuth and you can revoke it from Settings at any time.
  4. 4In a chat, click + → Connectors, switch LeadMind on and ask: “Find 25 coffee shops in Dubai Marina with websites.” Claude calls create_lead_job straight away; credits are held only up to your balance (or a budget you name).
MCP URL:  https://mcp.leadmindai.app/mcp

Claude Code (terminal): OAuth opens in your browser on first use.

claude mcp add --transport http leadmind https://mcp.leadmindai.app/mcp

Headless or CI? Use an API key instead of OAuth:

claude mcp add --transport http leadmind https://mcp.leadmindai.app/mcp \
  --header "Authorization: Bearer lp_live_…"

Integrations

LeadMind exposes one MCP endpoint (https://mcp.leadmindai.app/mcp) and a REST API behind the same key, so a platform can either hand the whole toolset to an agent or call a single endpoint. Credits are held up to the caller's balance or budget and charged only for delivered leads, and every key carries a daily cap — whoever is calling.

n8n

Workflows
Available now

Hand an AI agent the whole toolset in one node.

Add an MCP Client Tool node, point it at the MCP endpoint over Streamable HTTP, and pass your API key as a bearer header. The agent gets all 11 tools, lead generation and email verification, with no per-tool wiring. For delivery, add a Webhook node and subscribe its URL to the job.delivered event in Settings, so the workflow continues the moment the list lands.

Docs

WhatsApp AI agent

Messaging
Works over HTTP

Your customer texts a description and gets a lead list back.

Wire Meta Cloud API, Twilio or WATI into n8n, then call create_lead_job with the message text (set max_credits if the sender named a budget). Poll for delivery and reply with the export link. No dashboard, no onboarding, no seat to buy.

Google Sheets

Spreadsheet
Works over HTTP

Deliver every list where the team already works.

Append delivered leads to a sheet from n8n, Make or Zapier. The sheet becomes the working surface for the sales team, which is what turns a one-off list into a standing weekly job.

Clay

GTM data
Works over HTTP

Be a source inside the stack that already buys data.

Call LeadMind from an HTTP enrichment column to fill a Clay table with scored, sourced rows. Clay teams run high volumes on a recurring cadence, so this is the highest credit burn per account of anything on this page.

Docs

Zapier

Workflows
Works over HTTP

Start a job from any of the apps you already pay for.

Use Webhooks by Zapier with a custom POST and bearer auth to fire a job from a form, a CRM stage change or a calendar event. Then add a Catch Hook trigger and subscribe it to the job.delivered webhook in Settings; the Zap resumes with the export link as soon as the leads are ready.

Docs

Groq

LLM API
Available now

Give a Groq-hosted model the toolset with one request.

Groq's Responses API takes remote MCP servers as tools: pass the LeadMind MCP URL and your key in the tool definition and the model can create jobs, poll status and read leads inside a single conversation — fast enough for interactive assistants. Copy the request from the Groq tab above.

Docs

Jobs run for two to fifteen minutes, so treat delivery as asynchronous. Subscribe an endpoint to the job.delivered webhook (signed with HMAC-SHA256, retried up to six times) and it will POST the export link the moment the list is ready; a Zapier Catch Hook or an n8n Webhook node is enough. If you would rather poll, call GET /v1/jobs/:id and honour the Retry-After header rather than looping on a fixed timer. Details in the API docs.

Scopes

  • jobs:write: create, clarify and cancel jobs, and start email verifications.
  • leads:read: read job status, leads, CSV exports and verification results.
  • credits:read: read the balance, the ledger and the verification quota.
  • webhooks:write: manage outbound webhook endpoints (see webhooks in the API reference).

Keep reading