{"product_id":"telegram-bot-management-mcp-tools-bot-api-mtproto-bridge","title":"Telegram Bot Management MCP Tools (Bot API + MTProto Bridge)","description":"\u003ch3\u003eManage your Telegram bot from any MCP-capable AI client—directly via Bot API or an optional MTProto BotFather bridge\u003c\/h3\u003e\n\u003cp\u003eThis n8n workflow turns Telegram bot administration into an \u003cstrong\u003eMCP server endpoint\u003c\/strong\u003e. Your AI agent (Claude, Cursor, or an n8n AI Agent) can call Telegram \u003cstrong\u003eBot API\u003c\/strong\u003e methods like \u003cem\u003egetMe\u003c\/em\u003e and \u003cem\u003esetMyCommands\u003c\/em\u003e, and—when needed—route restricted actions through a self-hosted \u003cstrong\u003eMTProto BotFather bridge\u003c\/strong\u003e.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eExposes 9 MCP tools\u003c\/strong\u003e to any MCP-compatible AI client via an \u003cstrong\u003eMCP Server Trigger\u003c\/strong\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003e8 tools call Telegram’s official Bot API directly\u003c\/strong\u003e using a bot token you provide per request:\n    \u003cul\u003e\n      \u003cli\u003eget_me\u003c\/li\u003e\n      \u003cli\u003eset_my_name\u003c\/li\u003e\n      \u003cli\u003eset_my_description\u003c\/li\u003e\n      \u003cli\u003eset_my_short_description\u003c\/li\u003e\n      \u003cli\u003eset_my_commands\u003c\/li\u003e\n      \u003cli\u003edelete_my_commands\u003c\/li\u003e\n      \u003cli\u003eset_chat_menu_button\u003c\/li\u003e\n      \u003cli\u003eset_default_admin_rights\u003c\/li\u003e\n    \u003c\/ul\u003e\n  \u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003e1 tool (mtproto_botfather_bridge)\u003c\/strong\u003e forwards BotFather-only actions to a small self-hosted Python service that logs into your personal Telegram account and chats with \u003cstrong\u003e@BotFather\u003c\/strong\u003e.\u003c\/li\u003e\n  \u003cli\u003eYour AI decides \u003cstrong\u003ewhich tool to call\u003c\/strong\u003e and \u003cstrong\u003ewith what arguments\u003c\/strong\u003e—nothing runs until it’s asked.\u003c\/li\u003e\n  \u003cli\u003eReturns \u003cstrong\u003estructured JSON\u003c\/strong\u003e responses your agent can read and act on.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eHave an AI agent verify bot identity (\u003cem\u003egetMe\u003c\/em\u003e) before changing settings.\u003c\/li\u003e\n  \u003cli\u003eAutomate command setup (\u003cem\u003esetMyCommands\u003c\/em\u003e) across multiple environments.\u003c\/li\u003e\n  \u003cli\u003eUpdate bot profile fields (name, description, short description) from natural-language requests.\u003c\/li\u003e\n  \u003cli\u003eUse the MTProto bridge for actions the Bot API can’t do (e.g., \u003cstrong\u003e\/newbot\u003c\/strong\u003e, toggling privacy mode, or revoking a token).\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eDesigned for \u003cstrong\u003en8n automation workflow\u003c\/strong\u003e with nodes including: \u003cem\u003en8nn8n-nodes-langchainmcp trigger\u003c\/em\u003e, HTTP Request Tool, and a Sticky Note for guidance.\u003c\/li\u003e\n  \u003cli\u003eSecured with \u003cstrong\u003eBearer Auth\u003c\/strong\u003e on the MCP Server Trigger—every MCP client must send the same Authorization token.\u003c\/li\u003e\n  \u003cli\u003eBot API tools require the bot token supplied per call by your AI agent.\u003c\/li\u003e\n\u003c\/ul\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":45876838465715,"sku":"N8N-18527","price":3.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/u5f81EWNLSn2PxODKOp21_7peDKegQ.png?v=1787303102","url":"https:\/\/buyflowscripts.com\/products\/telegram-bot-management-mcp-tools-bot-api-mtproto-bridge","provider":"N8N Commerce","version":"1.0","type":"link"}