
LinkedIn Campaign Manager
io.github.ZLeventerPublished by GitHub account ZLeventerv1.0.1Updated Oct 30, 2026
MCP server for LinkedIn Ads — 19 read-only tools for campaigns, performance, and Lead Gen Forms.
Overview
Local MCP server giving an assistant 19 read-only tools to inspect LinkedIn Ads campaigns, performance metrics and Lead Gen Forms.
- What you can do
- Inspect LinkedIn ad accounts and campaigns
- Review campaign performance and reporting metrics
- Look up Lead Gen Forms and their data
- All 19 tools are read-only, so the assistant can query but not change ads
- When to use it
- Useful when you want an assistant to answer questions about LinkedIn Ads performance, campaign structure or lead form results without opening Campaign Manager manually. Suited to marketers and analysts who already have LinkedIn Developer App credentials and an authorized ad account.
- Requirements
- Runs locally over stdio from the npm package linkedin-campaign-manager-mcp, so Node.js is needed. Requires a LinkedIn Developer App OAuth client ID and secret (LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET), an OAuth token file created by the package's auth script and pointed to by LINKEDIN_TOKEN_PATH, and optionally LINKEDIN_DEFAULT_AD_ACCOUNT and LINKEDIN_API_VERSION. Network access to the LinkedIn API is required.
Installation
In SourceWeft
- Open LinkedIn Campaign Manager in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.