Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, type /mcp, and sign in with your PaidSync login. Claude Code then reaches LinkedIn Campaign Manager through 34 tools: performance by job title, seniority and company, audience sizing, forecasts, campaign groups, campaigns and ads. Claude Code asks before it runs each tool, and most LinkedIn writes preview with a dry run first.
One command. OAuth sign-in, no key pasted. Free plan, 15 tasks a month, no card.
Claude Code talks to remote MCP servers over Streamable HTTP. PaidSync is one of them. Add it once and the same terminal that edits your code can read and change your LinkedIn ad accounts.
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcpBy default that registers the server for the current project only. Add --scope user to make it available in every project on your machine. Run claude mcp list to confirm it is there, then start a session and type /mcp to sign in.
Takes 10 seconds. Google or email sign-in. The free plan is 15 tasks a month at $0, no card.
Click Connect on LinkedIn Ads and sign in with the LinkedIn account that has access to Campaign Manager. LinkedIn Ads authorizes via LinkedIn OAuth. PaidSync stores the tokens encrypted at rest with AES-256-GCM.
Already inside Claude Code? Ask it to run connect_linkedin_ads. The tool returns an OAuth link to open in your browser.
After the sign-in, PaidSync lists the LinkedIn ad accounts that login can reach. Inside a session, list_linkedin_ad_accounts shows them and set_linkedin_ad_account picks the active one.
In your terminal, run:
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcpStart a session, type /mcp, pick paidsync, and sign in with your PaidSync login in the browser window that opens. Claude Code stores the OAuth token for you. No key is pasted anywhere.
Setting this up for a team? Commit a .mcp.json at the repo root so every engineer gets the same connector:
{
"mcpServers": {
"paidsync": { "type": "http", "url": "https://mcp.paidsync.ai/mcp" }
}
}Prefer an API key, for example for headless runs? Send it in a header, never in the URL, where it would end up in logs:
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp --header "Authorization: Bearer $PAIDSYNC_API_KEY"In a committed .mcp.json, add "headers": { "Authorization": "Bearer ${PAIDSYNC_API_KEY}" } so the key stays in each engineer's environment and never enters git. Applying a change to Google Ads still requires the OAuth sign-in. On other platforms a key can apply changes too, so treat it like a password and prefer OAuth.
In a Claude Code session ask: “Show me LinkedIn campaign performance for the last 30 days”
Claude Code returns impressions, clicks, spend, CTR, CPC and conversions for each campaign. The connection is live.
Each prompt below maps to tools in the PaidSync LinkedIn Ads group. Claude Code picks the tool. The last column says whether the call can change anything in the ad account.
| Ask | Tools it calls | Changes your account? |
|---|---|---|
| “Show campaign performance for the last 30 days” | get_linkedin_performance | No |
| “Break down spend and CTR by job title and by seniority” | get_linkedin_performance_by_dimension | No |
| “How many members does VP of Marketing in Germany reach?” | search_linkedin_targeting_entities, get_linkedin_audience_size | No |
| “Forecast impressions and clicks for that audience at $100 a day” | get_linkedin_campaign_forecast | No |
| “Create a campaign group and a draft campaign for that audience” | create_linkedin_campaign_group, create_linkedin_campaign | Yes, after you confirm |
| “Pause the campaign with the highest CPC” | pause_linkedin_campaign | Yes, after you confirm |
| “Change the intro text and destination URL on this ad” | update_linkedin_ad | Yes, after you confirm |
The -p flag runs Claude Code without the interactive session. Sign in once through /mcp and the stored OAuth token carries over. A report that lands in a file looks like this:
claude -p "Pull last 30 days LinkedIn performance by job title and list the five titles with the lowest cost per conversion." \
--allowedTools "mcp__paidsync" \
--output-format json > reports/linkedin-ads-$(date +%F).jsonReads run straight through, and so do writes. --allowedTools "mcp__paidsync" allows every PaidSync tool, writes included, with no prompt. For an unattended job, allow only the read tools it needs, each by name as mcp__paidsync__tool_name.
Of the 34 LinkedIn Ads tools, 15 only read and 17 can write. Reads cover performance, breakdowns by creative, company, job title, industry, seniority, country and region, targeting, audience counts, forecasts, conversions and lead forms.
Writes cover campaign groups, campaigns, targeting, creatives, ads, conversions and lead gen forms. Most writes preview by default with dry_run. Image and video uploads apply on the first call.
Over MCP, the approval step is Claude Code’s own prompt. It asks before it runs a tool unless you allowed it with --allowedTools or in your settings. PaidSync adds checks on its side. Deletes, pauses and budget changes need confirm_destructive, and a pre-write rule check blocks unsafe arguments. The approval card and one-tap undo apply only in the PaidSync workspace.
When the image sits on your machine rather than a public URL, create_linkedin_image_upload_url returns a one-time upload link. It takes JPEG, PNG or GIF up to 5 MB, works once, and expires after 15 minutes. Claude Code can run the upload for you:
curl -X PUT --data-binary @ad.jpg -H "Content-Type: image/jpeg" "<put_url>"The response carries the image URN that create_linkedin_ad takes. Video goes through upload_linkedin_video from a public URL, up to 200 MB.
Sign up at paidsync.ai, connect LinkedIn Ads via LinkedIn OAuth in the dashboard, then run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp in your terminal. Type /mcp inside a session, pick paidsync, and sign in with your PaidSync login.
Yes. LinkedIn Ads is a build tier platform in PaidSync. Claude Code can create campaign groups, campaigns, creatives, ads, conversions and lead gen forms. New campaigns start as drafts, most writes preview as a dry run first, and Claude Code asks before it runs each tool.
Yes. search_linkedin_targeting_entities turns names like a job title or company into the IDs LinkedIn needs, get_linkedin_audience_size counts the members, and get_linkedin_campaign_forecast returns LinkedIn’s own forecast. None of these change the account.
Yes. Once you have signed in through /mcp, claude -p reuses the stored OAuth token. Reads run straight through. Writes need care. No one is there to answer the Claude Code prompt, so any write tool you allowed with --allowedTools runs straight through. For an unattended job, allow only the read tools it needs.
Yes. The free plan is $0 for 15 tasks a month with no card. Pro starts at $99 a month and Team at $249 a month.
34 LinkedIn Ads tools. One command in Claude Code.