Unipile MCP Server: LinkedIn MCP, WhatsApp MCP and Email MCP for coding agents

The Unipile MCP server gives your coding agent a LinkedIn MCP server (Classic, Sales Navigator and Recruiter), a WhatsApp MCP, an Instagram MCP, a Telegram MCP, an email MCP for Gmail, Outlook and IMAP, and a calendar MCP for Google and Outlook, all in one hosted server. Plug it into Cursor, Claude Code, Codex, Gemini CLI, VS Code or Windsurf. Your agent then reads the exact Unipile API contract, writes your product's LinkedIn, WhatsApp or email integration in your stack, and tests each call on your own connected accounts before you commit.

https://developer.unipile.com/mcp?branch=v2.0

Behind the server is the Unipile API: one REST API for the LinkedIn API, WhatsApp API, Instagram API, Telegram API, email API and calendar API. Your users connect their own accounts, and your product acts on those accounts with one key.

Who it's for

Teams building a SaaS product that needs to talk to its users' LinkedIn, WhatsApp or email accounts:

• Sales engagement, CRM and AI SDR tools: LinkedIn search and Sales Navigator lead lists, invitations, messages and InMails, synced with email and WhatsApp.
• ATS and recruiting software: LinkedIn Recruiter search, candidate profiles, hiring projects, InMails, job postings and applicants.
• Unified inbox, helpdesk and CRM sync: one message and email schema across LinkedIn, WhatsApp, Instagram, Telegram, Gmail, Outlook and IMAP.
• Scheduling and AI assistants: Google and Outlook calendar events, availability and invitations next to the conversations.

The MCP server is a build-time tool. Your agent uses it in the editor to discover, write and test the integration. The code it writes calls the Unipile REST API directly, or the Node.js or Python SDK, so your product does not depend on MCP in production.

Where it saves time

Building a LinkedIn, WhatsApp or email integration usually means reading API docs page by page and copying request schemas by hand. You also have to learn the provider quirks, such as how a Sales Navigator search differs from a Recruiter one, or how an InMail differs from a message. Then comes trial and error with curl. With the MCP server connected, your agent does that loop itself:

You:    Add a "Connect on LinkedIn" button to our CRM contact page. It sends an
        invitation with the rep's note and shows whether it is still pending.

Agent:  search-endpoints  "relation-requests"
        get-endpoint      POST /v2/{account_id}/users/me/relation-requests
        get-endpoint      GET  /v2/{account_id}/users/me/relation-requests
        -> writes the service, the route handler and the UI state in your codebase
        execute-request   sends a real invitation from your test LinkedIn account to a test profile
        -> checks the response against the schema, then hands you the diff

• No invented endpoints. The server is generated from the live OpenAPI spec, so the agent works from the real paths, parameters and response shapes. They never drift from the API.
• LinkedIn account types stay distinct. Classic, Sales Navigator and Recruiter each have their own search routes, filters and InMail options. The agent reads the right one instead of guessing.
• Tested before it is committed. The request the agent runs is the same HTTP call your backend will make in production.

Quick start

1. In the Unipile dashboard, connect a test account (LinkedIn, WhatsApp, Gmail...), then create a Scope for it and a scoped Account API key. See API keys.

2. Add the server to your coding agent with the buttons above, or for Claude Code:

   bashCopy

   claude mcp add --transport http unipile "https://developer.unipile.com/mcp?branch=v2.0" --header "X-API-KEY: your-scoped-api-key"
   

3. Describe the feature you want to build, for example:

   • "Build a Sales Navigator lead search screen with seniority and headcount filters, using the Unipile API."
   • "Sync our users' WhatsApp and LinkedIn conversations into our inbox, with a webhook for new messages."
   • "Add Gmail, Outlook and IMAP sending to our sequences, with replies threaded under the original email."

Configs for Cursor, VS Code, Codex, Gemini CLI, Windsurf and Claude Desktop are in Setup.

What you can build, route by route

Every route below is Unipile API v2 and runs on behalf of a connected account: {account_id} is its acc_... ID, from GET /v2/accounts/. This list is a map for you and your agent, not a schema: the agent should call get-endpoint on a route before writing its request body.

LinkedIn MCP server: the LinkedIn API for your agent

Sales Navigator MCP: the LinkedIn Sales Navigator API

The account needs a Sales Navigator seat. When a user holds several LinkedIn contracts, list them with GET /v2/{account_id}/linkedin/contracts and pick one with POST .../contracts/{contract_id}/select.

LinkedIn Recruiter MCP: the LinkedIn Recruiter API

The account needs a Recruiter seat.

WhatsApp MCP, Instagram MCP, Telegram MCP: one messaging API with LinkedIn

One set of routes serves every messaging provider: WhatsApp chats and groups, Instagram DMs, Telegram chats and groups, and LinkedIn messages. A unified inbox is one integration, not four.

Email MCP: the Gmail, Outlook and IMAP email API

One schema for all three providers, so you write the email integration once.

Calendar MCP: Google Calendar and Outlook Calendar API

