Telegram MCP Server (chigwell) vs WhatsApp MCP Server (lharries)
A side-by-side comparison of two Communication servers — tools, transport, auth, maintenance, and copy-paste config for each.
| Telegram MCP Server (chigwell) Full Telegram user-account MCP via MTProto: read chats, manage groups, send messages Verified stdio (local) API key Python | WhatsApp MCP Server (lharries) Connect your personal WhatsApp: search, read and send messages and media locally Verified stdio (local) No auth Python | |
|---|---|---|
| Category | Communication | Communication |
| Language | Python | Python |
| Transport | stdio (local) | stdio (local) |
| Auth | API key | None |
| GitHub stars | 1.2k | 5.7k |
| Last commit | 9 days ago | 28 days ago |
| Verified | ||
| Actively maintained | ||
| Install | git clone https://github.com/chigwell/telegram-mcp && cd telegram-mcp && uv sync && uv run main.py | git clone https://github.com/lharries/whatsapp-mcp && cd whatsapp-mcp/whatsapp-bridge && go run main.go |
| Repo | Open | Open |
Verdict
Pick Telegram MCP Server (chigwell) if you prefer its approach (full telegram user-account mcp via mtproto: read chats, manage groups, send messages).
Pick WhatsApp MCP Server (lharries) if you prefer the more popular, battle-tested option, and you want zero-setup with no API key.
Add Telegram MCP Server (chigwell)
git clone https://github.com/chigwell/telegram-mcp && cd telegram-mcp && uv sync && uv run main.pyPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"telegram-mcp-server-chigwell": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/telegram-mcp",
"run",
"main.py"
],
"env": {
"TELEGRAM_API_ID": "<your-telegram-api-id>",
"TELEGRAM_API_HASH": "<your-telegram-api-hash>",
"TELEGRAM_SESSION_STRING": "<your-generated-session-string>"
}
}
}
}Add WhatsApp MCP Server (lharries)
git clone https://github.com/lharries/whatsapp-mcp && cd whatsapp-mcp/whatsapp-bridge && go run main.goPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"whatsapp-mcp-server-lharries": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/whatsapp-mcp/whatsapp-mcp-server",
"run",
"main.py"
]
}
}
}FAQ
Telegram MCP Server (chigwell) or WhatsApp MCP Server (lharries) — which is better?
Pick Telegram MCP Server (chigwell) if you prefer its approach (full telegram user-account mcp via mtproto: read chats, manage groups, send messages). Pick WhatsApp MCP Server (lharries) if you prefer the more popular, battle-tested option, and you want zero-setup with no API key.
Can I use both Telegram MCP Server (chigwell) and WhatsApp MCP Server (lharries)?
Yes — MCP clients let you enable multiple servers at once. Add both configs to your client's mcpServers and use whichever tool fits the task.
Do Telegram MCP Server (chigwell) and WhatsApp MCP Server (lharries) work with Claude, Cursor and Windsurf?
Both do. Copy the per-client config below into Claude Desktop, Cursor, or Windsurf.