aiogram-mcp

io.github.Py2755Published by GitHub account Py2755v0.7.1Updated Oct 25, 2026

MCP server for aiogram Telegram bots — 30 tools, 7 resources, 3 prompts, event streaming

Overview

AI-generated overview

Turns an existing aiogram Telegram bot into an MCP server so an AI assistant can send messages, manage chats and react to events.

What you can do
Send, forward, delete and pin messages, photos, documents, voice, video, stickers, polls, contacts and locations, and build inline keyboard menus with edits and callback answers. Look up bot, chat and member information, member counts and user profile photos. Moderate chats by banning or unbanning users and changing chat title and description. Subscribe to real-time Telegram events pushed as MCP notifications, and optionally broadcast to many chats. Read resources for bot info, config, chat lists, message history, event queue, file metadata and an audit log, plus moderation, announcement and user report prompts.
When to use it
Use it when you already run an aiogram bot and want an AI client such as Claude Desktop to operate that same bot: answering and sending messages, running moderation, posting announcements, or building interactive button flows without rewriting handlers.
Requirements
Runs locally as a stdio process started alongside your bot (Python 3.10+ and aiogram 3.20+, installable via pip or uvx). Needs a Telegram Bot API token supplied in the BOT_TOKEN environment variable, and the bot code must add the middleware and MCP server. Network access to Telegram is required.
Before you install
The BOT_TOKEN grants full control of the bot, so keep it out of shared configs. Tools can send, edit, delete, pin, ban and change chat settings, and broadcast can message many chats; restrict access with allowed_chat_ids, permission_level and the opt-in broadcast limits. Audit logging is off by default. Message content and chat data pass through the AI client.

Installation

In SourceWeft

  1. Open aiogram-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

aiogram-mcp

[CI] [Python 3.10+] [License: MIT] [PyPI version] [MCP Registry]

Connect your Telegram bot to AI agents via the Model Context Protocol.

aiogram-mcp 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.

Why aiogram-mcp?

Most Telegram MCP servers are thin wrappers with 3-5 tools. aiogram-mcp goes further:

  • 30 tools — messaging, rich media, moderation, interactive keyboards, event subscriptions, broadcasting
  • 7 resources — bot info, config, chat lists, message history, event queue, file metadata, audit log
  • 3 prompts — ready-made moderation, announcement, and user report workflows
  • Structured output — every tool returns typed Pydantic models with outputSchema for programmatic parsing
  • Real-time events — the bot pushes Telegram events to AI clients via MCP notifications (no polling)
  • Interactive messages — AI agents create inline keyboard menus, handle button presses, edit messages
  • Rate limiting — built-in token bucket prevents Telegram 429 errors
  • Permission levels — restrict AI agents to read-only, messaging, moderation, or full admin access
  • Audit logging — track every tool invocation with timestamps and arguments
  • Zero rewrite — add 5 lines to your existing bot, keep all your handlers

How It Works

Telegram users                Your aiogram bot              AI agent (Claude Desktop)      |                             |                              |      |  send messages, tap buttons |                              |      | --------------------------> |                              |      |                             |  MCP server (stdio or SSE)   |      |                             | <------------------------->  |      |                             |  tools / resources / events  |      |                             |                              |      |  bot replies, shows menus   |   send_message, edit, ban    |      | <-------------------------- | <--------------------------- |

The bot runs normally for Telegram users. The MCP server runs alongside it, giving AI agents access to the same bot via tools and resources.

Installation

bash
pip install aiogram-mcp

Requires Python 3.10+ and aiogram 3.20+.

Quickstart

1. Add aiogram-mcp to your bot

python
import asynciofrom aiogram import Bot, Dispatcherfrom aiogram_mcp import AiogramMCP, EventManager, MCPMiddleware
bot = Bot(token="YOUR_BOT_TOKEN")dp = Dispatcher()
# Middleware tracks chats, users, message history, and eventsevent_manager = EventManager()middleware = MCPMiddleware(event_manager=event_manager)dp.message.middleware(middleware)dp.callback_query.middleware(middleware)  # for interactive buttons
# Register your normal handlers here# @dp.message(...)# async def my_handler(message): ...
# Create the MCP servermcp = AiogramMCP(    bot=bot,    dp=dp,    name="my-bot",    middleware=middleware,    event_manager=event_manager,    allowed_chat_ids=[123456789],  # optional: restrict which chats AI can access)
async def main():    await mcp.run_alongside_bot(transport="stdio")
asyncio.run(main())

2. Connect Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "my-telegram-bot": {      "command": "python",      "args": ["path/to/your/bot.py"],      "env": {        "BOT_TOKEN": "123456:ABC-DEF..."      }    }  }}

Now Claude can send messages, read history, create button menus, and react to events in your Telegram bot.

Built-in Tools

Messaging (5 tools)

ToolDescription
send_messageSend text with HTML/Markdown formatting
send_photoSend a photo by URL with optional caption
forward_messageForward a message between chats
delete_messageDelete a message
pin_messagePin a message in a chat

Interactive Messages (3 tools)

