PaidSync>Blog>Platform

LinkedIn Ads MCP Server with Full Write Access

Founder written
Author: Ahmed Ashraf|9 min read|Updated September 2, 2026

34 live tools for LinkedIn Ads, with a dry-run preview on most writes, inside the same server that runs Google Ads, Meta, GA4, and GTM. Compared honestly against AdKit and Adzviser.


Claude Desktop running PaidSync LinkedIn Ads MCP, showing the output of List my LinkedIn ad accounts with client names and account IDs blurred

PaidSync is the LinkedIn Ads MCP that runs and manages LinkedIn campaigns from inside Claude, ChatGPT, or Cursor, connected once, with a dry run before most writes, part of a 13-platform ads and measurement stack starting Free at 15 tasks per month. For LinkedIn-first teams on a budget, AdKit's ads MCP covers LinkedIn from $29 a month with a draft you approve before each change; for teams that also need GA4, GTM or Merchant Center in the same session, PaidSync exposes the full toolset in one MCP server.

An MCP server turns an ad platform's API into typed tools an AI assistant can call. Connect one to Claude or ChatGPT and "pause every LinkedIn campaign with a cost per lead above $120" becomes a command the assistant can verify, propose, and, once you confirm, execute. This page covers PaidSync's LinkedIn surface in full: what the 34 tools do, how writes are checked, what the server deliberately does not cover, and how it compares against the two other LinkedIn Ads MCP options active in August 2026.

The page is written for both audiences. Marketers who want to manage LinkedIn campaigns from a chat window, and agent builders who want to know exactly what the protocol surface looks like before wiring it into a workflow. Each section is labeled so you can skip to what matters.

What a LinkedIn Ads MCP server does

Three things in practice. It reads, so the assistant can pull impressions, clicks, leads, and cost per result without you exporting from Campaign Manager. It writes, so campaigns, campaign groups, ads, creatives, targeting, and conversions can be created or changed through conversation. And it gates, so most writes preview as a dry run first and destructive changes need an explicit confirm. The reading part is available on several LinkedIn MCP options. The depth of the write surface and the honesty of the gating are where they differ.

All 34 LinkedIn tools by category

PaidSync's live server exposes 34 LinkedIn tools (server total 610+ across 14 platforms). All 34 are named in the table below; the live count is also fully discoverable from any session via paidsync_context with include_tools:['linkedin_ads'].

CategoryNamed tools
Account and identityconnect_linkedin_ads, linkedin_auth_status, list_linkedin_ad_accounts, set_linkedin_ad_account
Campaign groupslist_linkedin_campaign_groups, create_linkedin_campaign_group, update_linkedin_campaign_group
Campaignslist_linkedin_campaigns, create_linkedin_campaign, update_linkedin_campaign, pause_linkedin_campaign, enable_linkedin_campaign
Ads and creativescreate_linkedin_ad, update_linkedin_ad, list_linkedin_creatives, create_linkedin_creative, update_linkedin_creative, list_linkedin_creatives_with_media, get_linkedin_ad
Creative mediaupload_linkedin_image, upload_linkedin_video, create_linkedin_image_upload_url
Lead gen formslist_linkedin_lead_forms, create_linkedin_lead_form
Audience and targetingget_linkedin_campaign_targeting, update_linkedin_campaign_targeting, search_linkedin_targeting_entities, get_linkedin_audience_size, get_linkedin_campaign_forecast
Conversionslist_linkedin_conversions, create_linkedin_conversion, add_linkedin_campaign_conversions
Performance reportingget_linkedin_performance, get_linkedin_performance_by_dimension

Three of these carry the most operational weight. create_linkedin_campaign builds a full campaign against an existing campaign group, with objective, bidding type, daily or lifetime budget, targeting facets, and status set in one call. update_linkedin_campaign_targeting patches the targeting spec on a live campaign, job functions, seniorities, industries, company sizes, and member skills, without rebuilding the campaign. And get_linkedin_performance_by_dimension breaks performance by campaign, creative, geography, job function, company size, member age range, or any combination, so cross-cuts that take clicks in Campaign Manager take one prompt here.

For marketers

Run LinkedIn Ads from a chat window

A practical week looks like this. On Monday you ask what changed in the last 7 days across LinkedIn campaigns. The assistant pulls spend, leads, and cost per lead from get_linkedin_performance and gives you a plain-number answer. You spot an ad group targeting too broadly, ask for the targeting breakdown, review it, and ask the assistant to tighten seniority to Director and above. It proposes the update_linkedin_campaign_targeting call with the exact change shown; you confirm, it applies.

Because the same server carries Google Ads (152 tools), Meta Ads (83 tools), GA4 (26 tools), and GTM (39 tools), the follow-up question "did the new LinkedIn creative produce GA4 conversions at a lower CPA" is answered in the same session, not in a separate tab. For teams running cross-channel demand generation, that session continuity is the practical difference between a LinkedIn connector and a paid-media server.

