Claude Telegram Bot

A headless **Claude Code** instance running on the [[gcp-mcp-standalone/README|MCP broker VM]], reachable over **Telegram**: you DM a bot, the message is injected into the Claude session, Claude acts (within a locked-down allow-list) and replies in the chat. It runs as the isolated

type readmestatus activemcp · telegram · claude-code · bot

claudebot user via the official telegram channel plugin (telegram@claude-plugins-official), authenticated with a Claude subscription token — so idle time costs nothing; only your messages consume usage.

This is not the same thing as the planned send-only Telegram broker connector (that remains a separate future design — see Status). This is a two-way chat/ops bot: Claude reachable from your phone.

It can also read your Notion — through the on-VM broker (localhost, read-only tools only), so you can ask it questions about your Notion docs from Telegram without it ever being able to modify them.

Status

Live (rebuilt 2026-07-02, reproducible via Ansible). Verified end-to-end: an allowlisted DM ("how much disk space?") returns a real answer. Access is pairing-then-allowlist; only paired Telegram user IDs are served.

History: originally hand-built on the VM; the 2026-07-02 Tailscale key-rotation VM rebuild destroyed it (it lived only on disk, not in IaC). Now captured in ansible/claudebot.yml so a rebuild can't silently kill it again.

Note: the separate broker-native send-only connector (Phase 3 of the 2026-06-29 connectors design — wrap the Bot API in-process in the broker for agent notifications) is still just proposed and unbuilt. Different mechanism, different purpose.

Docs

telegram-mcp-connector/HLD — architecture, message flow, security, cost
Host environment: gcp-mcp-standalone/README
Runbook: gcp-mcp-standalone/runbooks/deploy (broker) — bot deploy is ansible/claudebot.yml

Compiled from wiki/projects/telegram-mcp-connector/README.md · git is the source of truth