A LinkedIn Ads MCP server lets Claude or ChatGPT answer questions from your LinkedIn ad accounts, such as a client’s spend and leads by campaign. SyncWith’s is hosted, free to start and only reads. Before you ask it what a lead costs, know that LinkedIn gives you two different counts to divide by: its own lead counts, and conversions on your website.
Ask an assistant what your leads cost and it has to divide spend by something. SyncWith gives it both counts as separate fields, so tell it which one you mean:
| What you want | Ask SyncWith for |
|---|---|
| Leads, as LinkedIn counts them | One Click Leads, Qualified Leads or Valid Work Email Leads |
| Conversions on your website | Conversions, with Click Conversions and View Conversions as their own fields |
| Cost per lead | Spend divided by One Click Leads, or Cost per Qualified Lead |
| Cost per website conversion | Cost per Conversion |
Website conversions follow their own rules. View Conversions are the ones LinkedIn credits to someone seeing your ad, not clicking it. How long after a click or a view still counts is set for each conversion. LinkedIn recommends a 90-day click and 90-day view window for most conversions, and you can choose 1, 7, 30 or 90 days. Most conversions go to the last ad the person touched, and with LinkedIn’s default API setting a conversion is “counted once for each campaign to which they can be attributed.”
Blend the two into one cost per lead and some of your “leads” can be website conversions LinkedIn credited to people who only saw the ad.
If you’ve connected another LinkedIn tool too, start each question with “Using SyncWith,” so the assistant picks ours.
Use LinkedIn’s API names. Its Help pages say campaign and ad set, but its API and SyncWith’s fields say Campaign Group and Campaign, and Ad for a single ad. Every ad account gets a campaign group when it’s created, so you may see one in an answer that you never made.
Before a number goes to a client, check three things:
For a client report that updates on a schedule, pull LinkedIn Ads into Google Sheets with SyncWith’s ads add-on or into Looker Studio.
As of November 2026, LinkedIn hasn’t published an official Ads MCP server.
To run the open-source server on GitHub yourself, you need your own LinkedIn developer app with access to LinkedIn’s Advertising API. LinkedIn “reserves the right to review applications and select partners at its discretion,” and its Development tier reads every ad account you administer but makes changes on only 5 ad accounts. SyncWith, Markifact and PaidSync skip the developer app.
The GitHub server, Zapier, Markifact, Windsor, AdKit and PaidSync can each change something in LinkedIn (campaigns, budgets or audiences), some only after you approve it. If you only report, that’s access you don’t need on a client’s ad account. SyncWith’s server has no tool that changes anything in LinkedIn, and the same connection reads your Google Ads, Facebook Ads, GA4 and Shopify.
Looking for a free LinkedIn Ads MCP? The GitHub server is free if you host it. SyncWith’s has nothing to host, and there’s no separate charge for the MCP server today. Each live query uses one refresh from your SyncWith plan, and the free Hobby plan includes 35 refreshes a month. Listing sources and fields doesn’t use any.
https://mcp.syncwith.com/mcp
Every Claude plan can add one, though Free allows a single custom connector. In ChatGPT, an admin of a Business, Enterprise or Edu workspace can add it, and Pro accounts can only read and fetch. Steps for Claude and ChatGPT.
Then check it worked: “Using SyncWith, list my LinkedIn Ads accounts.” If your clients’ accounts come back, you’re set. For every tool the server has, see the SyncWith MCP docs.