Create and activate campaigns with create_comment_campaign and activate_campaign
Claude LinkedIn automation
Run a comment campaign by talking to Claude
With Icebreakly connected over MCP, a Claude conversation can do what the dashboard does. Create a campaign, paste in the profiles to watch, hear sample comments in your Voice, approve what is waiting and switch to Autopilot. You say it in plain language and confirm before anything is posted.
See how a comment campaign runs, step by stepBest for
- People who already spend their working day in Claude
- Founders who would sooner type a sentence than learn a dashboard
- Operators managing campaigns for several accounts
The problem
Claude can write a fine LinkedIn comment. On its own it cannot post one, or know who posted today.
Ask Claude to automate LinkedIn and it will, correctly, explain that it has no access to your account. It can draft and advise. The missing piece is a system that watches your leads, holds your Voice, posts at a human pace and keeps count. Icebreakly is that system, and MCP is how Claude reaches it.
Add or remove monitored leads by pasting profile URLs into the chat
Hear sample comments in your Voice with test_comment_voice before going live
Approve, edit or skip pending drafts, with a confirmation before anything posts
How it works
A comment campaign, built in one conversation
Connect Claude to https://mcp.icebreakly.com with an Icebreakly API key
Ask Claude to create a comment campaign in monitor mode, and paste the LinkedIn profile URLs to watch
Have Claude draft sample comments in your Voice, and adjust the Voice until they sound right
Activate the campaign, then return to the conversation whenever you want to review drafts or change settings
A first conversation, turn by turn
The quickest way to see how this works is to follow one session from an empty workspace to a live campaign. The requests are in plain English, and the tool Claude reaches for is named after each one.
- “Create a comment campaign called Q4 target accounts, in monitor mode, with approval on.” Claude calls create_comment_campaign and reports back a draft campaign
- “Add these 25 profiles to it.” You paste the URLs, and Claude calls add_monitor_targets
- “Write three sample comments in my Voice so I can hear the tone.” Claude calls test_comment_voice
- “Make the Voice shorter, and never mention our product.” Claude calls update_prompt to change the length and the guardrails
- “Also like each post we comment on.” Claude calls update_comment_settings
- “Start it.” Claude calls activate_campaign, which checks the LinkedIn account and settings before going live
The conversations that follow
After launch, most sessions are short. You come back to clear the queue, add a few names or check on progress.
A typical morning exchange goes like this. You ask what is waiting, and Claude lists eight drafts with the lead’s name, the subject of the post and the touch number. You say approve one to five, skip six, and change the last line of seven. Claude makes the edit, asks you to confirm, and queues the approvals.
Later in the month you might say that two people have left their companies and should come off the list. Claude calls remove_monitor_targets for those two and leaves the others alone. Or you ask why nothing was posted yesterday, and diagnose_campaign returns the recorded reason, such as a LinkedIn account that needs reconnecting.
What Claude will not do here
The boundaries are worth knowing before you start, since they are the boundaries of the product.
- No connection requests, direct messages, InMail or follow-up sequences. The tools do not exist
- No lead finding. Claude can only add profiles you supply
- No email lookup, CRM sync or exports through Icebreakly
- No posting faster than the product allows. The same pacing applies as in the dashboard
Why run it from a conversation at all
The dashboard is fine. The case for Claude is that the work happens where you already are, and that a sentence is quicker than a form. Pasting forty URLs and saying “add these” beats any import screen. Asking “who moved to Trusted this week” beats sorting a table.
It also combines with whatever else Claude can see. If your account plan sits in a document, you can ask Claude to read it and pick out the named buyers, then add their profiles once you supply the URLs.
- See: /claude-mcp-integration for the setup steps
- See: /linkedin-comment-automation for what the campaign does each day once it is running
- See: /mcp for all 63 tools grouped by purpose
- See: /linkedin-campaign-automation for the four parts of a comment campaign
- See: /pricing for plan limits, which also apply through Claude
FAQ
Common questions about claude linkedin automation
Can Claude automate LinkedIn by itself?
No. Claude has no built-in access to LinkedIn accounts and cannot post, monitor or schedule on its own. It needs a connected system that holds the LinkedIn session and performs the actions. Icebreakly provides that through an MCP server, limited to comment campaigns.
What can Claude do on LinkedIn through Icebreakly?
It can run comment campaigns: create them, add or remove the profiles they monitor, change settings such as Approval or Autopilot and whether to like posts, read and approve pending comments, tune Voices, and report on warming stages and dashboard figures. It cannot send connection requests or messages, because Icebreakly does not do those.
Who writes the comments, Claude or Icebreakly?
Icebreakly drafts them, using the Voice you trained and the content of each post. Claude’s role is to operate Icebreakly on your instruction. You can ask Claude to reword a pending draft, and it will save the edit with update_pending_comment before you approve it.
Do I have to keep the conversation open for the campaign to run?
No. Once a campaign is active it runs inside Icebreakly every day, whether or not Claude is open. The conversation is a control panel. Close it, and the monitoring, drafting and posting carry on.
Is it safe to let an AI assistant control this?
The connection is scoped to one workspace by its API key and goes through the same layer as the dashboard, so posting limits and plan caps still apply. Your client asks for confirmation before a comment or reaction is posted. Claude never handles your LinkedIn password, and deleting the key ends access.
What if I want Claude to send LinkedIn messages too?
Icebreakly will not do that. It has no tools for connection requests, direct messages or InMail. If automated messaging is what you need, look at a sequencer. Icebreakly’s tools cover warming only.