Unipile MCP server

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

Shortened. The full README is on GitHub.