LeadDelta MCP Server: What Your AI Assistant Can Do, What It Costs, and How It Stays Safe

Category: Integrations | Read time: 7 min | Updated: September 2026 | Status: Beta
The LeadDelta MCP Server connects your LeadDelta workspace to AI assistants like Claude, ChatGPT, Cursor and Perplexity using the Model Context Protocol (MCP). Once connected, you talk to your assistant normally and it does the work in LeadDelta for you: searching your network, building target lists, finding warm intros, keeping tags and notes current, and creating, launching and monitoring LinkedIn campaigns.
This is the reference article for the integration. It explains what the assistant can do, which actions cost credits or send messages, and how to set it up. The client-specific setup guides are linked at the bottom.

Beta notice: The MCP Server is in early access. The server URL, tool names and parameters may change as we iterate. The in-app page at Integrations → MCP Server is always the source of truth.

What you need

• A LeadDelta Business plan — the MCP Server is enabled for Business plan workspaces. Everything the assistant does happens inside the workspace your API key belongs to.
• A LeadDelta API key — created in under a minute at app.leaddelta.com/integrations/apiKey. Treat it like a password: anyone with the key can read and edit your workspace. You can revoke and regenerate it from the same page at any time.
• An MCP-capable assistant — Claude (claude.ai, Claude Desktop or Claude Code), ChatGPT (developer mode), Cursor, or Perplexity.

Connect in three steps

1. Create your API key. In LeadDelta, open Integrations (under Tools in the left sidebar) → API Key tab → generate a key if you don't have one and copy it.
2. Copy the server URL. Open the MCP Server tab on the same page. The server URL is:
https://mcp.leaddelta.com/mcp
The server uses Streamable HTTP and authenticates with your API key as a Bearer token (Authorization: Bearer YOUR_API_KEY). Clients with a guided connector flow (Claude, ChatGPT, Perplexity) will prompt you for the key; clients that use a config file (Cursor, Claude Code) take it as a header.
3. Add it to your assistant. Follow the guide for your client:

• Connect Claude (claude.ai, Claude Desktop, Claude Code)
• Connect ChatGPT
• Connect Perplexity
• Connect Cursor — add this to ~/.cursor/mcp.json (or Cursor Settings → MCP → Add new global MCP server) and replace the key:

{
  "mcpServers": {
    "leaddelta": {
      "url": "https://mcp.leaddelta.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_LEADDELTA_API_KEY"
      }
    }
  }
}

Start a new chat after connecting and make sure LeadDelta is enabled in your assistant's tools menu.

Before anything costs you

Three actions spend something real. Your assistant is instructed to confirm with you before running them, but it is worth knowing which they are. Everything else is free.

• Read — looks something up, changes nothing.
• Write — creates or edits, reversibly.
• Careful — deletes, spends credits, or contacts people.

What your assistant can do

You don't call these tools yourself. You describe what you want and the assistant picks the right one. The names are listed so you can recognise them when your assistant shows what it is about to do.

Your network

Finding new people

Warm introductions

• The person doesn't have to be in your network. Give the assistant any LinkedIn profile link and LeadDelta adds them as a contact tagged Imported before working out the paths, along with up to 25 of their mutual connections (the people who could make the introduction). You are told exactly who was added, and they can be removed like any other contact. If you'd rather nobody new was added, say so — the assistant will search only your existing network.
• Ask to see existing paths before paying for a fresh run. Results are saved and free to read back; a new run costs 10 credits and overwrites the old results.
• Brand-new contacts need a first look. When someone was just added, LeadDelta hasn't seen their mutual connections yet, so the first run works from profile similarity alone and may find little. Opening their LinkedIn profile with the LeadDelta extension records their mutuals, and the next run has much more to work with.

Tags, notes and follow-ups

Contact details

Campaigns — seeing what is happening

Campaigns — setting one up

Campaigns — choosing who to contact

Campaigns — sending

Done in the LeadDelta app

A few things stay in the app rather than being available to your assistant: connecting a LinkedIn account (it needs your LinkedIn password), sending a one-off message (messaging runs through campaigns), your inbox, and removing contacts.

Playbook: from a target list to live outreach

This is what the whole loop looks like in one conversation. Nothing is sent until you say start.

