Telegram MCP
An MCP server that gives your AI agent access to your personal Telegram: find a chat, read and search conversations, and send a message when you explicitly ask it to.
- Version
- 1.0
- Clients
- Claude Code, Codex and other MCP clients
- Requires
- Node.js 22 and a Telegram account
- License
- MIT
Why
Without a dedicated connection, an agent reaches Telegram through a browser, Telegram Web, CDP or desktop client files. That is fragile and gives it more access than it needs. Telegram MCP provides one focused entry point: a separate session, ten tools and confirmation for every action that changes something.
What it does
- Chats — recent conversations, search by name or @username, and archived chats.
- History — paginated messages without marking the chat as read.
- Search — across all chats or within one conversation.
- Attachments — save message photos and documents locally.
- Sending — text or files, only with
confirm: true, optionally as a reply. - Sign-in — a Telegram code and two-step verification password, through the terminal or the agent.
Example
Claude Code + Telegram MCP
- youWhat did people say about the release in the work chat yesterday?
- agentlist_dialogs {"query": "work"}
- agentsearch_messages {"peer": "title:Work", "query": "release"}
- agentThree messages. The latest says it is moving to Friday.
- youReply: “Okay, Friday works for me.”
- agentsend_message {"peer": "title:Work", "text": "Okay, Friday works for me.", "confirm": true}
Compatibility
Works with clients that launch MCP servers over stdio. I use it with Claude Code and Codex. Cursor, Claude Desktop and other clients use the same command: node server.mjs.
Status
Version 1.0 is a working tool I use myself. The source is available under MIT: github.com/vixkosla/telegram-mcp.