LinkedIn Ads

The film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.

18 read tools · 15 write tools, disabled by default.

Run locally with your own LinkedIn app credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the LinkedIn Marketing API. For managed connections, including supported ChatGPT setups, use the hosted option.

What's new

v1.0.1: Zod 4 security update · October 26, 2026

• Update zod to 4.6.7. Every Zod release before 4.6.6 is covered by the high-severity advisory GHSA-mrhx-c7xc-m3w5: validating an oversized constrained collection can exhaust memory, and no Zod 3 release carries the fix. npm audit --omit=dev reports no vulnerability again.
• Keep the Zod 3 validation behaviour. A parameter default is still validated and completed before use, so an omitted object must still supply its required fields.
• Tool names, parameters and descriptions published over MCP are unchanged. server-card.json is regenerated with Zod 4's JSON Schema output, which spells some constraints differently.

Earlier releases

Full changelog · All releases

Source synchronization: SOURCE_SYNC.md.

Upgrade notes

Requires Node.js 22.23.4, 24.22.1, 26.12.1 or a newer release. These carry the October 2026 security fixes, and the server prints a warning on stderr when it runs on an older one. CI covers Node 22, 24 and 26.

This is the first release. Hosted creative galleries, campaign launches and MCP Apps UI are outside it.

Install this release

This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned npx examples later in this document select the version currently available on npm.

git clone --branch v1.0.1 --depth 1 https://github.com/get-mcp-ads/linkedin-ads-mcp-server.gitcd linkedin-ads-mcp-servernpm cinpm run build

Configure your MCP client to run node with the absolute path to dist/cli.js and the variables documented below. Once the package is on npm, the client can run npx -y @getmcpads/linkedin-ads-mcp-server instead, which starts the linkedin-ads-mcp binary.

{  "mcpServers": {    "linkedin-ads": {      "command": "node",      "args": ["/absolute/path/to/linkedin-ads-mcp-server/dist/cli.js"],      "env": {        "LINKEDIN_ADS_ACCESS_TOKEN": "your-member-access-token",        "LINKEDIN_ADS_ACCOUNT_IDS": "512345678"      }    }  }}

npm run doctor reports which variables are set, never their values, and checks the Node.js release.

Prefer a managed connection? Use LinkedIn Ads with hosted getmcpads. Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.

Configuration

Provide these environment variables through the client's secret configuration:

The server validates the configuration at startup and names the variable to fix. It runs no OAuth browser flow and writes nothing to disk: a token renewed through the refresh token stays in memory until the process ends.

What your LinkedIn app needs

LinkedIn Marketing API access is granted per application, so this server runs with an app you own. LinkedIn's quick start describes the steps:

1. Create a LinkedIn Page, then a developer application in the LinkedIn Developer Portal.
2. Request the Advertising API product from the app's Products tab and complete the access form. LinkedIn reviews each request.
3. Every application starts on the Development tier: reads have no account limit, and edits are limited to five ad accounts you administer. On this tier, add each ad account ID under Products, View Ad Accounts. The Standard tier removes the edit limit and is requested through the Developer Support Portal. See access tiers.
4. Generate a member access token with the Token Generator, or your own authorization code flow, with the scopes below. Access tokens last 60 days. Apps approved for programmatic refresh tokens receive a refresh token valid for a year, which this server can use.

Scopes used by the tools of this server:

LinkedIn roles still decide what the token can do. A VIEWER on an ad account can only read, even with rw_ads; writes need ACCOUNT_BILLING_ADMIN, ACCOUNT_MANAGER, CAMPAIGN_MANAGER or CREATIVE_MANAGER (account roles). Media uploads and sponsored image or video ads belong to the Company Page referenced by the ad account, which needs an administrator or sponsored content poster role on that Page. linkedin_health_check lists the configured accounts the token reaches and the ones it does not.

Safety and coverage

Writes preview by default. Review the exact account, target and parameters before repeating the call with confirm: true. Campaign groups, campaigns and ads are created as DRAFT, and sponsored posts use feedDistribution: NONE, so nothing reaches the organic feed. New campaigns keep audience expansion and the LinkedIn Audience Network off. No tool activates delivery: activation, where spend starts, happens in Campaign Manager. A preview flags an edit of budget, bid, schedule or targeting, which can change what an already running campaign spends. Do not retry a write automatically when its result is uncertain. A failed write reports verify_before_retry when a mutation reached LinkedIn and not_applied when none did. This server never retries a mutation; reads retry a network error, HTTP 429 or a 5xx at most twice. Account checks apply before every request. Campaign, group and creative filters are verified against the account before a report, and every write re-reads its account and parent entities. Unknown arguments are rejected. Requests go only to api.linkedin.com, the token endpoint and the signed upload URLs on www.linkedin.com, without following redirects, with timeouts and bounded responses. Upload URLs travel inside HMAC-signed receipts that end with the process, and the upload request carries no token. Tokens and secrets are redacted from every result and error. Budgets and bids are decimal strings in the account currency, such as "20.00" with "EUR", not micros or cents. A report needs at least one entity scope, accepts at most 20 fields and is capped at 15,000 rows; the server applies these limits before the call and says when LinkedIn drops a field instead of returning zero.

This server exposes the native LinkedIn tools of the hosted gateway, plus account discovery, a health check and offline query validation. Audience size estimates, bid and supply forecasts, matched audiences, conversion rules, lead form definitions, experiments, Page statistics and generic endpoint reads are not included in this release. Submitted lead data is never exposed. Use tools/list or server-card.json for exact schemas and the Marketing API documentation for provider details.

Hosted option

getmcpads for LinkedIn Ads manages the hosted connection and account selection. Hosted and source releases can differ. Contact: [email protected].

Development

npm run typechecknpm run lintnpm run buildnpm testnpm run catalog

All tests run offline with mocked fetch responses. No live account is read or changed.

Tools

Every tool is listed below. See server-card.json for complete parameter and output schemas. Every tool except linkedin_list_ad_accounts, linkedin_health_check and linkedin_validate_query takes a configured adAccountId.

License

Apache License 2.0. See NOTICE.

More from getmcpads

Meta Ads · Google Ads · Google Analytics 4 · Google Search Console · TikTok Ads · Pinterest Ads · X Ads

Maintained by Emmanuel at getmcpads. Questions: [email protected].