Connect Claude, ChatGPT, Gemini or Groq

LeadMind exposes seven tools over MCP: 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.

You need an API key. Create one in Settings — it is shown once.

Building against the REST API instead of MCP? The API reference covers authentication, rate limits, the sandbox and signed webhooks.

1In Claude, open Settings → Connectors → Add custom connector.
2Paste the MCP server URL: https://outreach-nlfc.onrender.com/mcp
3Under advanced settings add a header Authorization with the value below (or use “Sign in” if OAuth is enabled).
4Ask Claude: “Find 25 coffee shops in Austin with websites.” It calls create_lead_job straight away; the job estimates the cost itself and holds credits only up to your balance (or a budget you name).

MCP URL:  https://outreach-nlfc.onrender.com/mcp

Authorization: Bearer lp_live_…

Claude Desktop (config file) alternative:

{
  "mcpServers": {
    "leadmind": {
      "url": "https://outreach-nlfc.onrender.com/mcp",
      "headers": { "Authorization": "Bearer lp_live_…" }
    }
  }
}

Integrations

LeadMind exposes one MCP endpoint (https://outreach-nlfc.onrender.com/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 seven tools 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.
leads:read — read job status, leads and CSV exports.
credits:read — read balance and ledger.
webhooks:write — manage outbound webhook endpoints (see the API docs).