Cold Leads

What Cold Leads MCP server does

Cold Leads MCP server exposes the hosted Cold Leads workspace to MCP-compatible clients. It gives agents access to contacts, imports, synced mailbox conversations, templates, campaigns, lead context, follow-up queues, website lead capture setup, and email verification.

The service works with data already present in the customer’s workspace. Lead search checks contacts in Cold Leads for a company domain and optional role keyword; it does not discover prospects from an external database. Imports accept up to 100 parsed contact rows per call, deduplicate records, skip global do-not-contact entries, and do not send email.

How it works

The package starts as a Node.js process and forwards workspace tool calls to the hosted Cold Leads MCP service. It requires Node.js 20 or newer. A local client can launch it over stdio with npx -y @coldleads/mcp-server, while remote MCP clients can connect to https://coldleads.app/api/mcp with a bearer API key.

Cold Leads MCP server returns compact JSON in tool-result text blocks. Errors include an error flag and fields such as an error code, HTTP status, and retry delay. Email verification checks syntax, disposable domains, role accounts, and MX records. When the recipient mail server is reachable, it can also perform SMTP mailbox and catch-all checks; otherwise the result identifies SMTP unavailability.

Setup and configuration

Create a secret sk_… API key in Cold Leads under Settings → API keys and provide it as COLDLEADS_API_KEY. The API is included with the Business plan, which provides 10,000 verification and API credits per month, with extra packs available. COLDLEADS_API_BASE can point a local installation at a Cold Leads development server instead of the default hosted address.

The server can also start without a key. An agent may call provision_account_and_get_payment_link, show the returned Stripe checkout link to the human owner, and poll check_provisioning_status with the session and claim token. After payment, the API key is returned once and the process begins using it immediately. The owner, not the agent, decides whether to pay.

Tools and capabilities

• Verify individual email addresses and receive validity, risk, score, and diagnostic fields.
• Search, list, import, and update contacts in the connected workspace.
• Read synchronized conversations and send a message after explicit recipient and content approval.
• Review, create, and update templates, with content screening applied.
• Inspect campaigns, create drafts, estimate audiences, and launch only after human review and confirmation.
• Retrieve lead context, sales next actions, due follow-ups, and API/MCP activity records.
• Schedule a contact’s next action without sending email.
• Read workspace or mailbox status and generate a public website inquiry form key and snippet.

Limitations and notes

A verified address does not establish consent or a lawful basis for outreach. Opt-outs, bounces, and do-not-contact records block sending. Campaign launches and individual messages require explicit human approval. Each verification costs one credit, and API usage is limited to 120 requests per minute per key.

The hosted demo uses a temporary sample workspace, never sends email, and has limits on session duration, contacts, templates, drafts, text length, requests, and verification depth. Its sample contacts use .example domains. Website submissions are inquiry leads and are not automatic consent for cold outreach.

Cold Leads MCP server supports keyless onboarding, but production workspace operations depend on the account, plan, recipient limits, and provider or sender limits. Store the returned key as COLDLEADS_API_KEY for later starts and treat it as a secret.