unipile_get_chat_messagesLABSCO 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 requiredchat_idand an optionalbatch_sizethat defaults to 100, returning an array of message objects with pagination- A dynamic resource at
unipile://messagesgiving 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
USE CASES
01
Catching up on a long thread
Pull the full message history of a chat and have the model summarise what was agreed.
02
Working LinkedIn conversations with an assistant
Read the professional threads through the same connection as everything else, and draft responses from what they say.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- docker on PATH
- UNIPILE_DSN in your environment
- UNIPILE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
docker pull buryhuang/mcp-unipile:latestMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"unipile": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"UNIPILE_DSN=<YOUR_UNIPILE_DSN>",
"-e",
"UNIPILE_API_KEY=<YOUR_UNIPILE_API_KEY>",
"buryhuang/mcp-unipile:latest"
]
}
}
}