1. Build the list. "Find heads of RevOps at SaaS companies with 51–200 employees in Germany." The assistant uses search_leads. Free — nobody is enrolled yet.
2. Create the campaign. "Create a draft campaign called Q4 RevOps DACH." (create_campaign)
3. Configure it. "Use my connection-request template, then a follow-up after 3 days, send Mon–Fri 9–17 from my account." (configure_campaign, update_campaign_accounts)
4. Enrol people. "Add the 25 best matches." — or from your existing connections or tags, or a list you paste in. (add_leads_from_prospects, add_leads_from_connections, add_leads_from_rows)
5. Review, then start. "Show me who's enrolled." then "Start it." Your assistant confirms first, because this begins sending real connection requests and messages from your account — usually within a minute — and sent messages can't be recalled. (get_campaign_leads, update_campaign_status)

Afterwards: "How is it performing?", "Who replied?", "Pause it", "How much sending room do I have left today?"

Example prompts

Know your network

• "Find all my connections who work at Google in San Francisco."
• "Show me connections with VP in their job title."
• "Who in my network changed jobs recently? Tag them 'Job change'."
• "Who can introduce me to the CTO of Stripe?"
• "Find me a warm intro to linkedin.com/in/some-profile."

Build lists and expand

• "Find heads of RevOps at SaaS companies with 51–200 employees in Germany."
• "Show me founders of companies started after 2020 in fintech."
• "Quote me the credits to get work emails for these 20 people."

Run campaigns and growth ops

• "Create a campaign for that list with a 2-step connection request and follow-up."
• "Add my 'Founders'-tagged connections to the campaign and start it."
• "How is my Q4 outreach performing? Who replied?"
• "Create a task to follow up with everyone who replied this week."

Frequently asked questions

Can the assistant send messages from my LinkedIn account? Only through a campaign, and only after you tell it to start one. Creating, configuring and enrolling people into a campaign sends nothing. update_campaign_status is the single tool that begins contacting people, it is labelled Careful, and your assistant is instructed to confirm with you first. Campaigns follow your sending window and each account's daily limits. One-off messages and your inbox stay in the LeadDelta app.
Can it connect my LinkedIn account or remove contacts? No. Connecting a LinkedIn account needs your LinkedIn password, so it is done in the app. Removing contacts and working your inbox also stay in the app.
What spends credits? Two things: looking up contact details (run_enrichment) and generating fresh warm-intro paths (generate_connection_recommendations). Everything else, including searching the lead database and reading back saved intro paths, is free. Ask your assistant for a quote before enriching; spent credits are not refunded.
Some tools say I need a subscription. Tagging, notes and tasks need an active subscription. Reading is always available.
Is my LinkedIn data safe? Your assistant connects to LeadDelta over encrypted HTTPS using your personal API key. Your data stays in your LeadDelta workspace — the assistant reads it on demand and LeadDelta makes no live calls to LinkedIn to answer it. Revoke the key at any time from Integrations → API Key and the connection stops immediately.
Which LeadDelta plan do I need? The Business plan.
Do I need a paid Claude / ChatGPT plan? Claude's free plan includes one custom connector slot; paid plans allow more. ChatGPT custom MCP connectors require developer mode, which is available on paid plans. Perplexity and Cursor requirements are covered in their guides.
Why did new people appear in my network tagged "Imported"? You (or your assistant) ran a warm-intro search for someone outside your network. To work out who can introduce you, LeadDelta adds the person you named and up to 25 of their mutual connections to your workspace so the paths can be evaluated. The assistant tells you exactly who was added, they can be removed like any other contact, and you can ask it not to add anyone next time.
The connector shows an error after setup. Check that the URL is exactly https://mcp.leaddelta.com/mcp (some clients need a trailing slash), that your workspace is on the Business plan, and that the API key hasn't been revoked. Start a new chat after reconnecting. If it still fails, email with the assistant you use and a screenshot.
Something that used to work stopped working. The server is in beta and tool names or parameters may have changed. Check the in-app Integrations → MCP Server page for the current list.

Related articles

• How to Connect Claude AI Using LeadDelta – LinkedIn MCP
• How to Connect ChatGPT Using LeadDelta – LinkedIn MCP
• How to Connect Perplexity Using LeadDelta – LinkedIn MCP
• How to Generate / Revoke an API Key
• How do credits work?
• LeadDelta AI Campaigns: Automate Your LinkedIn Outreach
• Warm Intro AI: Find the Best Path to Any Contact

Updated on: 22/09/2026