Integrations
Three connections exist today. An MCP server lets Claude and other AI clients run your comment campaigns. Slack receives notifications. Every LinkedIn account can use a proxy you supply. No native sync exists for HubSpot, Salesforce, Instantly or Clay, and further down we show how teams work beside those tools regardless.
All three are set up from the Integrations screen inside the app. None of them is required. Icebreakly monitors your leads and drafts comments with nothing else attached.
One endpoint, https://mcp.icebreakly.com, exposes 63 tools in nine groups: comment campaigns, monitored leads, comments and approvals, warming, Voices, dashboard numbers, AI setups, LinkedIn accounts and workspace jobs. Claude.ai, Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline and Zed can all connect. You create a key inside the app, and deleting that key cuts access at once.
See the tool reference →Link your Slack workspace and Icebreakly sends its alerts there, so campaign activity turns up where the team already talks. Think of it as a notification channel and nothing more. It is not a route for pushing leads or warming stages into other software.
Add an HTTP proxy with its host, port and credentials, then assign it to a LinkedIn account. From then on that account’s activity goes out through an IP address you control. Icebreakly tests the proxy before saving it and warns you if it later stops responding. This one is optional. Accounts run without it.
Icebreakly has no native integration with HubSpot, Salesforce, Instantly, Clay or any other CRM, email platform or data tool. Contacts are not synced in. Activity is not written back. No public REST API exists to build that sync on, either. Better you read it here than discover it after signing up.
Scope is the reason. Icebreakly does one job: it comments on the posts of leads you chose and keeps count of how familiar each has become. It holds no deal records and sends no email. What it tracks for a lead is small: a profile URL, the comments posted, a touch count and a stage.
If a field-level CRM sync is a hard requirement for your team, Icebreakly does not meet it today, and a tool with a native connector is the right call.
The division of labor is simple and needs no connector.
The CRM holds the list. Accounts, contacts and open deals stay where they are. Pull the LinkedIn profile URLs of the people who matter this quarter: the 80 contacts sitting on open opportunities, perhaps, or the buying committees at your twenty target accounts.
Icebreakly warms the people on it. Add those URLs as monitored leads. Whenever one of them posts, a comment is drafted in your voice. It waits for your approval, or posts by itself on Autopilot. Each comment is one touch.
The warming stage tells you when to act. A lead goes from Stranger to Familiar at about five touches, Trusted at about twelve, Warm at twenty or more. Once a week, open the ready-to-reach-out list and carry the result back by hand. Log a task against the contact in HubSpot. Move the deal stage. Release that person into the Instantly sequence you had been holding them out of. The first email now comes from a name they have seen under their own posts.
An assistant can do the carrying for you. Suppose Claude is connected to Icebreakly over MCP and also has a connector for your CRM. Ask it who reached Trusted this week and have it add a note to those contacts. That is your assistant moving information between two tools while you watch. It is not a sync Icebreakly runs or guarantees, so read what it writes.
None of this depends on which CRM or email tool you run. HubSpot, Salesforce and Instantly all work the same way here: Icebreakly sits next to them, and nothing syncs natively.
Setup steps, tool lists and worked examples. CRMs and email tools have no guide here, because Icebreakly sits beside them and does not sync with them.
For the wider picture, the LinkedIn automation guide sorts the tools into categories and shows where comment warming sits. Plans and pricing lists what each tier includes.
All 63 tools by group, example prompts, and the config for each supported client.
Open the guide →GuideCreate a key, add the server URL in Claude, approve the connection. Each step in order.
Open the guide →GuideWhat running comment campaigns from a Claude conversation looks like once the server is connected.
Open the guide →GuideThe same subject seen from the workflow side: where comment warming sits among the tools a sales team runs.
Open the guide →Three things today. An MCP server at https://mcp.icebreakly.com lets Claude and other MCP clients operate your workspace through 63 tools. Slack can receive Icebreakly notifications. Each LinkedIn account can be routed through an HTTP proxy that you supply. Those are the only native integrations.
No. Icebreakly has no native HubSpot or Salesforce integration in either direction. Teams with a CRM keep the contact list there, add the LinkedIn profile URLs of the people they want to warm to an Icebreakly campaign, and record the result in the CRM by hand once a lead reaches a warm stage.
No. Icebreakly sends no email and has no connector for Instantly, Clay or similar products. A workable way to combine them is timing: keep a lead out of the email sequence while comments build familiarity, then start the sequence when that lead reaches the Familiar or Trusted stage.
Treat the CRM as where the list lives and Icebreakly as where the warming happens. Copy the LinkedIn profile URLs of your priority contacts into a comment campaign and look at the warming stages once a week. When a contact reaches the Trusted stage, at about 12 touches, create the follow-up task or move the deal in your CRM. The hand-off is manual. For a list of around a hundred people it is a small weekly job.
Run the whole comment-campaign workflow. The 63 tools cover creating and activating comment campaigns, adding and removing monitored leads, listing, editing and approving pending comments, reading warming stages, tuning Voices, checking dashboard numbers and managing connected LinkedIn accounts. Access belongs to a key for one workspace, the plan limits match the dashboard, and deleting the key revokes access immediately.
Any client that speaks MCP over streamable HTTP, including Claude.ai, Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline and Zed. Claude connects through a sign-in step where you paste your key once and approve access. Clients configured by file send that same key as a bearer token.
Notifications. With your Slack workspace linked, Icebreakly can post its alerts there, so you hear about campaign activity without opening the dashboard. It is a notification channel, not a way to sync data into a CRM.
So a LinkedIn account’s activity comes from an IP address you picked, for example one in the country that account normally signs in from. You enter the HTTP proxy’s host, port and credentials, Icebreakly confirms it can be reached, and you assign it to a LinkedIn account. It is optional. A proxy reduces one kind of risk, an inconsistent location. It does not make automation risk-free.
There is no public REST API product. The supported programmatic route is the MCP server, which any MCP-capable client or agent framework can call and which returns structured data.
MCP access comes with your plan and runs inside the same limits as the dashboard, such as the number of monitored leads. If you use a proxy of your own, you pay your proxy provider for it. The plans are a free 7-day trial, Standard at $49 a month and Pro at $99 a month.
Begin with ten leads on the 7-day trial. Add Claude over MCP, Slack or a proxy of your own whenever you are ready for them.
