Server facts
mcp-telegram
Project
- Author
- tacticlaunch
- Repository
- github.com/tacticlaunch/mcp-telegram
- Website
- npmjs.com/mcp-telegram
- License
- MIT
- Category
- Communication
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 31
- Last commit
- Data as of
Tags
- mcp server
- mcp telegram
- telegram bot
Overview
Conversation lookup in mcp-telegram ranges from finding a chat by name to filtering its messages by sender, content type, or date. An assistant can then reply, schedule a message, forward content, send an album, or download media. Saved Messages has separate tools for reaction-tag searches and browsing groups of forwards by their source. Voice or video note transcription requires Telegram Premium.
Channel administration covers member restrictions, admin permissions, invite links, slow mode, and forum topics; account management also includes stories, contacts, folders, drafts, and privacy settings. For operations outside the dedicated tools, invoke_mtproto accepts a raw Telegram API method name, with no per-method safety checks. The server runs on Node.js 20 or later, requires Telegram API credentials, and uses browser-based sign-in. It acts as the authenticated user, not a bot, and keeps sessions locally. Local settings offer read-only mode and tool allowlists or blocklists, with environment variables taking precedence; settings changes require an MCP client restart.
mcp-telegram setup notes
- mcp-telegram records stdio only; confirm a network transport upstream before planning remote access.