Enables AI agents to search LinkedIn jobs, companies, and people, and manage messages and connection requests through a connected account.
Also known as ffucucuoglu/linkedin-mcp-server, linkedin-mcp-server, linkfetch-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 2.0.1
- Last commit
- Oct 9, 2026
- License
- MIT
What is LinkFetch MCP?
LinkFetch enables AI agents to search LinkedIn jobs, companies, and people, and manage messages and connection requests through a connected account.
Summary generated from the project's README
About LinkFetch MCP server
LinkFetch: LinkedIn MCP provides AI agents with a bridge to LinkedIn data and account management. It functions as a stdio bridge to a hosted server, meaning tool calls are processed via a remote endpoint rather than running a local browser. This setup works with clients like Claude Desktop, Cursor, Windsurf, and Zed by using the npx command and a required LINKFETCH_API_KEY.
Users can access public data such as jobs and companies without a LinkedIn account using tools like search_jobs and search_companies. For deeper interaction, connecting a LinkedIn account enables agents to search people, read profiles, manage conversations, and send connection requests. The server also includes AI-driven functions like ai_score and ai_classify to process up to 25 jobs or companies at a time. All operations are subject to credit costs and daily or weekly limits enforced by the LinkFetch platform.
What you can do with it
- 1Automated job market researchAn AI agent can search for and retrieve details on public job postings.
- 2Direct LinkedIn account managementAn agent can interact with your personal inbox and connection requests through a connected account.
Written from the project's README. Every use case is checked against a quote from it.
How to install LinkFetch MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall LinkFetch MCP in Claude Code
$ claude mcp add --env 'LINKFETCH_API_KEY=<YOUR_LINKFETCH_API_KEY>' linkedin-mcp-server -- npx -y linkfetch-mcpInstall LinkFetch MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"linkedin-mcp-server": {
"command": "npx",
"args": [
"-y",
"linkfetch-mcp"
],
"env": {
"LINKFETCH_API_KEY": "<YOUR_LINKFETCH_API_KEY>"
}
}
}
}Install LinkFetch MCP in VS Code
.vscode/mcp.json
{
"servers": {
"linkedin-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"linkfetch-mcp"
],
"env": {
"LINKFETCH_API_KEY": "<YOUR_LINKFETCH_API_KEY>"
}
}
}
}Install LinkFetch MCP in VS Code CLI
$ code --add-mcp '{"name":"linkedin-mcp-server","type":"stdio","command":"npx","args":["-y","linkfetch-mcp"],"env":{"LINKFETCH_API_KEY":"<YOUR_LINKFETCH_API_KEY>"}}'Install LinkFetch MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"linkedin-mcp-server": {
"command": "npx",
"args": [
"-y",
"linkfetch-mcp"
],
"env": {
"LINKFETCH_API_KEY": "<YOUR_LINKFETCH_API_KEY>"
}
}
}
}Install LinkFetch MCP in Codex
$ codex mcp add linkedin-mcp-server --env 'LINKFETCH_API_KEY=<YOUR_LINKFETCH_API_KEY>' -- npx -y linkfetch-mcpInstall LinkFetch MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.linkedin-mcp-server] command = "npx" args = ["-y", "linkfetch-mcp"] [mcp_servers.linkedin-mcp-server.env] LINKFETCH_API_KEY = "<YOUR_LINKFETCH_API_KEY>"
Install LinkFetch MCP in Gemini CLI
$ gemini mcp add -s user -e 'LINKFETCH_API_KEY=<YOUR_LINKFETCH_API_KEY>' linkedin-mcp-server npx -- -y linkfetch-mcpInstall LinkFetch MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"linkedin-mcp-server": {
"command": "npx",
"args": [
"-y",
"linkfetch-mcp"
],
"env": {
"LINKFETCH_API_KEY": "<YOUR_LINKFETCH_API_KEY>"
}
}
}
}Configuration
LINKFETCH_API_KEYRequiredSecretYour LinkFetch API key (lf_…), created on the MCP page of the dashboard.
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableffucucuoglu/linkedin-mcp-server is public and reachablegithub.com/ffucucuoglu/linkedin-mcp-server ↗Pass
- Package names this repository as its sourcelinkfetch-mcp names ffucucuoglu/linkedin-mcp-server as sourcenpmjs.com/package/linkfetch-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-09github.com/ffucucuoglu/linkedin-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from linkfetch-mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubLinkedIn MCP server for Claude, Cursor and any AI agent
linkfetch-mcp gives any AI agent a full set of LinkedIn tools: search every public LinkedIn job since April 2026, look up companies, score and sort them with AI functions, and, through a LinkedIn account you connect, search people and posts, read profiles and your inbox, and send messages and connection requests.
It is a small stdio bridge to LinkFetch's hosted MCP server: every tool call goes to https://linkfetch.io/mcp with your API key, so the tools and prices are always current and nothing runs a browser on your machine. If your client supports remote MCP over HTTP, you can skip this package and use the URL directly.
Full tool list with prices, and setup for each client: linkfetch.io/mcp/claude
Tools
- Jobs and companies (no LinkedIn account needed):
search_jobs,get_job,search_companies,get_company - AI functions:
ai_score,ai_classify,ai_extract,ai_write, each over up to 25 jobs or companies - Your leads:
list_leads,save_lead,list_lead_lists - Through your connected LinkedIn account: people and company search, profiles, employees, posts and reactions, connections, invitations, conversations, messages, comments, reactions, follows
Each call costs a flat number of credits, stated in the tool's description. Every connected account works inside daily and weekly limits that LinkFetch enforces whatever the agent asks for.
Setup
Create an API key (lf_…) on the MCP page of your LinkFetch dashboard. New accounts start with free credits. Then add the server to your client: every client runs npx -y linkfetch-mcp with LINKFETCH_API_KEY set. Node.js 18+ is required.
Upgrading from 0.1.x? Keys starting with
sk_live_stopped working when LinkFetch 2 launched in October 2026. Create a newlf_…key and replace it in your config.
Claude Desktop
Settings → Developer → Edit Config, or edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"linkfetch": {
"command": "npx",
"args": ["-y", "linkfetch-mcp"],
"env": { "LINKFETCH_API_KEY": "lf_..." }
}
}
}
Fully quit and reopen Claude.
Claude Code
claude mcp add linkfetch -e LINKFETCH_API_KEY=lf_... -- npx -y linkfetch-mcp
Cursor, Windsurf, Gemini CLI, Cline
These use the same mcpServers block as Claude Desktop above. Put it in:
| Client | Config file |
|---|---|
| Cursor | ~/.cursor/mcp.json (global) or .cursor/mcp.json (project) |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Gemini CLI | ~/.gemini/settings.json |
| Cline | MCP Servers → Configure → cline_mcp_settings.json |
VS Code (GitHub Copilot agent mode)
.vscode/mcp.json:
{
"servers": {
"linkfetch": {
"command": "npx",
"args": ["-y", "linkfetch-mcp"],
"env": { "LINKFETCH_API_KEY": "lf_..." }
}
}
}
OpenAI Codex CLI
~/.codex/config.toml:
[mcp_servers.linkfetch]
command = "npx"
args = ["-y", "linkfetch-mcp"]
env = { LINKFETCH_API_KEY = "lf_..." }
Zed
settings.json:
{
"context_servers": {
"linkfetch": {
"command": "npx",
"args": ["-y", "linkfetch-mcp"],
"env": { "LINKFETCH_API_KEY": "lf_..." }
}
}
}
Your own agent
Any MCP client library can spawn the server over stdio. OpenAI Agents SDK (Python):
from agents import Agent, Runner
from agents.mcp import MCPServerStdio
async with MCPServerStdio(params={
"command": "npx",
"args": ["-y", "linkfetch-mcp"],
"env": {"LINKFETCH_API_KEY": "lf_..."},
}) as linkfetch:
agent = Agent(name="LinkedIn researcher", mcp_servers=[linkfetch])
result = await Runner.run(agent, "Which companies in Berlin started hiring data engineers this week?")
LangChain users can load the same server with langchain-mcp-adapters.
No install: remote MCP
Clients that support remote MCP over Streamable HTTP can connect to the hosted server directly:
- URL:
https://linkfetch.io/mcp - Header:
Authorization: Bearer lf_...
Claude (desktop or claude.ai): Settings → Connectors → Add custom connector, with https://linkfetch.io/mcp?key=lf_... as the URL.
Claude Code: claude mcp add --transport http linkfetch https://linkfetch.io/mcp --header "Authorization: Bearer lf_..."
Environment variables
| Variable | Required | Default | |
|---|---|---|---|
LINKFETCH_API_KEY |
yes | Your lf_… key |
|
LINKFETCH_MCP_URL |
no | https://linkfetch.io/mcp |
Point at another LinkFetch MCP endpoint |
Errors
A missing, old or rejected key comes back as an error on every request, with what to do about it, so the agent can tell you. Tool errors (no credits left, no LinkedIn account connected, a limit reached) come from the hosted server as normal tool results.
Development
npm install
npm run build
LINKFETCH_API_KEY=lf_... node dist/index.js
src/index.ts is the whole server: it opens one MCP client connection to the hosted server and forwards tools/list and tools/call to it.
License
MIT
LinkFetch MCP questions
How do I add LinkFetch MCP to Claude Code?
Run claude mcp add --env 'LINKFETCH_API_KEY=<YOUR_LINKFETCH_API_KEY>' linkedin-mcp-server -- npx -y linkfetch-mcp in your terminal. Add --scope user to make it available in every project.
How do I add LinkFetch MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What happens if I use an old API key?
Keys starting with sk_live_ are no longer supported; you must create a new lf_… key.