LinkFetch: LinkedIn MCP Server

by linkfetch Your server? Claim it

answering

LinkFetch: LinkedIn MCP is answering right now. Last checked 9 min ago. 172 installs a week from npm. Last commit 10 Oct 2026.

LinkedIn jobs, companies and people for AI agents, plus messages and invites via your own account.

Installs per day peak 396 · avg 16

a month agotoday

Uptime history 7 days of history · worst day 90%

7 days agonow

92.4%

Uptime 24h

85 of 92 checks

—

Tools

hidden behind auth

121 ms

Response time

average over 24h

172

Installs / week

npm and PyPI

LinkFetch: LinkedIn MCP does not always answer

Over the last week it answered 96.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add linkedin --transport http https://linkfetch.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "linkedin": {
      "url": "https://linkfetch.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.linkedin]
url = "https://linkfetch.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "linkedin": {
      "url": "https://linkfetch.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "linkedin": {
      "url": "https://linkfetch.io/mcp"
    }
  }
}

This one needs environment variables set before it will start: LINKFETCH_API_KEY (Your LinkFetch API key (lf_…), created on the MCP page of the dashboard.). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://linkfetch.io/mcp	streamable-http	needs key	136 ms	9 min ago

Alternatives to LinkFetch: LinkedIn MCP

same job, measured the same way

by johannsenlum

Read LinkedIn profiles, companies, jobs and messages via your own browser session

166 installs/wk local only

gtm-api: LinkedIn MCP Server

by gtm-api

Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.

65 installs/wk answering

LinkedIn MCP Server

by prakharagarwal-dev

Find LinkedIn jobs and people, research companies, manage network, posts, and messages with MCP.

local only

Curviate

by curviate

LinkedIn actions for AI agents: search, messaging, posts and invites, as hosted MCP tools.

answering

HeyReagent LinkedIn MCP

by linglistack

Free to start. Hosted LinkedIn MCP for your own account: inbox, invites, search. Not by LinkedIn.

answering

LinkMCP: hosted LinkedIn MCP server

by linkmcp

Hosted LinkedIn MCP server on your own account: 35 tools for search, profiles, inbox, posts, pages.

answering

Linkedin Data

by superagnt

LinkedIn data for AI agents: profiles, companies, jobs, posts, search. Sales research, recruiting.

answering

HeyLead — AI agent for LinkedIn outreach

by d4umak

AI agent for LinkedIn outreach: finds the right people, writes in your voice, follows up, replies.

17 638 installs/wk answering

LinkFetch: LinkedIn MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for LinkFetch: LinkedIn MCP?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 92.4% of checks in the last 24 hours got a reply.

Is LinkFetch: LinkedIn MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 92 checks got a reply (92.4%), average response time 121 ms. The bar chart above shows every period we have measured.

How do I connect LinkFetch: LinkedIn MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does LinkFetch: LinkedIn MCP need an API key?

Yes. Every time we knock, LinkFetch: LinkedIn MCP answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is LinkFetch: LinkedIn MCP?

It answers our handshake in 121 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use LinkFetch: LinkedIn MCP?

The npm package linkfetch-mcp was installed 172 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is LinkFetch: LinkedIn MCP open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.