To connect LinkedIn ads to Claude Code, you add the Creator OS hosted MCP server to Claude Code, sign in to LinkedIn through Creator OS, and then run LinkedIn sponsored post commands from the Claude Code prompt. There is nothing to install on the server side and no LinkedIn developer app to register. The whole setup is three steps: add the MCP server, connect the LinkedIn account, then talk to your campaigns. This guide walks through each step with the exact commands, plus how to move budgets and pause campaigns without opening the LinkedIn Campaign Manager.
Claude Code Creator OS MCP LinkedIn
----------- -------------- --------
prompt: create a --> ads_create_ad --> sponsored post
LinkedIn ad (validate, pause) created paused
ads_campaign_* review queue
prompt: pause it --> ads_campaign_pause --> paused
What Connecting LinkedIn Ads to Claude Code Actually Means
It does not mean LinkedIn ships an official Claude Code plugin, and it does not mean you write a LinkedIn API client by hand. Creator OS runs a hosted MCP server at https://mcp.creatoros.ca/mcp. Claude Code connects to that server as a tool provider. When you ask for a LinkedIn ad, your agent calls a Creator OS tool, and Creator OS handles the LinkedIn API call, the currency formatting, the ad account lookup and the review rules.
Claude Code registers MCP servers with the claude mcp add command. That is the only install step. The server is already running. You are not cloning a repo or hosting anything.
Why Use Claude Code Instead of the LinkedIn Ads Manager
The LinkedIn Campaign Manager is a web dashboard built for point and click campaign building. Claude Code is a terminal agent that reads your repo, runs commands and keeps context across a session. Once LinkedIn is a tool inside that agent, campaign work becomes part of the same session as your copy, your landing page and your analytics.
The practical difference shows up in repetition. A sponsored post in LinkedIn ads needs a Company Page, an objective, a daily budget of at least 10 units per day, and copy that fits the format. Doing that by hand for each variant is slow. Asking your agent to draft five variants, validate them, and create them paused takes one prompt.
Two things to know before you start. Creator OS creates LinkedIn ads in a paused state, and LinkedIn reviews every ad before it runs. The ads add on costs $19.99 per month on any plan and takes no percentage of ad spend. Your ad spend is billed by LinkedIn to your own ad account.
Prerequisites: LinkedIn Ads Account, Claude Code, and Creator OS
You need four things.
- A LinkedIn ads account with at least one ad account and a Company Page you can sponsor from.
- Claude Code installed and working in a terminal.
- A Creator OS workspace with a LinkedIn account connected, plus the ads add on enabled. The Creator plan is $14.99 per month or $59.99 per year for 11 platforms plus Skool, one account on each. Agency plans cover 5 sets of socials for $49.99 per month, or 10 sets for $99 per month.
- A Creator OS API key that starts with
cos_live_. Keys, MCP access, the CLI and the agent skills are included in every plan.
If your LinkedIn personal account is not yet in Creator OS, connect it first. The ads docs list which networks the add on covers: Meta, Google, TikTok, LinkedIn, X and ChatGPT. If you have not connected Claude Code to Creator OS at all, read the setup post on adding social media to Claude first, then come back here for the ads layer.
Install the LinkedIn Ads MCP Server in Claude Code
One command adds the server with your API key as a bearer token:
claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp \
--header "Authorization: Bearer cos_live_..."Replace the placeholder with your real key. Then confirm Claude Code sees the tools. Ask it to list your connected ad accounts. Claude Code has no separate LinkedIn MCP entry, and that is deliberate. The same server exposes posting, comments, analytics, Skool, the blog and ads. Your agent only calls the ad tools when you ask about ads.
If you prefer a settings file, Cursor, Windsurf and VS Code take an mcpServers entry with type: http, the URL and the Authorization header. The MCP docs show the exact JSON. The Claude page covers the connector flow for the Claude apps.
One decision matters here. Creator OS supports read only and read and write connections. A read only connection only sees read tools, and the API refuses writes from it. Use read only while you are exploring campaign data. Switch to read and write when you actually want to launch or pause. If you later hand this workspace to a contractor or an automated agent, read only is the safer default.
Authenticate Your LinkedIn Ads Account Safely
Two separate credentials are in play, and mixing them up is the most common source of confusion.
The first is your Creator OS API key. It is pinned to one workspace, which is one set of socials. An agent holding one workspace key cannot post to another workspace. Treat it like a password and keep it out of repos and screenshots.
The second is the LinkedIn ads connection itself. In Creator OS you connect LinkedIn and then connect the ads account, which returns you to Creator OS when it finishes. The ads docs cover the flow, and the LinkedIn ads MCP post goes deeper on the LinkedIn specific fields.
Claude Code will keep working if the connection drops, but ad calls will fail. Run the CLI check in a terminal to see the real state:
creatoros auth:check
creatoros ads:connectionsThe second command lists ad connections across networks, so you can confirm LinkedIn is attached before you blame your prompt. Destructive tools such as deleting an ad are marked so the AI app asks for confirmation first. Launching an ad is not destructive, but it does create a paused object in your ad account, so check the output before you move on.
Launch a Sponsored Post From Claude Code Step by Step
Start by asking your agent to list your accounts and audiences. You want two ids: the Creator OS LinkedIn account id, which looks like acc_, and the LinkedIn ad account id.
Then write the ad in plain language in the Claude Code prompt. A prompt that works:
Create a LinkedIn sponsored post ad in ad account act_123456.
Name it "Q3 webinar traffic".
Objective traffic. Budget 20 daily.
Headline: "Build a social agent in an afternoon"
Body: "Free 30 minute walkthrough. We build the agent live."
Link to our sign-up page. CTA LEARN_MORE.
Countries US and CA only. Validate first.Behind the prompt your agent calls the ads_create_ad tool. Under the hood the same work runs through the CLI command creatoros ads:create, which takes --accountId, --adAccountId, --name, --goal, --budget, --budgetType, and optional flags for the headline, body, link, image, CTA, countries and dates. Budgets are whole units of the ad account currency, so no decimals.
Ask for validation first. Creator OS supports a dry run through --validateOnly or validate_only, which checks the shape without creating anything. That catches a missing Company Page, a budget value that LinkedIn will reject, or copy that is too long before you touch the live account. Note the honest limit here: LinkedIn has no native dry run. Creator OS validates what it can, and then LinkedIn reviews the ad itself before it runs.
Read the result carefully. Ads are created paused for review, on every network, by design. Nothing spends until you resume it.
Manage and Pause Campaigns With Natural Language Prompts
This is where the agent earns its place. Once the connection is live, campaign management is a sentence.
Pause a campaign:
Pause the Q3 webinar campaign on LinkedIn.Change a budget:
Raise the daily budget on that ad to 25.Pull results:
Show me LinkedIn ad spend and results for the last 14 days.
Which ads are live right now?Those map to ads_campaign_pause, ads_budget and the analytics tools, and the CLI equivalents are creatoros ads:campaign-pause, creatoros ads:budget and creatoros ads:campaign-analytics. Creator OS also exposes spend and result reads by network, so you can compare LinkedIn against Meta or Google in the same session.
There is a reason to prefer the agent over clicking here. Budget changes are confirmed before they run, and every create can be dry run. That gives you a written record in your terminal of what changed. If you want the campaign builder skills that package this work, run npx @creatoros/cli@latest init. It installs 14 Claude Code skills, including the LinkedIn campaign builder skill and the other network builders. creatoros sync updates skills later without overwriting files you edited, since updates land as .new files.
If you would rather watch the whole loop run before you try it, the walkthroughs on the KevBuildsApps YouTube channel show agents posting, replying and reporting end to end.
Troubleshooting Common Connection and Auth Errors
Four failures cover most of it.
Auth check fails or returns nothing
Your key is wrong, expired or missing the workspace. Run creatoros auth:check. If that fails in the CLI but works in Claude Code, check the --header value in your MCP entry. A key pasted with line breaks or smart quotes is the usual culprit.
Writes are refused
You are on a read only connection. Read only connections only see read tools, and the API refuses writes from them. Reconnect and choose read and write.
LinkedIn is not in the ad account list
Check creatoros ads:connections. If LinkedIn is absent, connect it again and allow the redirect back to Creator OS. Also confirm the ads add on is active, since it is a separate $19.99 per month item on any plan.
A create fails with a validation message
Most LinkedIn creates fail for mundane reasons: no image or video on a sponsored post, a budget that falls under LinkedIn’s own daily minimum, or a missing Company Page. Ask your agent to print the error. Responses use one shape, { error: { code, message, status } }, so the message names the problem. Fix it in the prompt and re-run with validate only.
One more habit worth building. Read the docs page for the ad network before you automate something new. For LinkedIn and the other networks, that is Docs > Ads. For exact request bodies, the base URL lives in the docs, not in a blog post. For the agent side, the CLI docs list every command and flag.
If you want to compare notes on how this looks on other networks, the walkthroughs for Meta ads and Google ads follow the same pattern with different fields.
Get Started With Creator OS
Pick the plan that matches your account count, connect LinkedIn, add the ads add on, and paste the MCP command into Claude Code. The Creator plan is $14.99 per month or $59.99 per year and covers 11 platforms plus Skool, one account on each, which is enough for one brand across the major networks plus Skool. API keys, the MCP server, the CLI and the agent skills are included at every tier, so the LinkedIn ads workflow costs no more than your base plan plus the $19.99 ads add on.
Start at https://www.creatoros.ca/sign-up. Create the workspace, connect LinkedIn, add the ads add on, then run the single claude mcp add command above. Your first prompt can be as small as listing your ad accounts.
Get started for $0
Free trial for new subscribers. Cancel anytime.