Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http linkedin-ads 'https://gateway.pipeworx.io/linkedin_ads/mcp'{
"mcpServers": {
"linkedin-ads": {
"type": "http",
"url": "https://gateway.pipeworx.io/linkedin_ads/mcp"
}
}
}@pipeworx/mcp-linkedin_adsclaude mcp add linkedin-ads -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-linkedin_ads@0.2.0{
"mcpServers": {
"linkedin-ads": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-linkedin_ads@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<your pipeworx_api_key>"
}
}
}
}Environment variables
PIPEWORX_API_KEYsecret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-linkedin_ads
LinkedIn Ads MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
li_list_ad_accounts | Check which LinkedIn ad accounts you can access. Returns account IDs, names, and status to identify which account to use for campaigns. |
li_list_campaigns | Get all campaigns in a LinkedIn ad account (e.g., account ID "501234567"). Returns campaign IDs, names, budgets, status, and date ranges. |
li_get_campaign | Get full details for a specific LinkedIn campaign (e.g., campaign ID "501234567"). Returns name, budget, spend, status, targeting, and performance metrics. |
li_campaign_analytics | Analyze campaign performance over a date range (e.g., "2024-01-01" to "2024-01-31"). Returns impressions, clicks, conversions, spend, and CTR by campaign. |
li_list_creatives | View all ads in a LinkedIn campaign (e.g., campaign ID "501234567"). Returns creative IDs, titles, content, status, and creation dates to compare variations. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"linkedin_ads": {
"url": "https://gateway.pipeworx.io/linkedin_ads/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/linkedin_ads/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack runs against a connected linkedin_ads account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect linkedin_ads, then call POST https://gateway.pipeworx.io/v1/tools/li_list_ad_accounts with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/li_list_ad_accounts. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"linkedin_ads": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-linkedin_ads"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-linkedin_adsIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Linkedin_ads data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Linkedin_ads?
LinkedIn Ads MCP Pack
How do I install Linkedin_ads?
It runs as a remote server. In Claude Code: claude mcp add --transport http linkedin-ads 'https://gateway.pipeworx.io/linkedin_ads/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Linkedin_ads need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Linkedin_ads open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Linkedin_ads?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.