Telegram vs Matrix
Telegram MCP (chigwell) and Matrix MCP (mjknowles) both connect an agent to a chat network, but they differ sharply in scale and platform. Telegram's server drives a real user account through Telethon and exposes well over a hundred tools: listing and filtering chats, sending and scheduling messages, editing and deleting messages, pinning, forwarding, reacting, searching globally and within chats, managing contacts, handling media with send_file and send_album and send_voice and send_sticker and send_gif, running polls, administering groups and channels with promote_admin and ban_user and toggle_slow_mode and set_default_chat_permissions, and managing folders, drafts, and invite links. Matrix MCP connects to a self-hosted homeserver such as Synapse and keeps a lean 20-tool surface: listing joined rooms, reading room info and members, pulling messages or messages by date range, identifying active users, checking notification counts, and on the write side sending messages and DMs, joining and leaving rooms, creating rooms, inviting users, and setting room name or topic. The right pick depends on which network your team uses and how much administrative depth the agent needs.
How they compare
| Dimension | Telegram | Matrix |
|---|---|---|
| Platform | Telegram: a centralized cloud platform, accessed through your real user account via the Telethon MTProto library. | Matrix: a federated, open protocol, connected to a self-hosted homeserver (such as Synapse) over HTTP with OAuth. |
| Tool breadth | Over 100 tools covering chats, messages, contacts, media, group and channel administration, folders, and drafts. | 20 tools split into a read tier (rooms, members, messages, profiles, notifications) and a write tier (send, join, create, invite, set name and topic). |
| Message operations | Send, schedule, edit, delete, forward, pin, mark read, reply, search globally with search_global, react with send_reaction, press inline buttons, and save drafts. | Send messages with send-message and send direct messages with send-direct-message; retrieve recent messages with get-room-messages or by date with get-messages-by-date. |
| Group and room administration | Create groups and channels, invite users, promote or demote admins, ban or unban users, set default permissions, toggle slow mode, manage invite links, and review admin action logs. | Create rooms with create-room, join rooms with join-room, leave rooms with leave-room, invite users with invite-user, and set name or topic with set-room-name and set-room-topic. |
| Best-fit task | Agents that need deep automation of Telegram: community moderation, triage across many chats, media delivery, or contact management at scale. | Agents on a self-hosted Matrix homeserver that need to read conversations, post messages, and manage room membership without a heavy administrative surface. |
Verdict
Choose by network and depth. Telegram MCP is the clear pick when your team is on Telegram and the agent needs real administrative reach: scheduling messages, moderating groups with ban_user and promote_admin, handling media, managing contacts and folders, and searching across all chats. Matrix MCP is the right choice when your chat infrastructure is a self-hosted Matrix homeserver and the agent's role is lighter, reading rooms, posting replies, and managing membership through a focused 20-tool surface that runs over OAuth. Neither server crosses the other's network.
FAQ
- Does Telegram MCP require a bot account?
- No. It drives your real Telegram user account through the Telethon MTProto library using an API ID, API hash, and a Telethon session string generated from your my.telegram.org credentials. It also includes get_bot_info and set_bot_commands for managing bots you own, but the server itself authenticates as a user.
- Does Matrix MCP work with any Matrix homeserver?
- It connects to any Matrix homeserver you control, such as Synapse, using the homeserver URL and domain you configure. It supports full OAuth 2.0 when ENABLE_OAUTH is set, plus a development mode that accepts a Matrix access token via header. It runs as an HTTP server, not over stdio.