We use analytics cookies and similar tools to see how LinkMCP is used. You can accept or reject them, and change your choice at any time in Cookie settings. Privacy Policy

Install LinkMCP in any AI client

LinkMCP is a hosted LinkedIn MCP server. Every AI client connects to it with the same server URL. Find your client below: some clients add LinkMCP with one click, others need one command or one entry in a settings file. Most clients then open a browser window where you sign in to LinkMCP. Your own code and servers without a browser use an API key.

Add with one click

These clients have an install link. Click it, check the values that the client shows, and confirm. The client then opens a browser window where you sign in to LinkMCP.

Claude

The link opens Customize → Connectors on claude.ai with the name and the URL filled in. Check them, click Add, then Connect, and sign in to LinkMCP. The connector also works in Claude Desktop and Cowork.

Every plan can add custom connectors; the Free plan allows one. On a Team or Enterprise plan, only an Owner can add one, and members then click Connect.

Add to Claude

Or add it yourself: in Customize → Connectors, click "+", choose "Add custom connector" and paste this URL:

https://app.linkmcp.io/api/mcp?ref=install-claude-url

Guide: Claude LinkedIn Connector: How to Connect Claude to LinkedIn. Source: Claude docs.

Cursor

The link opens Cursor, which asks you to install LinkMCP. Next to LinkMCP, Cursor then shows Needs authentication: click Connect and sign in to LinkMCP in the browser window. The Cursor CLI reads the same settings.

Add to Cursor

Or add this entry to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "linkmcp": {
      "url": "https://app.linkmcp.io/api/mcp?ref=install-cursor-json"
    }
  }
}

Guide: How to Connect Cursor to LinkedIn. Source: Cursor docs.

VS Code (GitHub Copilot)

The link opens VS Code and adds LinkMCP for GitHub Copilot chat after you confirm. When LinkMCP first starts, VS Code asks you to trust it and to sign in in the browser.

Add to VS Code

Or run this in a terminal:

code --add-mcp '{"name":"linkmcp","type":"http","url":"https://app.linkmcp.io/api/mcp?ref=install-vscode-cmd"}'

Source: VS Code docs.

Kiro

