Data · Remote MCP server
LinkedIn Ads MCP Server
LinkedIn Ads management and analytics - CRUD, targeting, delivery forecasts, and media uploads.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.cesteral/linkedin-mcp- Version
- 1.3.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-10
- Updated
- 2026-06-10
- Publisher
- cesteral (GitHub) · 13 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/cesteral) · how
- Listed under
- LinkedIn MCP servers, Weather MCP servers
- Repository
- github.com/cesteral/mcp-open-advertising
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{host}/linkedin-mcp/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @cesteral/linkedin-mcp | 1.3.0 | stdio |
How to connect LinkedIn Ads MCP Server
LinkedIn Ads MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://{host}/linkedin-mcp/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {host}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @cesteral/linkedin-mcp version 1.3.0. 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 @cesteral/linkedin-mcp@1.3.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"linkedin-mcp": {
"command": "npx",
"args": [
"-y",
"@cesteral/linkedin-mcp@1.3.0"
]
}
}
}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 cesteral (GitHub)
| Server | Runs |
|---|---|
| Amazon DSP MCP ServerAmazon DSP management - CRUD, async reports, targeting, and audience management. | Remote & Local · HTTP, stdio |
| Bid Manager MCP ServerBid Manager reporting and query workflows for DV360 campaign performance analysis. | Remote & Local · HTTP, stdio |
| Campaign Manager 360 MCP ServerCampaign Manager 360 management - CRUD, Floodlight tracking, async reporting, and targeting. | Remote & Local · HTTP, stdio |
| DV360 MCP ServerDV360 campaign management - writes, targeting, custom bidding, previews, and media uploads. | Remote & Local · HTTP, stdio |
| Google Ads MCP ServerGoogle Ads management - campaign writes, GAQL reporting, bulk mutate, validation, and previews. | Remote & Local · HTTP, stdio |
| Meta Ads MCP ServerMeta Ads management - writes, insights, targeting, delivery estimates, previews, and media uploads. | Remote & Local · HTTP, stdio |
| Microsoft Advertising MCP ServerMicrosoft Ads management - CRUD, Google Ads import, ad extensions, and async reports. | Remote & Local · HTTP, stdio |
| Pinterest Ads MCP ServerPinterest Ads management - CRUD, async reports, targeting, and audience estimates. | Remote & Local · HTTP, stdio |
| Search Ads 360 MCP ServerSearch Ads 360 - reporting via query language, insights, and offline conversion upload. | Remote & Local · HTTP, stdio |
| Snapchat Ads MCP ServerSnapchat Ads management - CRUD, async reports, targeting, and audience estimates. | Remote & Local · HTTP, stdio |
| The Trade Desk MCP ServerThe Trade Desk management - CRUD, GraphQL, bulk ops, and async reports. | Remote & Local · HTTP, stdio |
| TikTok Ads MCP ServerTikTok Ads management - CRUD, async reports, targeting, and media uploads. | Remote & Local · HTTP, stdio |
More data servers
| Server | Runs |
|---|---|
| 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 AdsMCP server for LinkedIn Campaign Manager - campaigns, creatives, and analytics. | Local · stdio |
| 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 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 |
| LinkedIn MCP ServerFind LinkedIn jobs and people, research companies, manage network, posts, and messages with MCP. | Local · stdio |
| Linkedin PostsScrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API. | Remote · HTTPLive check: sign-in required |