Is there an official LinkedIn MCP server?
LinkedIn does not publish one. Unipile's server is a LinkedIn MCP server for coding agents built on the Unipile LinkedIn API, acting on accounts your users connect within each account's own limits.
@unipile
Basic information
Transport
Streamable HTTP
Authentication
API Key
Last updated
Category
Developer Tools
Author
unipile
Submitted by
Arnaud
Unipile MCP server: LinkedIn MCP (Sales Navigator, Recruiter), WhatsApp, Instagram, Telegram and email MCP for coding agents. Build your LinkedIn, WhatsApp and email API integration from Cursor, Claude Code, Codex.
https://developer.unipile.com/mcp?branch=v2.0claude mcp add unipile --transport http https://developer.unipile.com/mcp?branch=v2.0Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
Gets detailed information about a specific API endpoint, including security schemes and servers
Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.
Lists all available OpenAPI specs. Use the title to select a spec.
Executes an API request with a given HAR request object.
Unipile MCP Server is a hosted, build-time MCP server that gives coding agents the Unipile API contract for LinkedIn (Classic, Sales Navigator and Recruiter), WhatsApp, Instagram, Telegram, Gmail, Outlook, IMAP and calendars, so they can write and test your integration on your own connected accounts.
Behind it is the Unipile API: one REST API through which your users connect their own LinkedIn, messaging, email and calendar accounts, and your product acts on those accounts with one key. The MCP server is generated from the live OpenAPI spec, so the agent works from real paths, parameters and response shapes. It is used while you build; the code it writes calls the Unipile REST API or the Node.js or Python SDK directly, so your product does not depend on MCP in production. Only repositories under github.com/unipile/* are official.
https://developer.unipile.com/mcp?branch=v2.0 to your coding agent with the key in an X-API-KEY header.The key is optional for reading the API reference; without it the agent can still search endpoints and read schemas. It is required for execute-request. Use a scoped Account API key only: a Global Account API key reaches every account in your application, and a Service API key belongs in your backend. Never commit a key to a shared repository.
claude mcp add --transport http unipile "https://developer.unipile.com/mcp?branch=v2.0" --header "X-API-KEY: YOUR_SCOPED_API_KEY"
Or install the plugin, with the key in the UNIPILE_API_KEY environment variable:
/plugin marketplace add unipile/unipile-mcp
/plugin install unipile@unipile
In claude_desktop_config.json:
{
"mcpServers": {
"unipile": {
"type": "http",
"url": "https://developer.unipile.com/mcp?branch=v2.0",
"headers": { "X-API-KEY": "YOUR_SCOPED_API_KEY" }
}
}
}
In ~/.cursor/mcp.json or .cursor/mcp.json:
{
"mcpServers": {
"unipile": {
"url": "https://developer.unipile.com/mcp?branch=v2.0",
"headers": { "X-API-KEY": "YOUR_SCOPED_API_KEY" }
}
}
}
In .vscode/mcp.json, which prompts for the key instead of storing it:
{
"inputs": [
{ "type": "promptString", "id": "unipile_api_key", "description": "Unipile scoped Account API key", "password": true }
],
"servers": {
"unipile": {
"type": "http",
"url": "https://developer.unipile.com/mcp?branch=v2.0",
"headers": { "X-API-KEY": "${input:unipile_api_key}" }
}
}
}
[mcp_servers.unipile]
url = "https://developer.unipile.com/mcp?branch=v2.0"
http_headers = { "X-API-KEY" = "YOUR_SCOPED_API_KEY" }
The README also has configs for Gemini CLI and Windsurf. For API v1, replace v2.0 with v1.0 in the URL and use your v1 access token as the key.
execute-request sends the same HTTP call your backend will make, against your own test accounts.On branch=v2.0 the server exposes five tools:
search-endpoints searches paths, operations and parameters (for example sales-navigator, inmail or relation-requests); list-endpoints lists every path and method; list-specs lists the available OpenAPI specs.get-endpoint returns one operation's full request and response schema, security and servers.execute-request runs a request for real, as a HAR object, against your own accounts.On branch=v1.0, get-server-variables replaces list-specs.
execute-request fails while search works: reading the reference needs no key, but executing does. Add a scoped Account API key in the X-API-KEY header.branch=v1.0 and use your v1 access token.LinkedIn does not publish one. Unipile's server is a LinkedIn MCP server for coding agents built on the Unipile LinkedIn API, acting on accounts your users connect within each account's own limits.
No. The agent uses MCP to discover and test the API while you build; your product calls the Unipile REST API or an SDK directly.
A scoped Account API key that only reaches the accounts assigned to one Scope. Do not use a Global Account API key or a Service API key.
Yes, in the same server. They share the messaging routes with LinkedIn messages, and Instagram also has posts, stories and comments.
Any client that supports remote MCP over Streamable HTTP with a custom header, including Cursor, Claude Code, Codex, Gemini CLI, VS Code, Windsurf and Claude Desktop.
v2, unless your accounts are in the v1 environment.
The Unipile remote MCP server is a hosted Model Context Protocol endpoint at https://developer.unipile.com/mcp?branch=v2.0, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://developer.unipile.com/mcp?branch=v2.0 to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Yes. Unipile requires an API key — check the official documentation for how to obtain one, then include it in your client's configuration.
Unipile exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
Hosted 3GPP MCP server: cited search across Rel-15 through Rel-20 TS/TR specs, recent TDocs, company proposals and meeting decisions. OAuth 2.1; no local index required.
Convert web pages to clean Markdown and retrieval-ready chunks with browser rendering support.
Write, schedule and publish LinkedIn posts in your own voice, reply to comments and read your analytics, all from your AI assistant. Remote MCP server with OAuth sign-in.
Official 42min MCP server: let Claude, ChatGPT, Cursor or any MCP client manage your meeting scheduling. Check availability, find free slots, book, cancel and reschedule meetings, manage recurring series, secret booking
Live crypto trading signals via API. Full trade setups with entry, stop-loss, take-profit, leverage, and automated verification. Built for Claude Code, OpenAI Codex, and 30+ AI agents.
Comments