Write access brings an honest concern about safety on live ad accounts. The answer is procedural. Over MCP, the confirmation step is your assistant's own prompt; PaidSync writes no approval card on that path. Most LinkedIn write tools default to dry_run, which returns the planned payload without executing it, and image and video uploads apply on the first call. Sessions can be revoked at any time from the PaidSync connect panel. Read operations never require confirmation because they change nothing.

Connect LinkedIn Ads in Claude or ChatGPT and run the first report in minutes.

Start free, 15 tasks, no card See all plans
For agent builders

The protocol surface behind the 34 tools

PaidSync is one MCP endpoint covering 14 platforms; architecture detail is on the MCP server page. To keep client context small, tools/list returns a lean starter set. The full catalog is discovered at runtime through paidsync_context, which returns the active account, connected platforms, and the grouped tool catalog. Pass include_tools:['linkedin_ads'] to get the exact LinkedIn tool names, signatures, and approval-gate defaults. Then execute any tool through paidsync_exec via await paidsync.call('tool_name', {...args}). That two-call pattern means an agent can enumerate and invoke all 34 LinkedIn tools without a 610+ tool schema payload in every conversation turn.

The server-side checks run whatever the client. Most mutation tools default to dry_run for a no-op preview of the planned change, destructive operations need confirm_destructive, and sessions can be revoked without touching the OAuth client. For discovery and verification, the domain publishes OAuth authorization-server and protected-resource metadata (RFC 8414 and RFC 9728), an MCP server card, agent-auth.json, security.txt, and a Content-Signal directive, so an agent can establish what this server is and how to authenticate before its first task.

LinkedIn's Marketing API enforces rate limits per application per member, at tighter thresholds than Google or Meta for some account classes. High-volume reporting loops (pulling performance for hundreds of campaigns per minute) will hit those limits. Design polling loops with a back-off and prefer dimensional breakdowns over per-campaign loops where possible.

PaidSync vs AdKit vs Adzviser

Several LinkedIn Ads MCP options exist in September 2026, including AdKit, Adzviser, Ryze AI, Adspirer and Pipeboard, which lists LinkedIn as a preview platform. The comparison below covers AdKit and Adzviser, using each vendor's own site as checked on September 23, 2026.

DimensionPaidSyncAdKitAdzviser
LinkedIn tools25Not publishedReporting connector
Write accessFull (create, update, pause, enable)Yes, every change a draft you approveRead-only
Preview and confirm on writesYes, dry_run on most writes, confirm_destructive on destructive callsYes, draft first, approve to publishNot applicable
Platform scope14 platforms (Google, Meta, LinkedIn, TikTok, Snapchat, Reddit, Pinterest, Microsoft, GA4, GTM, GSC, GMC, ChatGPT Ads)Meta, Google, TikTok, LinkedIn, Microsoft, Reddit, X50+ reporting sources, read-only
LinkedIn Marketing PartnerYes, company-verifiedNot listedNot listed
Cross-platform session (LinkedIn + GA4)Yes, same sessionNoYes, reporting only
Conversion tracking creationYes, create_linkedin_conversionNot listedNo
PriceFree $0 (15 tasks), Pro from $99/mo$29/mo one brand, $49/mo unlimited; 7-day free trialFrom $48.99/mo

Quick verdict.

LinkedIn is your main ad channel and your needs are core campaign management: AdKit at $29 a month is the honest budget pick. It covers LinkedIn alongside Meta, Google, TikTok, Microsoft, Reddit and X, and every change waits as a draft for your approval.

You need LinkedIn reporting only and run it alongside 40-plus other data sources: Adzviser covers that reporting use case well, read-only at $48.99 per month.

You run LinkedIn alongside GA4, GTM or Merchant Center, want a free tier, or want to create LinkedIn conversions from chat: PaidSync. One session covers all of it, and most writes preview as a dry run first.

Is there an official LinkedIn Ads MCP server? (checked September 2026)

No. As of September 2026, LinkedIn's developer docs do not list one. The LinkedIn Marketing API documentation covers REST endpoints for Campaign Manager and nothing under the Model Context Protocol. Google, Meta, TikTok, and Microsoft each publish a first-party server for their ad platform. LinkedIn does not. Every LinkedIn Ads MCP you can use today is third party, built on the Marketing API through the vendor's own approved developer application.

Two things follow. A first-party server, if one ships, will most likely cover LinkedIn only, the way Google's official Google Ads server and Microsoft's Advertising server each cover one platform. And the write surface, the approval gating, and the cross-platform session stay the vendor's job. The table uses the same rows as our Google and Meta pages so the gap is easy to read.