The link opens the Kiro IDE, which asks you to confirm before it writes LinkMCP to your MCP config. Kiro then runs the browser sign-in by itself. kiro-cli cannot finish the LinkMCP sign-in yet because of an open Kiro issue (#11677); use an API key there.

Add to Kiro

Source: Kiro docs.

Goose

The link opens Goose Desktop, which asks you to confirm the new extension. Goose then registers itself with LinkMCP and opens the sign-in in your browser.

Add to Goose

Source: Goose docs.

LM Studio

The link opens LM Studio and adds LinkMCP as an MCP server. LM Studio 0.4.10 or later then signs you in to LinkMCP in the browser; older versions have no MCP sign-in.

Add to LM Studio

Source: LM Studio docs.

Replit Agent

The link opens Integrations in Replit with LinkMCP filled in. Replit registers itself with LinkMCP; when the Project Editor asks you to authorize the connection, sign in to LinkMCP. Replit Agent then uses the LinkedIn tools when they fit the task.

Add to Replit

Source: Replit docs.

Poke (Messages, WhatsApp, Telegram)

Poke is an assistant that you text from Apple Messages, WhatsApp or Telegram. The link opens a new Poke integration with the name and the URL filled in; check them and save. Poke registers itself with LinkMCP and signs you in. Ask Poke to show you each LinkedIn message before it sends it.

Add to Poke

Source: Poke docs.

Add with a command or a config file

These clients add LinkMCP with one command or one entry in a settings file. Shell commands put the URL in quotes, because zsh reads ? as a pattern.

Claude Code

Run the command, start Claude Code, type /mcp, select linkmcp and choose Authenticate. --scope user adds LinkMCP to all your projects, not only the current folder. From the shell, claude mcp login linkmcp starts the same sign-in.

claude mcp add --transport http --scope user linkmcp "https://app.linkmcp.io/api/mcp?ref=install-claude-code-cmd"

Guide: How to Connect Claude Code to LinkedIn. Source: Claude Code docs.

Codex (CLI and IDE extension)

The command writes LinkMCP to ~/.codex/config.toml, which the Codex CLI, the IDE extension and the ChatGPT desktop app share. When Codex finds that LinkMCP uses OAuth, it starts the sign-in at once; if it does not, run codex mcp login linkmcp.

codex mcp add linkmcp --url "https://app.linkmcp.io/api/mcp?ref=install-codex-cmd"

Guide: How to Connect OpenAI Codex to LinkedIn. Source: Codex docs.

Gemini CLI

Google stopped Gemini CLI for Google AI Pro, Ultra and free accounts on 18 June 2026. It still works with a Gemini Code Assist Standard or Enterprise license and with a paid Gemini API key. The sign-in starts when Gemini CLI first connects; if it does not, type /mcp auth linkmcp.

gemini mcp add --transport http --scope user linkmcp "https://app.linkmcp.io/api/mcp?ref=install-gemini-cli-cmd"

Guide: How to Connect Gemini to LinkedIn. Source: Gemini CLI docs.

Google Antigravity

Add the entry to ~/.gemini/config/mcp_config.json. In Agent settings → Customizations, click Authenticate next to linkmcp, sign in in your browser, copy the code, paste it back into Antigravity and click Submit.

{
  "mcpServers": {
    "linkmcp": {
      "serverUrl": "https://app.linkmcp.io/api/mcp?ref=install-antigravity-json"
    }
  }
}

If the sign-in does not work for you, use an API key instead. Antigravity does not read environment variables here, so paste the key in place of <your API key>:

{
  "mcpServers": {
    "linkmcp": {
      "serverUrl": "https://app.linkmcp.io/api/mcp?ref=install-antigravity-key-json",
      "headers": {
        "Authorization": "Bearer <your API key>"
      }
    }
  }
}

Guide: How to Connect Gemini to LinkedIn. Source: Antigravity docs.

OpenCode

Add the entry to opencode.json in your project, or to ~/.config/opencode/opencode.json for all projects. OpenCode asks you to sign in the first time it uses LinkMCP; if it does not, run opencode mcp auth linkmcp.

{
  "mcp": {
    "linkmcp": {
      "type": "remote",
      "url": "https://app.linkmcp.io/api/mcp?ref=install-opencode-json"
    }
  }
}

Source: OpenCode docs.

Zed

Add LinkMCP under context_servers in Zed's settings, or in Settings → AI → MCP Servers → Add Server → Add Remote Server. Without an Authorization header, Zed asks you to sign in with OAuth.

{
  "context_servers": {
    "linkmcp": {
      "url": "https://app.linkmcp.io/api/mcp?ref=install-zed-json"
    }
  }
}

Source: Zed docs.

Windsurf (Devin Desktop)

Windsurf is now Devin Desktop. Add the entry to ~/.config/devin/mcp_config.json (on Windows %APPDATA%\devin\mcp_config.json). Devin asks you to sign in the first time it uses LinkMCP; when it shows Needs auth, click Authenticate. On an Enterprise team, an admin must turn on MCP first.

{
  "mcpServers": {
    "linkmcp": {
      "url": "https://app.linkmcp.io/api/mcp?ref=install-windsurf-json"
    }
  }
}

Source: Devin docs.

Hermes Agent

In Hermes Desktop, the link shows the LinkMCP entry and asks you to confirm. Elsewhere, add LinkMCP under mcp_servers in ~/.hermes/config.yaml. On the first connect, Hermes opens the sign-in in your browser; hermes mcp login linkmcp starts it again.

A Hermes gateway (on a server, or in Telegram or Discord) never opens a browser. Use an API key there: put LINKMCP_TOKEN=<your API key> in ~/.hermes/.env and use the second entry.

Add to Hermes Desktop

mcp_servers:
  linkmcp:
    url: "https://app.linkmcp.io/api/mcp?ref=install-hermes-yaml"
    auth: oauth

With an API key:

mcp_servers:
  linkmcp:
    url: "https://app.linkmcp.io/api/mcp?ref=install-hermes-key-yaml"
    headers:
      Authorization: "Bearer ${LINKMCP_TOKEN}"

Source: Hermes Agent docs.

OpenClaw

Stop the OpenClaw Gateway first: the CLI changes saved servers only while it is stopped. Run the command, then openclaw mcp login linkmcp to sign in. Set the transport as shown: without it, OpenClaw uses the older SSE transport. On a running Gateway, an admin adds the server in the Control UI under Settings → MCP instead.

openclaw mcp add linkmcp --url "https://app.linkmcp.io/api/mcp?ref=install-openclaw-cmd" --transport streamable-http --auth oauth

Source: OpenClaw docs.

pi

The command saves LinkMCP to ~/.pi/agent/mcp.json; it does not connect yet. Then run pi mcp login linkmcp: pi registers itself with LinkMCP and opens the sign-in page.

pi mcp add linkmcp --url "https://app.linkmcp.io/api/mcp?ref=install-pi-cmd"

Source: pi docs.

Grok Build

Grok Build opens the LinkMCP sign-in in your browser the first time it uses the server. To sign in at another time, type /mcps in Grok Build, select linkmcp and press i.

grok mcp add --transport http linkmcp "https://app.linkmcp.io/api/mcp?ref=install-grok-build-cmd"

Source: Grok Build docs.

Amp

The next time you start the Amp terminal app, Amp opens the LinkMCP sign-in in your browser. In Amp orbs (cloud sandboxes), a browser sign-in is not available.

amp mcp add linkmcp "https://app.linkmcp.io/api/mcp?ref=install-amp-cmd"

Source: Amp docs.

Factory Droid

droid mcp add saves LinkMCP to your user config. Then type /mcp in Droid to finish the browser sign-in; Droid registers itself with LinkMCP.

droid mcp add linkmcp "https://app.linkmcp.io/api/mcp?ref=install-factory-cmd" --type http

Source: Factory docs.

Warp

In Warp, open Settings → Agents → MCP servers, click + Add and paste the entry. When Warp first starts the server, it opens the LinkMCP sign-in in your browser. Use Warp 2026.10.07 or later: that release fixed the MCP sign-in for servers like LinkMCP.

{
  "linkmcp": {
    "url": "https://app.linkmcp.io/api/mcp?ref=install-warp-json"
  }
}

Source: Warp docs.

Chat apps: paste the URL

These apps have no install link. Open the setting, paste the URL, and sign in to LinkMCP in the window that opens.

ChatGPT

In ChatGPT on the web, open Settings → Security and login and turn on Developer mode. Go to chatgpt.com/plugins, click "+", name the app LinkMCP, paste the URL and sign in. In a new chat, click "+", choose Developer mode and turn on LinkMCP. It needs a paid plan: Plus, Pro, Business, Enterprise or Edu.

https://app.linkmcp.io/api/mcp?ref=install-chatgpt-url

Guide: How to Connect ChatGPT to LinkedIn. Source: OpenAI docs.

Gemini app

On gemini.google.com, open Settings → Connected Apps, click "Add a custom app", paste the URL and sign in. Google allows custom apps for personal Google Accounts in the US, for people aged 18 or over, with Keep Activity on. After that, the app also works in the Gemini mobile app.

https://app.linkmcp.io/api/mcp?ref=install-gemini-url

Guide: How to Connect Gemini to LinkedIn. Source: Gemini Help.

Grok

Go to grok.com/connectors, click "New Connector" and choose "Custom". Enter LinkMCP as the Name, paste the URL as the Server URL, and sign in to LinkMCP in the popup window. Custom connectors work on grok.com without SuperGrok.

https://app.linkmcp.io/api/mcp?ref=install-grok-url

Guide: How to Connect Grok to LinkedIn. Source: xAI docs.

Mistral Vibe (Le Chat)

In Mistral Vibe, formerly Le Chat, open Connectors, click "+ Add Connector" and choose the "Custom MCP Connector" tab. Enter linkmcp as the name, paste the URL and click Connect: Vibe finds the sign-in method by itself. Only an admin can add a connector; on the Free, Pro and Student plans, the account owner is the admin.

https://app.linkmcp.io/api/mcp?ref=install-lechat-url

Source: Mistral docs.

Notion Custom Agents

In a Custom Agent, open Settings → Tools & Access → Add connection → Custom MCP server, paste the URL and click Connect. It needs a Business or Enterprise plan, and a workspace admin must first turn on "Enable custom MCP servers" (Settings → Connections → Manage). Each connection belongs to one agent and uses the account of the person who signed in.

https://app.linkmcp.io/api/mcp?ref=install-notion-url

Source: Notion Help.

Automation platforms

A workflow runs when you are not at the screen. Where the platform takes a Bearer token, use an API key; LinkMCP for builders shows how to create one.

n8n

Attach an MCP Client Tool node to an AI Agent node. Paste the URL into Endpoint, set Server Transport to HTTP Streamable and Authentication to Bearer Auth, and put your API key in the Bearer Token field of the credential.

https://app.linkmcp.io/api/mcp?ref=install-n8n-url

Guide: How to Connect LinkedIn to n8n. Source: n8n docs.

Make

In the MCP Client app, click "Create a connection", then "+ New MCP Server", and paste the URL into the URL field. Then either put your API key in the "API Key / Access token" field, or sign in to LinkMCP when Make asks you to. The MCP Client app is in open beta.

https://app.linkmcp.io/api/mcp?ref=install-make-url

Source: Make docs.

Zapier

On the Apps page in Zapier, click "+ Add connection" and choose MCP Client. Paste the URL as the Server URL, choose Streamable HTTP, set OAuth to No and paste your API key as the Bearer Token. With OAuth set to Yes, Zapier ignores the token and you sign in to LinkMCP in a new window. MCP Client is a beta feature.

https://app.linkmcp.io/api/mcp?ref=install-zapier-url

Source: Zapier Help.

Any other client

Add a remote MCP server with this URL. If the client asks for a transport, choose Streamable HTTP (some clients call it HTTP). If the client opens a browser window, sign in to LinkMCP there. If it asks for a header or a token, use an API key and send it as Authorization: Bearer <your API key>.

https://app.linkmcp.io/api/mcp?ref=install-other-url

Sign in or use an API key

Most clients open a browser window. Sign in to LinkMCP there with your email (you get a 6-digit code) or with Google, and approve the access. A new account starts with the 7-day free trial.

A client that cannot open a browser, such as a server, a messaging gateway or your own code, uses an API key: sign in at LinkMCP, open API Keys → New access key, and send the key as Authorization: Bearer <your key>. Do not put the key in a link, a shared file or a public repository. LinkMCP for builders has the details and code for the most used agent SDKs.

Limits on your LinkedIn account

LinkMCP puts daily limits and pacing on every action through your account, a warm-up limit on connection requests for new or quiet accounts, and a hard monthly usage cap on every plan, so an agent that calls a tool many times in a loop is slowed down or stopped. The limits are on our security page. As with any tool that acts on LinkedIn for you, a restriction cannot be ruled out completely; these limits keep the risk low.

What it costs

LinkMCP starts with a 7-day free trial, and you do not need a credit card. In the trial, profile and company lookups, posts and post comments, and email and phone lookups work. Searches, messages, posting and Sales Navigator act through your own LinkedIn account, and connecting it needs a paid plan. Starter costs $19 per month. New trials get their first month of Starter for $9.50.

How we keep this page current

Each link and command on this page follows the client's own documentation, linked under each client. The LinkMCP team checked them on 12 October 2026. Client apps change their menus often. If a step does not match what you see, write to info@linkmcp.io.