██╗     ██╗███╗   ██╗██╗  ██╗███████╗██████╗ ██╗███╗   ██╗
██║     ██║████╗  ██║██║ ██╔╝██╔════╝██╔══██╗██║████╗  ██║
██║     ██║██╔██╗ ██║█████╔╝ █████╗  ██║  ██║██║██╔██╗ ██║
███████╗██║██║ ╚████║██║  ██╗███████╗██████╔╝██║██║ ╚████║
             MCP ZERO - public-first LinkedIn intelligence

🎨 System Flow

🔌 Works With

• ✅ Claude Desktop (Fully verified)
• ✅ Claude Code (Fully verified)
• ✅ Cursor (Fully verified)
• ✅ VS Code + Copilot (Fully verified)
• ✅ Cline / Roo Code (Fully verified)
• ✅ Any standard Stdio/HTTP MCP client

📊 Feature Comparison

Compare LinkedIn MCP Zero against the next most popular alternatives:

Install In One Command

uvx linkedin-mcp-zero --doctor

Verify after install:

uvx --refresh-package linkedin-mcp-zero linkedin-mcp-zero --verify-client claude-desktop

Browser mode:

uvx --refresh-package linkedin-mcp-zero linkedin-mcp-zero --install-client claude-desktop --with-extra browser

Tool Inventory

Default Tools: 30 Working

These work without LinkedIn login or browser setup.

Browser Tools: +11

Enable with --with-extra browser or --enable-browser. These are read-only, but they use your logged-in browser session.

Gated Private-Risk Tool: +1

Default mode exposes 30 usable tools: 29 core local/public tools plus search_jobs_multi, which falls back to LinkedIn-only results unless the multi extra is installed. Browser tools appear only with --enable-browser or --with-extra browser in an installed client config. Voyager/private API mode is hidden unless explicitly enabled.

Tool counts:

Safety Model

No tool posts, likes, connects, follows, applies, or sends messages.

Browser Mode

Install browser dependencies into the isolated uvx runtime:

uvx linkedin-mcp-zero --install-client claude-desktop --with-extra browser

Start Chrome with remote debugging and log in manually:

google-chrome --remote-debugging-port=9222

Then call check_session from your MCP client.

Global Playwright installs do not count for uvx; use --with-extra browser.

Token Usage Tracking

Claude Desktop has no built-in per-MCP token counter. This server provides a privacy-safe tracker instead:

• Estimated tokens: ceil(response_chars / 4), always on.
• Exact-style counts: optional Anthropic /v1/messages/count_tokens.
• Full tool responses are not stored in the metrics database.
• Exact-style counting sends the counted response text to Anthropic only when ANTHROPIC_API_KEY and LINKEDIN_MCP_EXACT_TOKEN_COUNT=true are both set.

Enable exact-style counting:

ANTHROPIC_API_KEY=sk-ant-... LINKEDIN_MCP_EXACT_TOKEN_COUNT=true uvx linkedin-mcp-zero

Use a different token-count model if needed:

LINKEDIN_MCP_TOKEN_COUNT_MODEL=claude-sonnet-4-5

Usage tools:

get_usage_stats
get_tool_usage_summary
reset_usage_stats

Avoid terminal transcript logging as a token strategy; it can expose private profile, inbox, resume, or job data.

Client Config

Print without editing files:

uvx linkedin-mcp-zero --print-config --client claude-desktop
uvx linkedin-mcp-zero --print-config --client vscode

Claude Desktop and Cursor use:

{
  "mcpServers": {
    "linkedin-zero": {
      "command": "/absolute/path/to/uvx",
      "args": ["linkedin-mcp-zero"]
    }
  }
}

VS Code uses:

{
  "servers": {
    "linkedin-zero": {
      "command": "/absolute/path/to/uvx",
      "args": ["linkedin-mcp-zero"]
    }
  }
}

Doctor

uvx linkedin-mcp-zero --doctor
uvx linkedin-mcp-zero --doctor --json

Checks OS, Python, RAM, disk, Chrome, CDP URL, display state, optional extras, and recommended mode.

Development

uv sync --extra dev
uv run --extra dev ruff check .
uv run --extra dev pytest
uv build

Publish only the new version files:

UV_PUBLISH_TOKEN=... uv publish dist/linkedin_mcp_zero-0.3.2*