DimensionLinkedIn, first partyPaidSync
Who hosts itNobody yet. The developer docs list REST endpoints only, checked September 2026Hosted at mcp.paidsync.ai, connect and go
Read or writeNot defined. The Marketing API itself is read and writeRead and write. 34 LinkedIn tools, 15 reads, 17 writes, 3 of them create campaigns
Which clientsNone, there is no server to addClaude, Claude Code, ChatGPT, Gemini CLI, Copilot Studio, Perplexity, Cursor
Platforms coveredLinkedIn only, if one ships14 platforms in one session, LinkedIn alongside Google, Meta, TikTok, Microsoft, GA4, GTM, and more
Approval gatingNot definedDry-run previews on most writes, confirm_destructive on destructive operations, approval cards in the PaidSync workspace
What PaidSync addsA wrapper LinkedIn has not builtOne endpoint, 610+ tools, cross-platform questions in one prompt, verified LinkedIn Marketing Partner

Connect LinkedIn Campaign Manager to your AI client

The endpoint is the same in every client, https://mcp.paidsync.ai/mcp. Sign-in is OAuth 2.0 with your PaidSync login. Once the client is connected, run connect_linkedin_ads to authorize your Campaign Manager account, then set_linkedin_ad_account to pick the account the session works on. The steps below are checked against each vendor's own docs.

Claude

In claude.ai or the Claude Desktop app, open Settings, then Connectors, search PaidSync, click Connect, and sign in with your PaidSync login. Connectors work on every Claude plan, including Free, which allows one custom connector. Full walkthrough at connect LinkedIn Ads to Claude.

Claude Code

Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp. Start a session, type /mcp, pick paidsync, and sign in with your PaidSync login in the browser window that opens. For a team, commit a .mcp.json at the repo root with the same http server entry. Full guide: LinkedIn Ads in Claude Code.

ChatGPT

Open Settings, then Security and login, and turn on Developer mode. Go to chatgpt.com/plugins, click the plus button, name the app PaidSync, paste the server URL, and choose OAuth. Sign in with your PaidSync login the first time a PaidSync tool runs. Developer mode is available on Plus, Pro, Business, Enterprise, and Education plans on the web. Full walkthrough at connect LinkedIn Ads to ChatGPT.

Gemini CLI

Run gemini mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then /mcp auth paidsync and sign in with your PaidSync login. Gemini Code Assist and Antigravity read an httpUrl entry in ~/.gemini/settings.json. On a personal Google account the Gemini app accepts custom MCP servers under Custom apps for Spark. Full walkthrough at connect LinkedIn Ads to Gemini.

Copilot Studio

Open your agent, then Tools, Add a tool, New tool, Model Context Protocol. Paste the server URL, choose OAuth 2.0 with Dynamic discovery, transport Streamable HTTP. Click Create, then Add to agent, test, then publish to the Microsoft 365 Copilot channel. Copilot Studio needs a work or school account. The consumer Copilot app does not accept custom MCP servers. Full walkthrough at connect LinkedIn Ads to Microsoft Copilot Studio.

Perplexity

Open your profile menu, then All settings, then Connectors, then Custom connector. Name it PaidSync, paste the server URL, choose OAuth and Streamable HTTP, save, and sign in with your PaidSync login when prompted. Custom connectors need a Perplexity Pro, Max, or Enterprise plan.

Cursor

Add {"mcpServers":{"paidsync":{"url":"https://mcp.paidsync.ai/mcp"}}} to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project. Open Cursor Settings, then MCP, and sign in with your PaidSync login when Cursor prompts for OAuth.

A client that lets you set a header, such as Claude Code, can use an API key instead, sent as Authorization: Bearer ps_... or x-api-key. Never put the key in a URL; query strings end up in logs. Applying a change to Google Ads still requires the OAuth sign-in. On LinkedIn and the other platforms a key can apply changes too, so treat it like a password and prefer OAuth.

What this does not do

Stated plainly, because accurate scoping is more useful than overselling.

  • Predictive Audiences beta is not exposed. LinkedIn's Predictive Audiences feature, currently in beta for some account classes, is not in the tool set. Standard saved audiences and targeting facets are fully supported.
  • Document Ads and certain vertical-specific formats are not documented. If Document Ads are central to your LinkedIn strategy, verify support with the PaidSync team before committing.
  • No campaign deletion. Campaigns are paused or archived, not deleted through the API. LinkedIn's own Marketing API design does not surface a bulk delete endpoint; the MCP matches that constraint.
  • One object per task. Creating or updating 15 campaigns is 15 confirmed tasks or a structured loop in your agent. There is no single-call bulk mutator.
  • No organic page posting or LinkedIn Pages management. PaidSync is paid media only.
  • Rate limits apply. LinkedIn's Marketing API enforces per-application rate limits that are tighter than Google Ads or Meta Ads for some account classes and reporting dimensions. High-volume automation loops should build in back-off logic.

