Telegram Bot Management MCP Tools (Bot API + MTProto Bridge)

Manage your Telegram bot from any MCP-capable AI client—directly via Bot API or an optional MTProto BotFather bridge

This n8n workflow turns Telegram bot administration into an MCP server endpoint. Your AI agent (Claude, Cursor, or an n8n AI Agent) can call Telegram Bot API methods like getMe and setMyCommands, and—when needed—route restricted actions through a self-hosted MTProto BotFather bridge.

What this workflow does

• Exposes 9 MCP tools to any MCP-compatible AI client via an MCP Server Trigger.
• 8 tools call Telegram’s official Bot API directly using a bot token you provide per request:
  • get_me
  • set_my_name
  • set_my_description
  • set_my_short_description
  • set_my_commands
  • delete_my_commands
  • set_chat_menu_button
  • set_default_admin_rights
• 1 tool (mtproto_botfather_bridge) forwards BotFather-only actions to a small self-hosted Python service that logs into your personal Telegram account and chats with @BotFather.
• Your AI decides which tool to call and with what arguments—nothing runs until it’s asked.
• Returns structured JSON responses your agent can read and act on.

Use cases

• Have an AI agent verify bot identity (getMe) before changing settings.
• Automate command setup (setMyCommands) across multiple environments.
• Update bot profile fields (name, description, short description) from natural-language requests.
• Use the MTProto bridge for actions the Bot API can’t do (e.g., /newbot, toggling privacy mode, or revoking a token).

Technical details

• Designed for n8n automation workflow with nodes including: n8nn8n-nodes-langchainmcp trigger, HTTP Request Tool, and a Sticky Note for guidance.
• Secured with Bearer Auth on the MCP Server Trigger—every MCP client must send the same Authorization token.
• Bot API tools require the bot token supplied per call by your AI agent.