Lets AI assistants control a LinkedIn account to search leads, analyze profiles, read conversations, and send messages.
Also known as Linked-API/linkedapi-mcp, linkedapi-mcp, @linkedapi/mcp
- Stars
- 70
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 2.3.21
- Last commit
- Nov 13, 2026
- License
- MIT
What is Linked API MCP?
Linked API lets AI assistants control a LinkedIn account to search leads, analyze profiles, read conversations, and send messages.
Summary generated from the project's README
About Linked API MCP server
Automating LinkedIn outreach and lead generation from within AI assistants like Claude, Cursor, or VS Code is what this server enables. It connects your LinkedIn account to your development environment through a cloud browser that handles actions automatically. Users can instruct their AI to perform complex tasks such as searching for specific professional profiles, analyzing backgrounds, and managing messages without manual navigation.
Because many operations like profile fetching or searches run through a cloud browser, they are treated as queued automation. When an action is in progress, the server returns a workflowId and operationName instead of an immediate result. Developers should use the get_workflow_result tool to poll for the final outcome rather than retrying the original command. This setup allows for long-running tasks that might take several minutes to complete while maintaining a safe connection to your account.
What you can do with it
- 1Automated Sales ProspectingAsk your AI to find specific leads and draft personalized messages based on their professional backgrounds.
- 2Candidate RecruitmentUse the assistant to search for candidates with specific skills and handle initial outreach tasks.
- 3Conversation ManagementHave your AI read existing chats to suggest contextually relevant replies and follow-up messages.
- 4Market ResearchGather data regarding competitors, company employees, and industry trends directly through your assistant.
Written from the project's README. Every use case is checked against a quote from it.
How to install Linked API MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Linked API MCP in Claude Code
$ claude mcp add --env 'IDENTIFICATION_TOKEN=<YOUR_IDENTIFICATION_TOKEN>' --env 'LINKED_API_TOKEN=<YOUR_LINKED_API_TOKEN>' linkedapi-mcp -- npx -y @linkedapi/mcpInstall Linked API MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"linkedapi-mcp": {
"command": "npx",
"args": [
"-y",
"@linkedapi/mcp"
],
"env": {
"IDENTIFICATION_TOKEN": "<YOUR_IDENTIFICATION_TOKEN>",
"LINKED_API_TOKEN": "<YOUR_LINKED_API_TOKEN>"
}
}
}
}Install Linked API MCP in VS Code
.vscode/mcp.json
{
"servers": {
"linkedapi-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@linkedapi/mcp"
],
"env": {
"IDENTIFICATION_TOKEN": "<YOUR_IDENTIFICATION_TOKEN>",
"LINKED_API_TOKEN": "<YOUR_LINKED_API_TOKEN>"
}
}
}
}Install Linked API MCP in VS Code CLI
$ code --add-mcp '{"name":"linkedapi-mcp","type":"stdio","command":"npx","args":["-y","@linkedapi/mcp"],"env":{"IDENTIFICATION_TOKEN":"<YOUR_IDENTIFICATION_TOKEN>","LINKED_API_TOKEN":"<YOUR_LINKED_API_TOKEN>"}}'Install Linked API MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"linkedapi-mcp": {
"command": "npx",
"args": [
"-y",
"@linkedapi/mcp"
],
"env": {
"IDENTIFICATION_TOKEN": "<YOUR_IDENTIFICATION_TOKEN>",
"LINKED_API_TOKEN": "<YOUR_LINKED_API_TOKEN>"
}
}
}
}Install Linked API MCP in Codex
$ codex mcp add linkedapi-mcp --env 'IDENTIFICATION_TOKEN=<YOUR_IDENTIFICATION_TOKEN>' --env 'LINKED_API_TOKEN=<YOUR_LINKED_API_TOKEN>' -- npx -y @linkedapi/mcpInstall Linked API MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.linkedapi-mcp] command = "npx" args = ["-y", "@linkedapi/mcp"] [mcp_servers.linkedapi-mcp.env] IDENTIFICATION_TOKEN = "<YOUR_IDENTIFICATION_TOKEN>" LINKED_API_TOKEN = "<YOUR_LINKED_API_TOKEN>"
Install Linked API MCP in Gemini CLI
$ gemini mcp add -s user -e 'IDENTIFICATION_TOKEN=<YOUR_IDENTIFICATION_TOKEN>' -e 'LINKED_API_TOKEN=<YOUR_LINKED_API_TOKEN>' linkedapi-mcp npx -- -y @linkedapi/mcpInstall Linked API MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"linkedapi-mcp": {
"command": "npx",
"args": [
"-y",
"@linkedapi/mcp"
],
"env": {
"IDENTIFICATION_TOKEN": "<YOUR_IDENTIFICATION_TOKEN>",
"LINKED_API_TOKEN": "<YOUR_LINKED_API_TOKEN>"
}
}
}
}Configuration
IDENTIFICATION_TOKENRequiredSecretIdentification token for the LinkedIn account from https://app.linkedapi.io.
LINKED_API_TOKENRequiredSecretLinked API access token from https://app.linkedapi.io.
| Name | Description | |
|---|---|---|
| IDENTIFICATION_TOKEN | Identification token for the LinkedIn account from https://app.linkedapi.io. | RequiredSecret |
| LINKED_API_TOKEN | Linked API access token from https://app.linkedapi.io. | RequiredSecret |
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 reachablelinked-api/linkedapi-mcp is public and reachablegithub.com/linked-api/linkedapi-mcp ↗Pass
- Package names this repository as its sourceNot checked
- 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-11-06github.com/linked-api/linkedapi-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @linkedapi/mcpPass
- No critical advisory in the package or its dependencies100 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 handshakeinitialize answered with protocol 2025-06-18 in 539 msPass
README
View on GitHubLinked API MCP server connects your LinkedIn account to AI assistants like Claude, Cursor, and VS Code. Ask them to search for leads, send messages, analyze profiles, and much more – they'll handle it through our cloud browser, safely and automatically.
Use cases
- Sales automation assistant. Ask your AI to find leads, check their profiles, and draft personalized outreach. It can search for "software engineers at companies with 50-200 employees in San Francisco", analyze their backgrounds, and suggest connection messages that actually make sense.
- Recruitment assistant. Let your assistant search for candidates with specific skills, review their experience, and send initial outreach. It handles the time-consuming parts while you focus on actually talking to people.
- Conversation assistant. Your AI can read your existing LinkedIn conversations and help you respond naturally. It understands the context of your chats, suggests relevant replies, and can even send follow-up messages.
- Market research assistant. Need competitor analysis? Your assistant can gather data about companies, their employees, and recent activities. Get insights about industry trends without spending hours on LinkedIn.
Get started
To start using Linked API MCP, spend 2 minutes reading these essential guides:
- Installation – set up MCP in Claude, Cursor, VS Code, or Windsurf.
- Available tools – explore all the LinkedIn tools your assistant can call.
- Usage examples – see real-world examples to get you started quickly.
Long-running actions
Linked API actions run through a cloud browser and are queued like normal automation. Many actions take several minutes, especially searches and profile fetches with optional data.
If a tool returns status, workflowId, operationName, and message, the action is still running. Do not retry the original tool because that can queue duplicate work. Call get_workflow_result with the exact workflowId and operationName until the final result is returned. By default get_workflow_result long-polls until the workflow completes or the current MCP client's request budget elapses; pass waitSeconds: 0 for an immediate single-shot snapshot.
License
This project is licensed under the MIT – see the LICENSE file for details.
Linked API MCP questions
How do I add Linked API MCP to Claude Code?
Run claude mcp add --env 'IDENTIFICATION_TOKEN=<YOUR_IDENTIFICATION_TOKEN>' --env 'LINKED_API_TOKEN=<YOUR_LINKED_API_TOKEN>' linkedapi-mcp -- npx -y @linkedapi/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Linked API MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can an AI assistant do with my LinkedIn account through this MCP server?
It can search for leads, analyze profiles, read existing conversations, and send messages and follow-ups. It can also gather company and employee data for market research.
Why does a tool return a workflowId instead of a result?
Long actions run through a cloud browser and are queued, so the tool returns a status while the work continues. Call get_workflow_result with that workflowId and operationName instead of retrying.
How do I get an immediate result instead of waiting?
Pass waitSeconds: 0 to get_workflow_result for a single-shot snapshot. Otherwise it long-polls until the workflow completes or the request budget runs out.
Which AI clients can use this server?
It works with Claude, Cursor, VS Code, and Windsurf. Setup guides are provided for each.