Manual setup required. The maintainer's config contains paths only you know - edit the placeholders below before adding it to Claude Code.
1
Prepare the server locally
Run this once before adding it to Claude Code.
git clone https://github.com/FantomaSkaRus1/telegram-bot-mcp
cd telegram-bot-mcpThen follow the repository README for any remaining dependency or build steps.
2
Register it in Claude Code
claude mcp add -e "TELEGRAM_BOT_TOKEN=${TELEGRAM_BOT_TOKEN}" telegram-bot -- node /path/to/mcp-telegram/index.jsReplace any placeholder paths in the command with the real path on your machine.
Required:
TELEGRAM_BOT_TOKEN+ 2 optional3
Make your agent remember this setup
telegram-bot's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- Supports 174 distinct Telegram Bot API tools
- Comprehensive message management including text, media, and reactions
- Full control over chat settings, permissions, and member management
- Advanced features for stickers, payments, forums, and stories
- Built-in rate limiting and retry logic for API stability
Tools 4
send_messageSends a text message to a specified chat.send_photoSends a photo to a specified chat.delete_messageDeletes a message from a chat.get_chatRetrieves information about a specific chat.Environment Variables
TELEGRAM_BOT_TOKENrequiredBot token from @BotFatherTELEGRAM_DEFAULT_CHAT_IDDefault chat ID to skip chat_id in tool callsTELEGRAM_DEFAULT_THREAD_IDDefault topic/thread ID for forum supergroupsTry it
→Send a message to my Telegram group saying 'Hello from Claude!'
→Get the current information and member count for my Telegram channel.
→Delete the last message sent in the current chat.
→Create a new topic in my Telegram forum group named 'Project Updates'.
Original README from FantomaSkaRus1/telegram-bot-mcp
telegram-bot-mcp
Full-featured Telegram Bot API server for MCP (Model Context Protocol). 174 tools covering the entire Bot API — messages, chats, stickers, payments, forums, stories, and more.
<a href="https://glama.ai/mcp/servers/@FantomaSkaRus1/telegram-bot-mcp"> </a>Features
- Messages — send (text, photo, video, audio, document, location, poll, dice, sticker, media groups), edit, forward, copy, delete, pin/unpin, reactions
- Chats — info, settings, permissions, invite links, member management, verification
- Bot — commands, profile, settings, description, menu button, admin rights
- Stickers — create/edit/delete sticker sets, upload stickers, custom emoji
- Payments — invoices, star transactions, gifts, refunds
- Forums — create/edit/close/reopen/delete topics
- Stories — post, edit, delete, repost
- Business — business messages, accounts, connections
- Games — send games, set scores, high scores
- Webhooks — set, delete, get info
Quick Start
npm install
Claude Code
claude mcp add -e TELEGRAM_BOT_TOKEN=your_token telegram -- node /path/to/mcp-telegram/index.js
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"telegram": {
"type": "stdio",
"command": "node",
"args": ["/path/to/mcp-telegram/index.js"],
"env": {
"TELEGRAM_BOT_TOKEN": "your_token"
}
}
}
}
Environment Variables
| Variable | Required | Description |
|---|---|---|
TELEGRAM_BOT_TOKEN |
Yes | Bot token from @BotFather |
TELEGRAM_DEFAULT_CHAT_ID |
No | Default chat ID (skip chat_id in tool calls) |
TELEGRAM_DEFAULT_THREAD_ID |
No | Default topic/thread ID for forum supergroups |
Project Structure
index.js # Entry point — registers all tool modules
utils/api.js # Telegram API client, rate limiting, retry logic
tools/
messages/ # send, edit, forward, manage
chat/ # info, settings, invite, members, verify
bot/ # core, commands, profile, settings
stickers.js
payments.js
forum.js
stories.js
business.js
games.js
webhook.js
License
MIT