# Chatroost Telegram MCP server > Read, search, reply and react in your own Telegram account from an AI assistant, using MTProto as a userbot. - Listing: https://mcp.tc/i/chatroost-telegram - Connect: use the server's own URL `https://mcp.mcp-telegram.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Communication & Meetings](https://mcp.tc/c/communication) - Vendor: mcp-telegram - Homepage: - Repository: - Package: npm `@overpod/mcp-telegram` ## About An unofficial Telegram server that connects an AI assistant to your personal Telegram account over MTProto, running as a userbot instead of a bot. It can read and search chats and message history, reply, react, and work with contacts, forum topics, folders, stickers, polls, scheduled messages, stories and account settings. The project describes 182 tools. It runs as a hosted endpoint with OAuth sign-in (scope mcp:read) or locally via the npm package @overpod/mcp-telegram with npx or Docker. The local setup needs Node.js 18 or later, a Telegram API ID and API hash from my.telegram.org, and a QR code login with the Telegram app. A 2FA password is needed if the account has one. ## What it can do - Read chats, contacts and message history from your own account - Search messages across all chats at once - Reply to messages and react to them - Work with forum topics, polls and scheduled messages - Browse and send stickers - Manage chat folders, profile and privacy settings - Read channel and supergroup statistics ## Example prompts - "Summarize my unread Telegram messages from today" - "Search all my Telegram chats for the hotel booking confirmation" - "Reply to my last message from Anna saying I will be there at 6" - "List the topics in my team forum group and show unread counts" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http chatroost-telegram https://mcp.mcp-telegram.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **chatroost-telegram** and choose **Authenticate**. A browser window opens for the mcp-telegram sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Chatroost Telegram** and paste this URL: ```url https://mcp.mcp-telegram.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when mcp-telegram asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.mcp-telegram.com/mcp` and click **Add**. 3. Click **Connect** and sign in when mcp-telegram asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.mcp-telegram.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to mcp-telegram to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "chatroost-telegram": { "url": "https://mcp.mcp-telegram.com/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"chatroost-telegram","type":"http","url":"https://mcp.mcp-telegram.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "chatroost-telegram": { "type": "http", "url": "https://mcp.mcp-telegram.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "chatroost-telegram": { "serverUrl": "https://mcp.mcp-telegram.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add chatroost-telegram --url https://mcp.mcp-telegram.com/mcp codex mcp login chatroost-telegram ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.chatroost-telegram] url = "https://mcp.mcp-telegram.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http chatroost-telegram https://mcp.mcp-telegram.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth chatroost-telegram` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "chatroost-telegram": { "type": "http", "url": "https://mcp.mcp-telegram.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.mcp-telegram.com/mcp`. ## Details - Server version: 1.43.2 - Last checked: 2026-10-04 (reachable, asks for credentials) - Listed: 2026-10-04 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/chatroost-telegram (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report