claude-code-telegrammer 0.6.3
“Custom Telegram MCP server + TUI auto-responder for running Claude Code as an autonomous Telegram agent”
Registry publisher is GitHub ActionsAgent Skills SKILL.md definition file
SHA-256695f15b5f63749e32740ee204d0a767f21277315f2f920c206371b062c2a1604
MaleculeK(Am)
Evidence
94:5… detail: `unexpanded \${...} placeholder(s): ${lines.join("; ")}`,
95 hint:
96 "the launcher started without its backing .env sourced — relaunch via " +
97 "claude.sh so the ${SCITEX_..._*} vars expand, or export the " +
98 "CLAUDE_CODE_TELEGRAMMER_* / CCT_* vars directly before starting.",
⋯6 lines
246:17… while a webhook is registered",
247 hint:
248 "delete it: curl https://api.telegram.org/bot<TOKEN>/deleteWebhook " +
249 "(substitute your bot token for the literal <TOKEN>)",
250 },
⋯5 lines
1---
2name: claude-code-telegrammer
3description: Telegram bridge MCP server for Claude Code — relay messages between an operator on Telegram and a Claude Code agent via MCP tools (reply, get_history, react, send_document, health, and more). Use this when wiring an agent up to Telegram, debugging why Telegram messages aren't reaching an agent (or replies aren't arriving), configuring per-agent bot tokens/state dirs, or working on the ts/telegram-server.ts MCP server itself.
4version: 0.5.0
5---
6
7# claude-code-telegrammer
8
9A TypeScript/Bun MCP server (`ts/telegram-server.ts`) that bridges a Telegram
10bot to a Claude Code agent. It long-polls the Telegram Bot API directly
11(`ge …
12:32… ound Telegram messages arrive as MCP channel
13notifications; the agent replies by calling MCP tools.
14
15Registered MCP server name: `claude-code-telegrammer` (matches
16`CHANNEL_SOURCE` in `ts/lib/config.ts`, so every inbound stimulus is
17attributed to thi …
50:48… AM_<SUFFIX>` (deprecated legacy,
51still honoured with a warning).
52
53| Suffix | Purpose |
54|--------|---------|
55| `BOT_TOKEN` | The Telegram bot token. …
No evidence locations were recorded for this file. Raw result