aemet/telegram-bot-mcp repository overview

⁠Telegram MCP via Docker

⁠Docker Image

• Image: aemet/telegram-bot-mcp
• Recommended tag: 1.0.0
• Registry: Docker Hub

docker pull aemet/telegram-bot-mcp:1.0.0

⁠Prerequisites

• Docker installed and running
• Telegram bot token from @BotFather

⁠Required Parameters

Only one required runtime variable:

• TELEGRAM_BOT_TOKEN - Telegram bot token

Optional parameter in MCP config:

• chat_Id - default chat id for quick notifications (client-side convenience field)

Important:

• chat_Id is a custom convention (not a standard MCP field).
• Recommended: add a Cursor rule or skill that tells the agent to read chat_Id from MCP config when sending Telegram notifications.

⁠Quick Local Check

Use this to verify the image starts correctly:

docker run -i --rm \
  -e TELEGRAM_BOT_TOKEN="YOUR_TOKEN" \
  aemet/telegram-bot-mcp:1.0.0

If the token is valid, MCP process starts and waits for tool calls over stdio.

⁠MCP Configuration

Example:

{
  "mcpServers": {
    "telegram": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--name",
        "telegram-mcp",
        "-e",
        "TELEGRAM_BOT_TOKEN",
        "aemet/telegram-bot-mcp:1.0.0"
      ],
      "env": {
        "TELEGRAM_BOT_TOKEN": "YOUR_TOKEN"
      },
      "chat_Id": "YOUR_CHAT_ID"
    }
  }
}

Notes:

• --name telegram-mcp prevents random container names.
• --rm removes container after process exit.

⁠How To Get chat_id

1. Send any message to your bot in Telegram.
2. Call MCP tool tg_get_me (sanity check bot access).
3. Call tg_send_message once with your known chat id, or inspect updates using your preferred Telegram method.