Log inSubmit server
Linkedin Ads logo

Linkedin Ads

Inspect LinkedIn ad accounts, campaigns, creatives, and date-range performance through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Linkedin Ads

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "linkedin-ads-2": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-linkedin_ads"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Linkedin_ads MCP server exposes LinkedIn advertising account and campaign data through five MCP tools. It can list accessible ad accounts, inspect campaigns and creatives, and return campaign analytics such as impressions, clicks, conversions, spend, and CTR. Use the hosted Pipeworx endpoint when you want gateway access, or run the package locally over stdio without a Pipeworx account. The hosted connection also includes shared Pipeworx meta-tools, while the standalone package exposes only the LinkedIn Ads tools.

Use cases

  • List accessible LinkedIn ad accounts
  • Review campaign budgets and statuses
  • Analyze campaign performance by date range
  • Compare creatives within a campaign

Key features

  • Ad account discovery
  • Campaign listing
  • Campaign detail lookup
  • Date-range analytics
  • Creative listing

Tools5

What Linkedin Ads lets your agent do. Expand a tool for its parameters.

Self-reported~207 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-linkedin_ads (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads434Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.
Tools exposed5Callable tools this server registers over MCP.

How Linkedin Ads works

What Linkedin_ads MCP server does

The Linkedin_ads MCP server gives an MCP client read access to LinkedIn advertising information through the Pipeworx gateway or a local package. Its five pack-specific tools cover account discovery, campaign browsing, campaign detail lookup, performance analysis, and creative listing.

Use li_list_ad_accounts to find accessible ad accounts and their IDs, names, and statuses. li_list_campaigns returns campaigns for a selected account, including budgets, statuses, and date ranges. For one campaign, li_get_campaign provides details such as budget, spend, targeting, status, and performance metrics. li_campaign_analytics compares campaign results over a supplied date range, including impressions, clicks, conversions, spend, and CTR. li_list_creatives lists the ads in a campaign with IDs, titles, content, status, and creation dates.

How it works

The hosted option uses the MCP endpoint at https://gateway.pipeworx.io/linkedin_ads/mcp. It connects through Pipeworx to a linked LinkedIn Ads account. The pack endpoint lists the five LinkedIn tools plus shared Pipeworx meta-tools, including ask_pipeworx, discover_tools, search_within, and memory tools. The exact tool scope is reported by the connection's initialize response.

A full Pipeworx gateway connection at https://gateway.pipeworx.io/mcp exposes the broader catalog directly. Both gateway URLs can use ask_pipeworx to route questions across the catalog, although the pack endpoint lists this pack's tools directly.

The standalone Linkedin_ads MCP server communicates over stdin and stdout. It answers MCP initialize, tools/list, and tools/call requests and exposes only the five pack tools, without the gateway's shared meta-tools.

Setup and configuration

For a hosted connection, add the pack URL to an MCP client configuration. Sign in at Pipeworx, connect the LinkedIn Ads account, and use a Pipeworx key for HTTP tool calls. Direct HTTP requests can call a tool such as li_list_ad_accounts at https://gateway.pipeworx.io/v1/tools/li_list_ad_accounts with a bearer authorization header.

For local use, configure the package with the command npx -y @pipeworx/mcp-linkedin_ads, or run that command directly to verify startup.

Tools and capabilities

  • Discover accessible LinkedIn ad accounts.
  • List campaigns within a selected ad account.
  • Retrieve detailed campaign configuration and metrics.
  • Analyze campaign performance for a date range.
  • Compare creatives within a campaign.

Limitations and notes

The Linkedin_ads MCP server documents inspection and analytics operations only; it does not document campaign creation, editing, budget changes, or creative publishing. The tool examples use numeric account and campaign identifiers, so callers need to identify the relevant account before querying campaigns. Hosted connections include additional gateway schemas, which can increase the tool set beyond the five pack-specific tools. The local package avoids those shared tools but does not provide ask_pipeworx routing.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Linkedin Ads

Linkedin_ads is an MCP server that connects AI clients to LinkedIn Ads through Pipeworx. Its main tools list accessible ad accounts, retrieve campaigns, inspect campaign details, analyze performance by date range, and list campaign creatives. It can run through the hosted gateway or locally over stdio.

Run `npx -y @pipeworx/mcp-linkedin_ads` and configure that command as a local stdio MCP server. This mode does not require a Pipeworx account. You can instead add the hosted endpoint `https://gateway.pipeworx.io/linkedin_ads/mcp` to an MCP client after connecting a LinkedIn Ads account in Pipeworx.

Yes, the hosted MCP endpoint can be added to Cursor. Configure `https://gateway.pipeworx.io/linkedin_ads/mcp` as the server URL, then use a connected LinkedIn Ads account through Pipeworx.

Yes, `li_campaign_analytics` analyzes campaigns over a supplied date range. Its results include impressions, clicks, conversions, spend, and CTR by campaign.

Related MCP servers

All in Social Media All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLinkedin Ads AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/linkedin-ads-2?style=directory)](https://allmcps.com/mcp/linkedin-ads-2)
HTML Embed
<a href="https://allmcps.com/mcp/linkedin-ads-2"><img src="https://allmcps.com/api/badge/linkedin-ads-2?style=directory" alt="Linkedin Ads on AllMCPs" /></a>