Back to Browse

Linkedapi MCP Server

Developer ToolsUse Caution2.5MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

Manage LinkedIn messages, connections, posts, and profile data through Linked API.

About

Manage LinkedIn messages, connections, posts, and profile data through Linked API.

Remote endpoints: streamable-http: https://mcp.linkedapi.io/mcp

Security Report

2.5
Use Caution2.5Critical Risk

This LinkedIn automation server is consistent with its stated purpose and has no hardcoded secrets or shell execution, but it has notable security concerns. In HTTP mode it listens on 0.0.0.0 and falls back to the server's LINKED_API_TOKEN env var for any unauthenticated caller, so anyone who can reach the port can drive the LinkedIn account. Conversation and profile content is logged in full, and the send_feedback tool is instructed to transmit user-derived content to the vendor without asking the user. Supply chain analysis found 7 known vulnerabilities in dependencies (0 critical, 4 high severity). Package verification found 1 issue.

7 files analyzed · 15 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

network_listen

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

account_write

Check that this permission is expected for this type of plugin.

account_read

Check that this permission is expected for this type of plugin.

admin_account_management

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Linked API access token from https://app.linkedapi.io.Required

Environment variable: LINKED_API_TOKEN

Identification token for the LinkedIn account from https://app.linkedapi.io.Required

Environment variable: IDENTIFICATION_TOKEN

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

Linked 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:

  1. Installation – set up MCP in Claude, Cursor, VS Code, or Windsurf.
  2. Available tools – explore all the LinkedIn tools your assistant can call.
  3. 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.

Reviews

No reviews yet

Be the first to review this server!