MCP server for aiogram Telegram bots — 30 tools, 7 resources, 3 prompts, event streaming
Connect your Telegram bot to AI agents via the Model Context Protocol. turns any aiogram bot into an MCP server. AI clients like Claude Desktop can then send messages, read chat history, build interactive menus, and react to events in real time — all through your existing bot, without rewriting a single handler. Most Telegram MCP servers are thin wrappers with 3-5 tools. goes further: 30 tools —…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Connect your Telegram bot to AI agents via the Model Context Protocol. turns any aiogram bot into an MCP server. AI clients like Claude Desktop can then send messages, read chat history, build interactive menus, and react to events in real time — all through your existing bot, without rewriting a single handler. Most Telegram MCP servers are thin wrappers with 3-5 tools. goes further: 30 tools — messaging, rich media, moderation, interactive keyboards, event subscriptions, broadcasting 7…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.