txtscape

Your AI agent forgets everything between conversations. Fix that.

txtscape is an MCP server that gives your agent persistent, searchable memory — plain .txt files committed to git.

Install · Tutorial · npm

Without txtscape vs. with

❌ Without	✅ With txtscape
"Remind me, are we using Postgres or SQLite?"	"Read the architecture decisions and follow the existing patterns."
"What's our error handling pattern again?"	The agent reads your pages and already knows.
Random .md files proliferating across your project	Everything in one .txtscape/ folder — your tree stays clean
Every conversation starts from zero.	Knowledge accumulates in your repo.

Why txtscape

• 📁 Plain text in git — Diffable, reviewable in PRs, and portable across any tool. Your agent's memory gets the same code review process as your code.
• 🔒 Zero dependencies — Pure Go standard library. One binary, nothing to audit, no supply chain to worry about.
• 🧠 LLM-native — Plain text with markdown formatting that any model already understands. No custom schema, no parsing layer.
• 🚫 No database — The filesystem is the storage layer. No install, no migrations, no process to keep running.
• 🏗️ Configurable structure — Define your own taxonomy — decisions/, runbooks/, architecture/ — with optional templates so every page follows the same shape.
• 🔓 No lock-in — Stop using txtscape and your .txt files stay right where they are. They're just files in your repo.
• ✨ No file sprawl — Everything lives in one .txtscape/ folder. No random markdown files cluttering your project tree or polluting search results.
• ⚡ No ports, no daemons — Your IDE launches it as a stdio subprocess, talks over stdin/stdout, and it exits when done. No attack surface.
• 📜 MIT licensed — Free and open source forever. Use it however you want, commercially or otherwise.

Works with

VS Code (Copilot) · Cursor · Windsurf · Claude Desktop · Claude Code · Zed · JetBrains (via MCP plugin) · Neovim (via MCP plugins) — any MCP-compatible client.

What it looks like

You: "Record that we chose Postgres over SQLite. Reason: we need concurrent writes and the team already knows it."

Agent: put_page → decisions/database-choice.txt created

— next day, new conversation —

You: "Add a users table migration."

Agent: search_pages → found decisions/database-choice.txt "I see you chose Postgres for concurrent writes. I'll write the migration using PostgreSQL syntax with a serial primary key…"

Get started

👉 Install in 2 minutes — pick your editor, paste one config block, done.

👉 Try the tutorial — build a text adventure game in 30 minutes while learning how persistent memory works.

License

MIT — see LICENSE.txt.