LinkedIn Campaign Manager

Install LinkedIn Campaign Manager in your MCP client

LinkedIn Campaign Manager is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.

1. Locate your client's MCP config file.
   • Cursor: ~/.cursor/mcp.json
   • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
   • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
   • VS Code: Settings → Extensions → MCP
   • Windsurf: Settings → MCP Servers
2. Add LinkedIn Campaign Manager to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing mcpServers object.
3. Restart your client so it picks up the new server.
4. Verify — ask the assistant to list available tools; LinkedIn Campaign Manager's tools should appear.

{
  "mcpServers": {
    "linkedin-campaign-manager": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-campaign-manager-mcp"
      ],
      "env": {
        "LINKEDIN_CLIENT_ID": "<your-linkedin-client-id>",
        "LINKEDIN_CLIENT_SECRET": "<your-linkedin-client-secret>",
        "LINKEDIN_TOKEN_PATH": "<your-linkedin-token-path>",
        "LINKEDIN_DEFAULT_AD_ACCOUNT": "<your-linkedin-default-ad-account>",
        "LINKEDIN_API_VERSION": "<your-linkedin-api-version>"
      }
    }
  }
}

npm package: linkedin-campaign-manager-mcp

Required environment variables

LinkedIn Campaign Manager needs the following environment variables set before it can run. Add them to the env block of your mcpServers entry, or export them in your shell before launching the client.

• LINKEDIN_CLIENT_ID
• LINKEDIN_CLIENT_SECRET
• LINKEDIN_TOKEN_PATH
• LINKEDIN_DEFAULT_AD_ACCOUNT
• LINKEDIN_API_VERSION

Transport

LinkedIn Campaign Manager supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.

More automate.revenue_ops.personalization MCP servers

Other Model Context Protocol servers in the same space as LinkedIn Campaign Manager. Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.

• apollo-mcp-server

  MCP server for Apollo.io — people search, contact management, sequences, and organization enrichment via the Model Context Protocol

• lgl-mcp-server

  MCP server for Little Green Light CRM. Search donors, log gifts, manage groups and contacts.

• mcp

  MCP server for SeldonFrame — AI-native Business OS platform. v1.2.0: complete the default personality + add CTA defense layers. The Ironclad Roofing demo exposed the gap that v1.1.9 didn't catch: roofing fell through to coaching personality, both CTAs wen

• media-mcp

  MCP Server for video enhancement and image segmentation (SAM3)

• Salesforce Marketing

  MCP server for Salesforce — 47 tools for leads, campaigns, pipeline, attribution, and reporting.

• mcp-1c

  MCP server for 1C:Enterprise — read+write CRM/ERP through Claude/Cursor/Cline.

• Provar MCP Server

  Provar MCP: AI-powered Salesforce test automation. Generate, validate, migrate, and run tests.

• mcp-server

  MCP server for TrustPager — connect Claude to your CRM

Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.