LinkedIn MCP Server

Project

A Model Context Protocol (MCP) server that provides a practical, capability-aware LinkedIn API toolset to AI agents such as opencode, Claude, Cursor, and other MCP clients.

Table of Contents

• Why another LinkedIn MCP server
• What it provides
• Getting started
• Prompt examples
• Tool reference
• Data & safety notes
• Limitations
• License

Why another LinkedIn MCP server?

What it provides

Current scaffold includes:

• OAuth code flow for interactive browser login (auth_start -> auth_finish)
• token bootstrap and refresh helpers
• per-tool capability matrix in src/linkedin_mcp/tool_catalog.json
• raw authenticated helpers for fast endpoint expansion
• wrapped tools for profile, org ACLs, posts, comments, reactions, media upload, and ads

Getting started

You need an MCP-capable client (opencode, Claude Desktop, Cursor, etc).

LinkedIn app registration

1. Open the LinkedIn Developer portal and create a new app.
2. In app auth settings, add an OAuth redirect URL, for example http://127.0.0.1:8765/callback.
3. Copy Client ID and Client Secret into your environment.
4. Under products/scopes, request only what you need now (start with sign-in scopes).
5. Ensure the redirect URL in app settings exactly matches LINKEDIN_REDIRECT_URI.

1. Install

Option A - local editable install (recommended for development)

Requirements: Python 3.10+.

pip install -e .
linkedin-mcp-full

Option B - uvx from source folder

Requirements: uv (uvx) and a local clone of this repository.

uvx --from . linkedin-mcp-full

2. Configure environment

Copy .env.example and set values (or export directly in shell).

Required variables (and usually the only ones you need):

• LINKEDIN_CLIENT_ID
• LINKEDIN_CLIENT_SECRET
• LINKEDIN_REDIRECT_URI (example: http://127.0.0.1:8765/callback)

3. Register with your MCP client

Example for opencode (~/.config/opencode/opencode.json):

{
  "mcp": {
    "linkedin": {
      "type": "local",
      "enabled": true,
      "command": ["uvx", "--from", "git+https://github.com/oliverhruby/linkedin-mcp.git", "linkedin-mcp-full"],
      "env": {
        "LINKEDIN_CLIENT_ID": "{env:LINKEDIN_CLIENT_ID}",
        "LINKEDIN_CLIENT_SECRET": "{env:LINKEDIN_CLIENT_SECRET}",
        "LINKEDIN_REDIRECT_URI": "{env:LINKEDIN_REDIRECT_URI}"
      }
    }
  }
}

Restart your MCP client after config changes.

Prompt examples

Tool reference

Data & safety notes

• Write tools are explicit and default to dry-run where feasible.
• Capability checks prevent many avoidable permission failures.
• API behavior still depends on LinkedIn app approvals and user/org roles.

Limitations

• This is a scaffold-first implementation, not complete LinkedIn API coverage.
• LinkedIn API availability depends on app-level approvals and account roles.
• Token persistence is currently in-memory; restart requires re-auth or env token.

License

MIT © Oliver Hrubý