Data · Local MCP server
Linkedin Ads
MCP server for LinkedIn Campaign Manager - campaigns, creatives, and analytics.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mharnett/linkedin-ads- Version
- 1.0.2
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-13
- Updated
- 2026-03-13
- Publisher
- mharnett (GitHub) · 7 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mharnett) · how
- Listed under
- LinkedIn MCP servers
- Repository
- github.com/mharnett/mcp-linkedin-ads
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mcp-linkedin-ads | 1.0.2 | stdio |
How to connect Linkedin Ads
Linkedin Ads runs locally from a Node.js package published to the npm registry: mcp-linkedin-ads version 1.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y mcp-linkedin-ads@1.0.2. It reads these environment variables: LINKEDIN_CLIENT_ID (required), LINKEDIN_CLIENT_SECRET (required, secret) and LINKEDIN_ACCESS_TOKEN (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"linkedin-ads": {
"command": "npx",
"args": [
"-y",
"mcp-linkedin-ads@1.0.2"
],
"env": {
"LINKEDIN_CLIENT_ID": "<value>",
"LINKEDIN_CLIENT_SECRET": "<secret>",
"LINKEDIN_ACCESS_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from mharnett (GitHub)
| Server | Runs |
|---|---|
| Bing AdsMCP server for Microsoft Advertising (Bing Ads) - campaigns, keywords, and reports. | Local · stdio |
| Ga4Google Analytics 4 MCP: reports, realtime data, custom dimensions, data streams. | Local · stdio |
| Google AdsGoogle Ads MCP with MCC support: 35 tools for campaigns, keywords, reporting, GAQL. | Local · stdio |
| Google GscGoogle Search Console MCP: search analytics, URL inspection, site management. | Local · stdio |
| Gtm Ga4GTM + GA4 MCP: tag management, consent auditing, workspace versioning, reports. | Local · stdio |
| Reddit AdsReddit Ads MCP: campaigns, ad groups, ads, reporting, and audience targeting. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| LinkBitShorten URLs, bulk create, QR, and click analytics for LinkBit. | Local · stdio |
| Linkbreakers MCPQR-driven customer-journey platform for tracked QR codes, short links, and analytics. | Remote · HTTPLive check: sign-in required |
| LinkedinLinkedIn: The LinkedIn Data API offers access to detailed information on individuals, companies. | Remote · HTTPLive check: ✓ handshake |
| LinkedinLinkedIn data for AI agents: search, profiles, companies, posts. Free key, self-minted, no signup. | Remote · HTTPLive check: sign-in required |
| LinkedIn Ads Library (unofficial)Unofficial read-only search over LinkedIn's public Ad Library: 253,610 B2B ads with durations. | Remote · HTTPLive check: sign-in required |
| LinkedIn Ads MCP ServerLinkedIn Ads management and analytics - CRUD, targeting, delivery forecasts, and media uploads. | Remote & Local · HTTP, stdio |
| Linkedin MCPLinkedIn for AI assistants - search, profiles, jobs, feed, messaging, and gated writes. | Local · stdio |
| LinkedIn MCP ServerLinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP. | Remote · HTTPLive check: ✓ handshake |