Linkedin Ads MCP server

LinkedIn Ads MCP Server

Production-grade MCP server for LinkedIn Campaign Manager API. Enables Claude to manage LinkedIn ad accounts, campaigns, ad sets, and creatives with full read/write support.

Features:

• 7 tools -- production-tested
• Multi-account management (multiple LinkedIn ad accounts)
• Campaign and campaign group listing
• Account and campaign performance analytics
• Flexible pivot-based reporting (demographics, device, creative breakdowns)
• Landing page click-based CTR (not total clicks)

Stats:

• ⭐ Production-proven: active campaigns under management
• 📊 Multi-client: Flowspace, Forcepoint, Neon One
• 🔄 CTR accuracy: Uses landingPageClicks (not total clicks with engagement)
• ✅ Full test coverage: 40+ contract tests

Installation

npm install mcp-linkedin-ads

Configuration

Security: Never share your .mcp.json file or commit it to git -- it may contain API credentials. Add .mcp.json to your .gitignore.

1. Get OAuth credentials:

• Go to LinkedIn Developer Portal
• Create a new app with "Sign In with LinkedIn" + "Marketing Developer Platform"
• Scopes: rads, rwads, wmembersocial, rorganizationsocial, worganizationsocial

1. Create config.json:

cp config.example.json config.json

1. Fill in your credentials:

{
     "oauth": {
       "client_id": "YOUR_CLIENT_ID",
       "client_secret": "YOUR_CLIENT_SECRET"
     },
     "clients": {
       "default": {
         "account_id": "YOUR_AD_ACCOUNT_ID",
         "name": "My Account"
       }
     }
   }

1. Set environment variables (recommended for production):

export LINKEDIN_ADS_CLIENT_ID="your_client_id"
   export LINKEDIN_ADS_CLIENT_SECRET="your_client_secret"
   export LINKEDIN_ADS_ACCESS_TOKEN="your_access_token"

Environment variables

Read-only by default

The LinkedIn Ads MCP currently ships with read-only tools only. The write-mode gate is already in place so that any future create/update/pause/enable/remove tool is hidden from ListTools and refused at call time unless LINKEDINADSMCP_WRITE=true is set in the MCP server environment. This mirrors the Google Ads MCP gate and matches the pattern being rolled out to Bing / Reddit / Meta. Motivation: prevent a casual LLM request from mutating production ad accounts without the operator explicitly opting in.

Usage

Start the server

npm start

Use with Claude Code

Add to ~/.claude.json:

{
  "mcpServers": {
    "linkedin-ads": {
      "type": "http",
      "url": "http://localhost:3001"
    }
  }
}

Claude Desktop: Add to ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows).

Example API Calls

// Get client context
linkedin_ads_get_client_context({ working_directory: "/path/to/project" })

Shortened. The full README is on GitHub.