A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
2 ★ · fenghaochang/LoreRoom · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository fenghaochang/LoreRoom;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Your Claude Code Telegram bot — but it remembers. 📖 Read the story — why inbound Telegram messages skip every hook > 中文版 → README.zh-TW.md **A private, encrypted room that remembers every conversation with your Claude Code Telegram bot — both sides — so it never forgets.** You chat with Claude Code from your phone through the official Telegram plugin. But every Claude Code session is amnesiac: restart it and the whole conversation is gone. LoreRoom captures both sides of that Telegram conversation into a single, whole-file-encrypted SQLite database and hands it back to Claude as searchable memory. So you can ask your bot: > **You:** what did I ask you to do last night? > **Bot:** *(searches LoreRoom)* You asked me to fix the crawler retry logic and send you the diff… Local-first. No cloud, no extra API keys, it never touches your bot token. --- Why LoreRoom exists (and why it's reliable) The Claude Code Telegram plugin delivers your incoming messages to Claude through an internal channel push — **not** through any hook. Worse, when Claude is busy those messages **queue invisibly**, and if the bot never replies they're simply gone. So the obvious approaches (hooks, reading the transcript) silently lose your messages. LoreRoom captures at the **plugin's source**, the instant a message arrives from Telegram: - **Inbound** — the moment Telegram delivers it, *before* any queue, *regardless of whether Claude is busy, crashed, or never replies*. - **Outbound** — whenever the bot sends a reply. Both are written to a small spool file that an ingester drains into the encrypted database. **Nothing is lost — even when your bot is unresponsive.** (Messages that were stuck while the bot was busy get captured the moment it restarts and re-fetches them.) No Claude Code hooks are used, so LoreRoom never interferes with your other Claude Code work. Before you start — what you need LoreRoom adds memory to an **existing** Claude Code Telegram bot. So you first need that bot working. **If you can already chat with your bot from Telegram, skip to Install.** Otherwise, set this up once (~5 minutes): **1. Node.js 20 or newer.** Check with node -v. If missing, get it from nodejs.org. **2. Claude Code** — Anthropic's command-line tool. See the install guide. **3. A Telegram bot connected to Claude Code:** 1. In Telegram, open a chat with **@BotFather**, send /newbot, follow the prompts, and copy the **bot token** it gives you (a long string). 2. In Claude Code, install the official **Telegram plugin**, then configure it with your token: /telegram:configure . 3. Link your account: send your bot any message in Telegram — it replies with a pairing code — then run /telegram:access pair in Claude Code. 4. Start a bot session: claude --channels plugin:telegram@claude-plugins-official, then send your bot "hi" in Telegram. It should reply. Once "hi" gets a reply, your bot works. Now give it memory with LoreRoom 👇 > **Scope:** LoreRoom only works with Claude Code + the official Telegram plugin (it is not a general Telegram bot framework). It captures by **patching the plugin** — one idempotent command you re-run after plugin updates. See Why patch the plugin. Install Then **restart your bot session** (claude --channels …) so it loads the patched plugin. Done — every Telegram message is now captured automatically. > **Node version note:** the encrypted-SQLite native module is ABI-bound to one Node version, and init pins the exact node that ran it. If you later upgrade or remove that Node, re-run npm install && npm run build and re-register.