ToolDescription
send_interactive_messageSend a message with inline keyboard buttons (callback or URL)
edit_messageEdit text and/or keyboard of an existing message
answer_callback_queryRespond to a button press with a toast or alert

Users (3 tools)

ToolDescription
get_bot_infoGet bot metadata (username, capabilities)
get_chat_member_infoGet a user's role and profile in a chat
get_user_profile_photosGet a user's profile photos

Chats (6 tools)

ToolDescription
get_chat_infoGet chat metadata (title, type, description)
get_chat_members_countGet number of members in a chat
ban_userBan a user (permanent or temporary)
unban_userUnban a user
set_chat_titleChange the chat title
set_chat_descriptionChange the chat description

Rich Media (10 tools)

ToolDescription
send_documentSend a file/document by URL with optional caption
send_voiceSend a voice message by URL
send_videoSend a video by URL with optional caption
send_animationSend a GIF/animation by URL
send_audioSend audio/music by URL with performer and title
send_stickerSend a sticker by file_id or URL
send_video_noteSend a round video note by URL
send_contactSend a contact with phone number and name
send_locationSend a geolocation pin
send_pollCreate a poll with multiple options

Events (2 tools)

ToolDescription
subscribe_eventsSubscribe to real-time events with chat/type filters
unsubscribe_eventsRemove a subscription

Broadcast (1 tool, opt-in)

ToolDescription
broadcastSend a message to multiple chats (requires enable_broadcast=True)

MCP Resources

Read-only data that AI agents can access without calling tools:

URIDescription
telegram://bot/infoBot username, ID, and capabilities
telegram://configServer name and allowed chat IDs
telegram://chatsList of active chats with metadata
telegram://chats/{chat_id}/historyLast 50 messages in a chat
telegram://events/queueEvent queue with auto-incrementing IDs
telegram://files/{file_id}File metadata (size, path, unique ID)
telegram://audit/logAudit log of tool invocations (opt-in)

MCP Prompts

Pre-built workflows that give AI agents structured context:

PromptArgumentsWhat it does
moderation_promptchat_id, user_id, reasonFetches user info + message history, suggests warn/mute/ban
announcement_prompttopic, audience?, tone?Drafts a formatted Telegram announcement
user_report_promptchat_id, user_idCompiles a full user activity report

Real-time Event Streaming

AI agents don't need to poll. The bot pushes events automatically:

Telegram message arrives    → MCPMiddleware captures it        → EventManager stores it (type: "message", "command", or "callback_query")            → MCP notification sent to subscribed clients                → AI agent reads telegram://events/queue

The AI agent calls subscribe_events once, then receives push notifications whenever new events match its filters.

Interactive Messages

AI agents can build full interactive UIs in Telegram — menus, confirmations, multi-step wizards:

The AI agent sends a message with buttons:

┌─────────────────────────┐│ Confirm deployment?     ││                         ││  [✅ Yes]  [❌ No]      ││  [📖 View docs]        │└─────────────────────────┘

User taps a button → event appears in the queue → AI agent reacts:

┌─────────────────────────┐│ ✅ Deployed!            ││                         ││  [📋 View logs]        │└─────────────────────────┘

The bot needs dp.callback_query.middleware(middleware) to capture button presses.

Safety Controls

python
mcp = AiogramMCP(    bot=bot,    dp=dp,    allowed_chat_ids=[123456789, -1001234567890],  # restrict AI access    enable_broadcast=True,            # opt-in for broadcast tool    max_broadcast_recipients=500,     # safety limit)
  • allowed_chat_ids — AI can only interact with listed chats. Default: all chats.
  • enable_broadcast — broadcast tool is disabled by default as a safety measure.
  • max_broadcast_recipients — caps the number of chats in a single broadcast.

Advanced Configuration

Rate Limiting

python
mcp = AiogramMCP(    bot=bot, dp=dp,    rate_limit=30,  # requests/sec (default), 0 to disable)

Built-in token bucket rate limiter prevents Telegram 429 errors. All outgoing API calls are automatically paced.

Permission Levels

python
mcp = AiogramMCP(    bot=bot, dp=dp,    permission_level="messaging",  # read + messaging tools only)
LevelAccess
readBot info, chat info, user profiles
messagingRead + send messages, photos, media, interactive messages
moderationMessaging + delete, pin, ban, unban, chat settings
adminFull access including broadcast and event subscriptions

Audit Log

python
mcp = AiogramMCP(    bot=bot, dp=dp,    enable_audit=True,    audit_log_size=1000,)

Every tool invocation is logged. Access via telegram://audit/log resource.

Examples

ExampleTransportFeatures
basic_bot.pystdioFull setup with middleware, events, and callback tracking
incident_alert_bot.pySSEBroadcast-enabled ops bot for incident notifications

Development

bash
git clone https://github.com/Py2755/aiogram-mcp.gitcd aiogram-mcppip install -e ".[dev]"
pytest -v          # ~228 testsruff check aiogram_mcp tests examplesmypy aiogram_mcp   # strict mode

License

MIT. See LICENSE.

Source: README.md at commit a5ae934

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.7.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts