Linkedin Ads MCP Server

Linkedin Ads MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for LinkedIn Ads - access and analyze advertising data across all linked ad accounts using Claude AI.

What you get

An MCP (Model Context Protocol) server that enables Claude AI to access and analyze your LinkedIn Ads data. Built for marketers, founders, and growth teams who want to leverage AI for campaign optimization, performance reporting, and data-driven advertising decisions.

• 25 Specialized Tools — - Covering accounts, campaigns, creatives, audiences, conversions, analytics, and full campaign management (create, update, delete)
• Comprehensive Metrics — - Every report includes: Spend, Impressions, Clicks, CTR, Reach, Frequency, Engagements, Engagement Rate, CPM, CPC, Conversions, Conversion Rate, Cost per Conversion, Audience Penetration, and Average Dwell Time
• Single OAuth Authentication — - Authenticate once and access all your LinkedIn ad accounts
• Automatic Token Refresh — - Tokens refresh automatically before expiration
• Rate Limit Handling — - Built-in exponential backoff for API rate limits
• Human-Readable Names — - Demographic data shows actual names (not IDs) for seniorities, job functions, industries, and more

Configuration and credentials

You will need 4 environment variables: LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET, MY_CLIENT_ID, MY_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by danielpopamd; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Linkedin Ads MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the linkedin ads mcp mcp server does with a few real requests.