English Français العربية

Linkedin_ads

السجل الرسمي التسويق والمبيعات

LinkedIn Ads MCP Pack

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http linkedin-ads 'https://gateway.pipeworx.io/linkedin_ads/mcp'
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "linkedin-ads": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/linkedin_ads/mcp"
        }
    }
}
NPM package @pipeworx/mcp-linkedin_ads
Claude Code 
claude mcp add linkedin-ads -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-linkedin_ads@0.2.0
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "linkedin-ads": {
            "command": "npx",
            "args": [
                "-y",
                "@pipeworx/mcp-linkedin_ads@0.2.0"
            ],
            "env": {
                "PIPEWORX_API_KEY": "<your pipeworx_api_key>"
            }
        }
    }
}

متغيرات البيئة

  • PIPEWORX_API_KEY سري Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. mcp-linkedin_ads
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-linkedin_ads

LinkedIn Ads MCP Pack

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
li_list_ad_accountsCheck which LinkedIn ad accounts you can access. Returns account IDs, names, and status to identify which account to use for campaigns.
li_list_campaignsGet all campaigns in a LinkedIn ad account (e.g., account ID "501234567"). Returns campaign IDs, names, budgets, status, and date ranges.
li_get_campaignGet full details for a specific LinkedIn campaign (e.g., campaign ID "501234567"). Returns name, budget, spend, status, targeting, and performance metrics.
li_campaign_analyticsAnalyze 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_creativesView 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_ads

It 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

الأسئلة الشائعة

ما هو Linkedin_ads؟

LinkedIn Ads MCP Pack

كيف أثبّت Linkedin_ads؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http linkedin-ads 'https://gateway.pipeworx.io/linkedin_ads/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Linkedin_ads إلى مفتاح API؟

نعم. يتطلب PIPEWORX_API_KEY، وتضبطها في إعداداته.

هل Linkedin_ads مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون Linkedin_ads؟

ينشره pipeworx-io. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.