Loading
LinkedIn Campaign Manager
io.github.ZLeventerClaim this server
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
npx -y [email protected]Credentials from the publisher
- LINKEDIN_CLIENT_ID — LinkedIn Developer App OAuth client ID
- LINKEDIN_CLIENT_SECRET — LinkedIn Developer App OAuth client secret
- LINKEDIN_TOKEN_PATH — Absolute path to the OAuth token.json file (created by 'npm run auth')
- LINKEDIN_DEFAULT_AD_ACCOUNT — Default LinkedIn ad account ID (numeric, no urn: prefix). Tools fall back to this when ad_account_id is not passed.
- LINKEDIN_API_VERSION — LinkedIn Rosetta API version in YYYYMM format (default 202504)
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
LINKEDIN_CLIENT_ID=<secret> LINKEDIN_CLIENT_SECRET=<secret> LINKEDIN_TOKEN_PATH=<value> LINKEDIN_DEFAULT_AD_ACCOUNT=<value> LINKEDIN_API_VERSION=<value> claude mcp add io.github.zleventer-linkedin-campaign-manager-mcp -- npx -y linkedin-campaign-manager-mcp@1.0.1Run in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.zleventer-linkedin-campaign-manager-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "LINKEDIN_CLIENT_ID": "<secret>", "LINKEDIN_CLIENT_SECRET": "<secret>", "LINKEDIN_TOKEN_PATH": "<value>", "LINKEDIN_DEFAULT_AD_ACCOUNT": "<value>", "LINKEDIN_API_VERSION": "<value>" } } }}claude_desktop_config.json
Local · npmPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Local- Transport
- stdio
- Version
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