Linkedin Pages

npm version License: MIT

MCP server for LinkedIn organization (Company Page) analytics via LinkedIn's Community Management API — follower growth and demographics, page views, post/share engagement, and video stats, surfaced to your AI assistant for analysis the native dashboard can't do.

Built for Claude Code and any MCP-compatible AI tool. Part of The SEO Engine toolkit by Lantern Row.

Scope & data policy

This server is intentionally read-only and limited to aggregate Page reporting data — the category LinkedIn permits storing for up to a year. It does not retrieve individual member-level data (who liked/commented and their profiles), which LinkedIn restricts to short-lived, in-app-only display and prohibits exporting. Keeping to aggregate Page metrics is both the compliant path and the genuinely useful one for trend analysis. There are no posting/write tools.

Access requirements (important)

Unlike most MCPs, this needs an approved LinkedIn developer app:

1. A LinkedIn developer app owned by a registered business, associated with and verified by your Company Page.
2. Approval for the Community Management API (Development tier to build, Standard tier for production — the latter requires a screencast demo).
3. A Page admin completes the 3-legged OAuth flow to produce an access token.

See LinkedIn's app review process. Organic Page analytics is a supported use case; there is no follower minimum or partner-status gate, but approval is a manual review.

Configuration

{
  "mcpServers": {
    "linkedin-pages": {
      "command": "npx",
      "args": ["-y", "linkedin-pages-mcp"],
      "env": {
        "LINKEDIN_ACCESS_TOKEN": "your_3legged_member_token",
        "LINKEDIN_CLIENT_ID": "your_app_client_id",
        "LINKEDIN_CLIENT_SECRET": "your_app_client_secret",
        "LINKEDIN_REFRESH_TOKEN": "your_refresh_token",
        "LINKEDIN_ORGANIZATION_ID": "1234567"
      }
    }
  }
}

LINKEDIN_ACCESS_TOKEN is the only hard requirement; the client id/secret/refresh trio enables automatic token refresh (access tokens last ~60 days).

Tools

Statistics tools accept an optional start_ms/end_ms time range with DAY/WEEK/MONTH granularity; omit the range for lifetime/aggregate figures.

Notes

• Versioned API: requests send Linkedin-Version (default 202606). LinkedIn sunsets versions roughly yearly — bump LINKEDIN_VERSION when migrating.
• Security: credentials come from environment variables only; the bearer token is never logged.

License

MIT © Lantern Row