One connector URL, https://mcp.icebreakly.com, and one Icebreakly API key
Claude MCP integration
Control Icebreakly from Claude.ai with MCP
Add https://mcp.icebreakly.com as a custom connector in Claude, paste one API key, and Claude can run your LinkedIn outreach: build lists, launch campaigns, enrich contacts, read replies, and audit what is not working.
Watch the full Icebreakly demo (1 min)Best for
- Building a list from buying signals and launching a campaign against it, in one chat
- Asking why a campaign stopped sending and fixing it without opening the dashboard
- Finding out who replied and is still waiting on you, ranked by how likely they are to close
The problem
Claude is only as useful as the data it can reach
Pasting a lead export into a chat gets you advice. Connecting Claude to Icebreakly over MCP gets you execution: it reads your live campaigns, contacts, and signals, then takes the action you asked for inside the same workspace your team already uses.
145 tools across contacts, lists, campaigns, signals, enrichment, and Unibox
Expert tools that audit a setup, diagnose a stalled campaign, and rank your pipeline
The same sending limits and safety rules as the dashboard, because it is the same engine
How it works
A simple workflow for claude mcp integration
In Icebreakly, open Integrations then Claude Connector (MCP) and create an API key
In Claude, go to Settings, Connectors, Add, then Add custom connector
Name it Icebreakly, paste https://mcp.icebreakly.com, and press Add
Paste the API key on the Icebreakly authorize page that opens, then press Authorize
Ask Claude to audit your whole account to confirm the tools are live
What MCP changes for sales workflows
Model Context Protocol is an open standard that lets an AI assistant call structured tools rather than read raw text. For a sales workflow, that distinction is the difference between Claude saying "you should follow up with these leads" and Claude actually loading the lead list, filtering it by signal score, drafting follow-up copy for each one, and queuing them for review.
Until MCP, integrating Claude with a SaaS product meant copying tables into the chat and asking Claude to reason over them. With MCP, Claude reads from the live data, calls actions back into Icebreakly, and works from a current source of truth. The integration is durable because it speaks a defined protocol rather than relying on screenshots or pasted CSVs.
Setting up the Icebreakly connector in Claude.ai
Setup is a URL and a key, with nothing to install. Once the connector is added, Claude discovers the tools on its own and lists them in the conversation.
- In Icebreakly, open Integrations then Claude Connector (MCP) and press New Key, then copy it
- In Claude, open Settings, Connectors, the Add menu, then Add custom connector
- Name it Icebreakly and paste https://mcp.icebreakly.com as the server URL
- Icebreakly's authorize page opens: paste the key, press Authorize, and Claude returns connected
- Ask Claude to read an Icebreakly list or audit your account to confirm the connection
The tools Claude gets, and the ones worth knowing by name
Most of the 145 tools you never need to think about, because Claude picks them from what you asked for. A handful are worth knowing by name, because they carry the expertise rather than just the data.
- full_audit: one prioritized fix plan across delivery, setup, performance, and pipeline
- diagnose_campaign: why a campaign will not start, stopped sending, or paused, plus the fix
- analyze_pipeline: the actual people to act on, ranked by conversion likelihood and ICP fit
- generate_message_templates: connect note, first message, and three follow-ups from your stored setup
- count_people and search_people: size an audience for free, then pull the profiles that match
- enrich_contacts_email_bulk: verified emails in batches, charged only when one is found
FAQ
Common questions about claude mcp integration
Does Icebreakly support Claude MCP?
Yes. Icebreakly runs a dedicated MCP server at https://mcp.icebreakly.com. It speaks streamable HTTP, so it works as a custom connector in Claude.ai and Claude Desktop, and as a configured server in Claude Code.
What can Claude access through Icebreakly MCP?
All 145 tools: dashboard stats and performance analysis, contacts, lists, campaigns, signal leads from the intent, competitor, and influencer agents, social listening engagers, email and phone enrichment, Unibox conversations and reply approvals, AI setup and prompts, LinkedIn sender accounts, and workspace admin.
Do I need an API key for Claude MCP?
Yes, one key. Create it under Integrations then Claude Connector (MCP) in Icebreakly. During setup Claude sends you to Icebreakly's own authorize page, where you paste the key once. Deleting the key revokes Claude's access immediately.
Can Claude send messages without asking me?
Your client asks you to confirm before a tool that writes or sends runs, and Icebreakly enforces the same daily limits, plan caps, and sender checks it applies to campaigns started from the dashboard. Anything Claude queues is visible in the app and can be cancelled there.
Explore more Icebreakly solutions