LinkedIn Ads MCP: Your Options Without an Official Server

Below: what we searched, why there are so few servers, the options side by side, a checklist for picking one, and the prompts worth asking.

LinkedIn's Marketing API documentation lives on Microsoft Learn, under learn.microsoft.com/linkedin. On 25 October 2026 we searched it, LinkedIn's newsroom and the wider web for an official MCP server or connector for Campaign Manager. Nothing turned up from LinkedIn or Microsoft, and vendor pages written in September and October 2026 report the same.

That puts LinkedIn in an odd spot. Microsoft, which owns LinkedIn, ships an official Microsoft Advertising MCP server for Bing search ads, read-only and free to connect. It does not cover LinkedIn campaigns. Reddit is the only other large ad platform in the same position as LinkedIn.

Meta and Google each have several community servers on GitHub next to their official ones, GoMarble's and Pipeboard's among them. LinkedIn has far fewer, and the reason third parties give is access. According to one vendor's write-up, LinkedIn's Marketing API needs a developer app tied to a LinkedIn Company Page, and the app needs approval for the Advertising API product before it can read campaign data.

• An app tied to a Company PageThe developer app is associated with an organisation on LinkedIn, not only with a person.
• Product approvalAccess to the Advertising API is a product the app has to be approved for, which a hobby project often never gets.
• Most teams use a vendorSo in practice, a team that wants LinkedIn in Claude connects a vendor that already holds the approval, rather than building its own server.

That is a third-party account of LinkedIn's process, not LinkedIn's own words; check LinkedIn's Marketing API docs for the current requirements before you plan a build.

Windsor.ai and Supermetrics are the two you can add from Claude's connector directory rather than as a custom connector. Anthropic says it has not verified third-party servers, directory or not, so the vetting below still applies. How Zapier compares with a direct API job or an MCP connector for recurring reports: MCP vs API vs Zapier for ad reporting.

A connector that reads Campaign Manager and a connector that reads your attribution data answer different questions. Knowing which you are asking saves a setup.

• Delivery questions

  Which campaigns spent the most this week? Where did CTR or CPM move? Which creative has the best click rate? A Campaign Manager connector answers these well.

• Outcome questions

  Which campaigns produced opportunities? What does a qualified lead cost by campaign group? Which creative's leads closed? These need the CRM, which Campaign Manager does not have.

Campaign Manager can show conversions from the Insight Tag, the Conversions API and Lead Gen Forms. If you send CRM stages back through the Conversions API, a Campaign Manager connector sees them as conversions too. Without that, its view ends at the form fill, and on LinkedIn the deal often closes months later. The full argument for any platform: why your ad platform's MCP gives Claude the wrong CPL.

With no official server, every LinkedIn connection runs through somebody else's infrastructure. Five questions to answer before you sign in with an account that has spend on it.

1. Read or write? If the job is reporting, prefer a read-only connection or a read-only permission set. A connector that can change budgets is a risk you only need when you want it to.
2. Who holds the token, and where? The vendor stores an access token to your ad account. Find out where it is kept, for how long, and how to revoke it.
3. What happens to the data? Read the data processing terms: is campaign data stored, for how long, and is it used for anything beyond your request?
4. Which accounts does it see? Sign in with a user who has access to the accounts the connector needs, not every account in the business.
5. What does a write look like? If it can change campaigns, check whether it asks before applying a change and whether new campaigns start paused. Markifact, for one, states that nothing goes live without your approval.

LinkedIn is the platform where the difference between a lead and a customer is widest. Lead Gen Forms make a form fill easy, prefilled from the profile, so a cheap lead says less about intent than on a site form. An assistant reading only Campaign Manager will rank campaigns by cost per lead, which on LinkedIn tends to reward the wrong ones.

The figures are an example. On cost per lead, the broad Lead Gen Form campaign is the winner at less than half the CPL. On cost per opportunity, the demo campaign costs $800 against $2,000. A connector that cannot see the opportunity column will recommend scaling the campaign that builds less pipeline.

Whichever connector you use, specific questions get useful answers. The first four need only Campaign Manager data; the last four need the CRM outcome joined to the campaign.

• "Which LinkedIn campaigns spent the most last month, and how did their CTR change against the month before?"
• "List creatives with a CTR below the campaign average and more than $500 of spend."
• "Compare CPM by campaign group for the last 30 days."
• "Which campaign groups had the highest cost per click last week?"
• "What did a qualified lead cost per LinkedIn campaign last quarter?"
• "Which LinkedIn campaigns produced opportunities, and what is the open pipeline per campaign?"
• "Show the deals won this quarter whose journey included a LinkedIn click, and the touchpoints before the demo."
• "Compare cost per opportunity for Lead Gen Form campaigns against website conversion campaigns."

The prompt shapes for Meta and Google, with the platform's own server: Claude for Meta Ads and Claude for Google Ads.

LinkedIn Ads is a native LeadJourney integration. It imports your campaign groups, campaigns, creatives and daily spend, captures every LinkedIn click with its li_fat_id server-side and first-party, and follows the lead into your CRM: HubSpot, Salesforce, Pipedrive, Close, Attio, GoHighLevel, ActiveCampaign, Odoo, Zoho CRM or Microsoft Dynamics 365. The stages you map go back to LinkedIn through its Conversions API, matched on li_fat_id, so campaigns can optimise on pipeline. More in the LinkedIn Ads integration and sending CRM deals to LinkedIn's Conversions API.

LeadJourney's MCP server puts that data in your assistant without waiting for LinkedIn. Copy the URL (https://api.leadjourney.io/mcp) from Ask Atlas, Settings, MCP, add it in Claude's Connectors, and approve it with OAuth. In ChatGPT, connect LeadJourney from the plugin directory. Then ask the outcome questions above: spend per LinkedIn campaign and ad set, qualified counts, booked demos, open pipeline and won revenue, under the attribution model you choose.

What it does not do: it cannot pause a campaign, change a budget or create an ad, and it is not a Campaign Manager client, so keep a Campaign Manager connector for delivery questions on creatives and audiences. It reads, and it builds reports and dashboards inside LeadJourney, only when you send a message. If you also want an assistant to manage campaigns, that is the Campaign Manager connector's job. The MCP connection is included from the Growth plan and available as an add-on below it.

• Ads MCP servers compared: Meta, Google, LinkedIn, TikTok and more
• Why your ad platform's MCP gives Claude the wrong CPL
• MCP vs API vs Zapier for ad reporting
• Send CRM deals to LinkedIn's Conversions API
• The best LinkedIn Ads tracking tools
• The best LinkedIn revenue attribution tools
• The LinkedIn Ads integration
• LeadJourney in Claude