Most Telegram MCP servers are thin wrappers with 3-5 tools. `aiogram-mcp` goes further:
If you already use Aiogram MCP, the aiogram mcp mcp server is the piece that lets your assistant work with it directly. Most Telegram MCP servers are thin wrappers with 3-5 tools. aiogram-mcp goes further:.
aiogram-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
send_message — Send text with HTML/Markdown formattingsend_photo — Send a photo by URL with optional captionforward_message — Forward a message between chatsdelete_message — Delete a messagepin_message — Pin a message in a chatsend_interactive_message — Send a message with inline keyboard buttons (callback or URL)edit_message — Edit text and/or keyboard of an existing messageanswer_callback_query — Respond to a button press with a toast or alertget_bot_info — Get bot metadata (username, capabilities)get_chat_member_info — Get a user's role and profile in a chatget_user_profile_photos — Get a user's profile photosget_chat_info — Get chat metadata (title, type, description)Configuration is passed through the environment: BOT_TOKEN, YOUR_BOT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Aiogram MCP's toolset — send_message, send_photo, forward_message and 11 more — is a fair guide to whether it matches your workflow. It is maintained by py2755; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| send_message | Send text with HTML/Markdown formatting |
| send_photo | Send a photo by URL with optional caption |
| forward_message | Forward a message between chats |
| delete_message | Delete a message |
| pin_message | Pin a message in a chat |
| send_interactive_message | Send a message with inline keyboard buttons (callback or URL) |
| edit_message | Edit text and/or keyboard of an existing message |
| answer_callback_query | Respond to a button press with a toast or alert |
| get_bot_info | Get bot metadata (username, capabilities) |
| get_chat_member_info | Get a user's role and profile in a chat |
| get_user_profile_photos | Get a user's profile photos |
| get_chat_info | Get chat metadata (title, type, description) |
| get_chat_members_count | Get number of members in a chat |
| ban_user | Ban a user (permanent or temporary) |
{
"mcpServers": {
"aiogram": {
"command": "uvx",
"args": ["aiogram-mcp"],
"env": {
"BOT_TOKEN": "your-value",
"YOUR_BOT_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| BOT_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_BOT_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.