Full Telegram Access
for AI Agents

# Clone and install
$ git clone https://github.com/sandikodev/telegram-mcp.git && cd telegram-mcp
$ bun install

# One-time authentication (saves session to ~/.config/telegram-mcp/session.txt)
$ bun run auth
API ID: ••••••••  |  API Hash: ••••••••••••••••
Phone: +62••••••••••  |  OTP: ••••••
✅ Session saved.

# mcp.json — full access: history, dialogs, topics, search
{
  "mcpServers": { "telegram": {
    "command": "bun", "args": ["run", "/path/to/telegram-mcp/src/index.ts"],
    "env": { "TELEGRAM_API_ID": "...", "TELEGRAM_API_HASH": "..." }
  }}
}

# No auth script needed — just a bot token from @BotFather
$ git clone https://github.com/sandikodev/telegram-mcp.git && cd telegram-mcp
$ bun install

# mcp.json — zero setup, works immediately
{
  "mcpServers": { "telegram": {
    "command": "bun", "args": ["run", "/path/to/telegram-mcp/src/index.ts"],
    "env": { "TELEGRAM_BOT_TOKEN": "your_bot_token" }
  }}
}

# Or via npx — zero install
{
  "mcpServers": { "telegram": {
    "command": "npx", "args": ["-y", "telegram-mcp"],
    "env": { "TELEGRAM_BOT_TOKEN": "your_bot_token" }
  }}
}

# Deploy to Cloudflare Workers — runs on the edge, zero cold start
$ git clone https://github.com/sandikodev/telegram-mcp.git && cd telegram-mcp
$ bun install
$ wrangler secret put TELEGRAM_BOT_TOKEN
Enter a secret value: ••••••••••••••••••••••••••••••••••••••••••••••
✅ Success! Uploaded secret TELEGRAM_BOT_TOKEN
$ wrangler deploy
✅ Deployed to https://telegram-mcp.your-subdomain.workers.dev

# mcp.json — HTTP transport, no local process needed
{
  "mcpServers": { "telegram": {
    "url": "https://telegram-mcp.your-subdomain.workers.dev/mcp"
  }}
}