Summary

One credential, and the professional inbox is readable.

The reach comes from Unipile rather than this server, and that is the trade: a paid subscription in exchange for not building nine integrations. The tool surface is read-focused — pull a chat's messages and reason over them — which suits summarising and triage more than replying.

What it is

An MCP server over the Unipile messaging platform. Unipile already unifies mobile, mail, WhatsApp, LinkedIn, Slack, Twitter, Telegram, Instagram and Messenger behind one API; this puts that unified inbox in front of a model.

What you get

`unipile_get_chat_messages` — every message from a specific chat, taking a required `chat_id` and an optional `batch_size` that defaults to 100, returning an array of message objects with pagination
A dynamic resource at `unipile://messages` giving access to messages from the connected platforms
One conversation surface across the platforms your Unipile account has connected — LinkedIn threads and WhatsApp chats reachable the same way

Requirements

A Unipile subscription, plus the DSN and API key from your Unipile dashboard — set `UNIPILE_DSN` (for example `api8.unipile.com:13851`) and `UNIPILE_API_KEY`. Run it from Docker: pull `buryhuang/mcp-unipile:latest` or build locally, then register the `docker run` command under `mcpServers` in your Claude Desktop config with both variables passed in. Images are built for linux/amd64, linux/arm64 and linux/arm/v7. Package version 0.1.0. MIT.

Setup effort

One command plus a key — docker pull buryhuang/mcp-unipile:latest, then supply credentials