Posts and engagement: LinkedIn and Instagram

Account connection, multi-tenancy and webhooks

API version: v2 by default, v1 still available

The branch query parameter picks which Unipile API the server reads from and calls. Use branch=v2.0: every example in this README targets v2. If your integration still runs on the v1 API, switch to branch=v1.0 and put your v1 access token in X-API-KEY; the rest of the client config stays the same.

v1 and v2 are separate environments. An account connected in one is not visible from the other, and a key from one does not work on the other. Use the branch that matches the environment your accounts live in.

On v1, the agent reads your DSN from the get-server-variables tool and must be given it before calling execute-request.

API keys

The key goes in the X-API-KEY header of the MCP connection. It is optional for reading the API reference: without a key, the agent can still search endpoints and read their schemas. It is required for execute-request.

v2 has three kinds of key. Give an MCP client a scoped Account API key only:

The agent can still read the schemas of the management routes (/v2/scopes, /v2/api-keys, /v2/webhooks) and write the backend code that calls them with your Service key. Never commit a key to a shared repository.

Tools

On branch=v2.0 the server exposes five tools:

On branch=v1.0, get-server-variables replaces list-specs and the tools take no title.

Setup

Every client below speaks Streamable HTTP and takes the key in an X-API-KEY header. For v1, replace v2.0 with v1.0 in the URL and use your v1 access token as the key.

{
  "mcpServers": {
    "unipile": {
      "url": "https://developer.unipile.com/mcp?branch=v2.0",
      "headers": { "X-API-KEY": "your-scoped-api-key" }
    }
  }
}

{
  "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}" }
    }
  }
}

claude mcp add --transport http unipile "https://developer.unipile.com/mcp?branch=v2.0" --header "X-API-KEY: your-scoped-api-key"

/plugin marketplace add unipile/unipile-mcp
/plugin install unipile@unipile

[mcp_servers.unipile]
url = "https://developer.unipile.com/mcp?branch=v2.0"
http_headers = { "X-API-KEY" = "your-scoped-api-key" }

{
  "mcpServers": {
    "unipile": {
      "httpUrl": "https://developer.unipile.com/mcp?branch=v2.0",
      "headers": { "X-API-KEY": "your-scoped-api-key" }
    }
  }
}

{
  "mcpServers": {
    "unipile": {
      "type": "http",
      "url": "https://developer.unipile.com/mcp?branch=v2.0",
      "headers": { "X-API-KEY": "your-scoped-api-key" }
    }
  }
}

Any other MCP client or agent framework (OpenAI Agents SDK, Claude Agent SDK, LangChain, LlamaIndex, CrewAI, a custom client) connects the same way: Streamable HTTP with header auth.

From the editor to production

• SDKs: Node.js/TypeScript and Python wrap the same endpoints the agent discovers through MCP. Ask the agent to use them in the code it writes.
• n8n: @unipile/n8n-nodes-unipile is a community node that exposes the same channels as typed resources and operations, for workflows with no code and no agent in the loop.

FAQ

Is there a LinkedIn MCP server? LinkedIn does not publish an official one. The Unipile MCP server is a LinkedIn MCP server for coding agents, built on the Unipile LinkedIn API. It acts on the LinkedIn accounts your users connect, within each account's own limits.

Is there a Sales Navigator MCP or a LinkedIn Recruiter MCP? Yes, in the same server. Sales Navigator has its own lead and account search, lead lists and InMail; Recruiter has its own candidate search, hiring projects, pipeline and InMail. See Sales Navigator MCP and LinkedIn Recruiter MCP.

Is there a WhatsApp MCP, an Instagram MCP or a Telegram MCP? Yes. WhatsApp chats and groups, Instagram DMs and Telegram chats share the same messaging routes as LinkedIn messages. Instagram also has posts, stories, comments and location search, under Posts and engagement.

Is there a Gmail MCP, an Outlook MCP or an IMAP MCP? Yes. One email schema covers Gmail, Outlook and any IMAP mailbox: search, read threads, send, reply, drafts, folders and attachments.

Does my product need MCP in production? 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.

Which coding agents does it work with? Any client that supports remote MCP servers over Streamable HTTP with a custom header: Cursor, Claude Code, Codex, Gemini CLI, VS Code, Windsurf and Claude Desktop, plus agent frameworks.

Should I use v1 or v2? v2, unless your accounts are in the v1 environment. See API version.

Notes

• Only repositories under github.com/unipile/* are official. Other GitHub repositories built on the Unipile API are third-party projects that Unipile does not maintain.
• This repository is the distribution kit for the hosted server: registry manifest, directory listing copy and setup notes. It does not run a second server. The URL at the top, documented at developer.unipile.com/docs/mcp, is the only one.

Registry manifest

server.json is the MCP registry manifest for this server. It is used for the official registry submission and by directories that ingest it (Glama, PulseMCP, mcp.so...). It declares branch as a URL variable (v2.0 by default, v1.0 optional) and X-API-KEY as a required secret header.