Unipile MCP

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:

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

1. 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.

| Group chats: add or remove participants | `