How to Connect Linkeddit to Claude as an MCP Connector

01What MCP actually changes

The Model Context Protocol is an open standard for connecting AI assistants to external tools and data at runtime. The practical consequence is narrow but important: a model that has been trained on the public web still knows nothing about your pipeline, your competitors' last pricing change, or which buying questions an answer engine is currently getting wrong about you. MCP is how that data reaches the conversation without a copy-paste step.

It is a protocol, not an integration. You connect Linkeddit once and the same server works in every MCP-compatible client, which is why the setup below is nearly identical across Claude.ai, Cursor, and VS Code. The only real difference between clients is whether they can run the OAuth flow themselves or need a bridge.

02What the connector gives Claude

One authorization exposes 34 tools. They group into three families, and Claude picks the right one from your phrasing. You never type a tool name.

The full list, with every parameter, lives in the tool reference.

03Before you start: two values

You need a Linkeddit account on the Compete plan, and two strings. That is the whole prerequisite list. There is no key to generate, no secret to store.

04Setup: Claude.ai (web)

1. 1Open Settings in Claude.ai, then Connectors.
2. 2Click Add custom connector.
3. 3Paste https://mcp.linkeddit.com/mcp as the connector URL and confirm.
4. 4Claude will report that automatic client registration is not supported. This is expected. Edit the connector and set the OAuth Client ID to linkeddit-mcp-claude, leaving the Client Secret empty.
5. 5Connect, sign in with your Linkeddit account, and click Allow on the consent screen.

Open the tools menu in the chat input to confirm the Linkeddit tools are listed before you start asking. Authorization persists, so this is a one-time step per account.

05Setup: Claude Code

Claude Code speaks HTTP transport and runs the OAuth flow natively, so the whole setup is one command followed by a browser sign-in.

claude mcp add --transport http linkeddit https://mcp.linkeddit.com/mcp

Authorize when prompted, then run claude mcp list to confirm the server is registered. No headers, no bridge, no config file to hand-edit.

06Setup: Claude Desktop, Cursor, and Windsurf

These clients need the mcp-remote package to bridge a remote OAuth server into their local stdio transport. Because Linkeddit uses pre-registered clients rather than dynamic registration, pass the client id to the bridge with --static-oauth-client-info.

{
  "mcpServers": {
    "linkeddit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.linkeddit.com/mcp",
        "--static-oauth-client-info",
        "{\"client_id\":\"linkeddit-mcp-claude\"}"
      ]
    }
  }
}

Config file locations differ by client. Claude Desktop reads ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. Cursor reads .cursor/mcp.json in the project root, and Windsurf uses its own MCP settings file. In all three, restart the client after saving, and use a Node.js 20 or newer npx binary: an older default Node version is the single most common cause of a bridge that silently fails to start.

07Setup: VS Code

VS Code supports HTTP transport for MCP servers directly, so no bridge is needed. Add the server to .vscode/mcp.json in your workspace:

{
  "servers": {
    "linkeddit": {
      "type": "http",
      "url": "https://mcp.linkeddit.com/mcp"
    }
  }
}

Authorize in the browser when prompted. If VS Code asks for an OAuth client id, use linkeddit-mcp-claude with no secret. The tools then appear in agent mode.

08The first three prompts to run

You never name a tool. Describe the outcome and Claude selects and chains the calls. These three exercise a different family each, which is the fastest way to confirm the whole connection works.

09Limits and security

On the connector, access tokens are short-lived and audience-bound to the endpoint, so a token minted for any other resource is rejected. Every tool reads only your own projects, briefs, and audit runs, and mutating tools require an idempotency key so a retried call replays its original result instead of duplicating work. Because authorization is OAuth, revoking access in your Linkeddit account cuts off every client at once. There is no key sitting in a config file to hunt down.

10Troubleshooting

Frequently asked questions