aiogram-mcp

io.github.Py2755由 GitHub 账号 Py2755 发布v0.7.1更新于 Oct 25, 2026

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

已验证STDIO仅桌面开发者工具沟通与协作

概览

AI 生成的概览

把现有的 aiogram Telegram 机器人变成 MCP 服务器,让 AI 助手能发消息、管理群聊并响应事件。

可以做什么
发送、转发、删除和置顶消息,以及照片、文档、语音、视频、贴纸、投票、联系人和位置,并可创建带按钮的内联键盘、编辑消息和回应按钮回调。查询机器人、群聊和成员信息、成员数量及用户头像。管理群聊:封禁或解封用户,修改群标题和描述。订阅以 MCP 通知推送的实时 Telegram 事件,并可选向多个群聊广播。读取机器人信息、配置、群聊列表、消息历史、事件队列、文件元数据和审计日志等资源,并使用审核、公告和用户报告提示词。
适用场景
适合已经运行 aiogram 机器人、希望让 Claude Desktop 等 AI 客户端操作同一个机器人的场景:收发消息、执行审核、发布公告,或搭建交互式按钮流程,而无需重写处理函数。
运行要求
作为本地 stdio 进程与机器人一起启动(需要 Python 3.10+ 和 aiogram 3.20+,可通过 pip 或 uvx 安装)。需要 Telegram Bot API 令牌,通过 BOT_TOKEN 环境变量提供,并在机器人代码中加入中间件和 MCP 服务器。需要访问 Telegram 的网络连接。
安装前请注意
BOT_TOKEN 拥有机器人的完全控制权,不要放入共享配置。工具可以发送、编辑、删除、置顶消息、封禁用户和修改群设置,广播可向多个群聊发消息;应通过 allowed_chat_ids、permission_level 和需显式开启的广播限制来约束访问。审计日志默认关闭。消息内容和群聊数据会经过 AI 客户端。

安装

在 SourceWeft 中

  1. 打开 控制台中的 aiogram-mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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.

来源:README.md,提交 a5ae934

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.7.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分