Pricing

Every plan includes all 14 platforms and there is no per-account or per-platform charge. The billing unit is tasks: each tool call, read or write, counts as one task. Full detail at paidsync.ai/pricing.

PlanPriceIncluded
Free$0/mo15 tasks a month, no card required
ProFrom $99/mo600 tasks ($99), 1,200 tasks ($149), or 4,000 tasks ($199)
TeamFrom $249/mo5 seats, 6,000 shared tasks per month
Done For YouCustomFully managed paid media
What is a LinkedIn Ads MCP?

An MCP (Model Context Protocol) server exposes an ad platform's API as typed tools that AI assistants like Claude and ChatGPT can call. A LinkedIn Ads MCP lets the assistant read campaign performance, create or edit campaigns, update targeting, and manage conversions through conversation instead of clicking through the LinkedIn Campaign Manager interface. PaidSync's LinkedIn surface covers 34 tools with full write access; Adzviser's LinkedIn connector is read-only, and AdKit's turns every change into a draft you approve before it goes live.

Is there an official LinkedIn Ads MCP server? (checked September 2026)

No. As of September 2026, LinkedIn's developer docs at learn.microsoft.com/en-us/linkedin/marketing list REST endpoints for the Marketing API and no Model Context Protocol server. Google, Meta, TikTok, and Microsoft each publish a first-party server for their ad platform; LinkedIn does not. Every LinkedIn Ads MCP available today is third party. PaidSync covers LinkedIn with 34 tools, read and write, most writes previewed as a dry run first, inside one endpoint that also covers 13 other platforms.

How do I run LinkedIn Ads from Claude or ChatGPT?

Connect PaidSync once at paidsync.ai/signup, then add the MCP endpoint https://mcp.paidsync.ai/mcp to your AI client's MCP configuration. Authorize your LinkedIn Ads account from the connect flow, then ask questions or give commands directly in the chat. Over MCP your assistant's own confirmation prompt is the check before a write runs, and most LinkedIn writes preview as a dry run first. Full setup guides for Claude and ChatGPT are available.

What LinkedIn Ads actions can PaidSync perform?

Full campaign lifecycle: create, update, pause, and enable campaign groups and campaigns. Ad and creative management: create_linkedin_ad, create_linkedin_creative, update_linkedin_creative, list_linkedin_creatives_with_media. Audience and targeting: get_linkedin_campaign_targeting, update_linkedin_campaign_targeting. Conversion tracking: list_linkedin_conversions, create_linkedin_conversion. Performance reporting: get_linkedin_performance and get_linkedin_performance_by_dimension for breakdowns by campaign, creative, geography, job function, company size, and more. The live catalog is discoverable via paidsync_context with include_tools:['linkedin_ads'].

Is PaidSync's LinkedIn Ads MCP write-capable or read-only?

Full write access. PaidSync can create campaigns, campaign groups, ads, creatives, and conversions, and update targeting, budgets, and status. Most writes preview as a dry run first, pauses and budget changes need confirm_destructive, and over MCP your assistant's own confirmation prompt is the human check. Adzviser's LinkedIn connector is read-only. AdKit's LinkedIn MCP can build and change campaigns, and every change lands as a draft you approve in AdKit before LinkedIn sees it.

How does PaidSync's LinkedIn Ads MCP compare to AdKit and Adzviser?

PaidSync has 34 LinkedIn-specific tools with full write access, a dry-run preview on most writes, and is a verified LinkedIn Marketing Partner, inside a 610+ tool server covering 14 platforms. AdKit's ads MCP covers LinkedIn alongside Meta, Google, TikTok, Microsoft, Reddit and X at $29 a month for one brand or $49 for unlimited brands, and every change is a draft you approve first. Adzviser's LinkedIn connector is read-only at $48.99 to $148.99 per month, strong for reporting but cannot create or change anything. If you want the lowest paid price for LinkedIn campaign management, AdKit at $29 a month is the honest budget pick. If you need GA4, GTM or Merchant Center in the same session, or a free tier, PaidSync is the right fit.

What does PaidSync's LinkedIn Ads MCP cost?

Free is $0 for 15 tasks a month with no card required. Pro starts at $99 per month for 600 tasks, with 1,200 tasks at $149 and 4,000 at $199. Team starts at $249 per month for 5 seats and 6,000 shared tasks. Done For You is custom-priced fully managed paid media. Every plan includes all 14 platforms; there is no per-account or per-platform charge. The billing unit is tasks: each tool call, read or write, counts as one task.

Put 34 LinkedIn tools, and the other 13 platforms, in front of your AI assistant today.