Zenrei
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ZenreiCheck this design proposal against past decisions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Zenrei(前例)
"That proposal? There's a precedent." — Decision memory for AI-driven development.
AI agents don't remember past discussions. They keep re-proposing designs you rejected weeks ago. Zenrei records your decisions — accepted, rejected, deferred — as Markdown in your repos, and serves them to every AI agent (Claude Code / Cursor / CI) over MCP. When an agent re-proposes a rejected design, check_proposal stops it.
git-native — decisions live in your git. Zenrei indexes and serves; it never owns your data
Humans decide — agents can only file drafts (
pending); only a human can accept or rejectDeterministic & light — no LLM calls, no API key, works offline (Japanese-aware bigram BM25). With 1,000 decisions, responses stay ~1,800 chars / 44ms — your prompts never bloat
🌐 How it works: https://zenrei.karakurio.com ・ Operations guide: https://zenrei.karakurio.com/guide
Quick start
claude mcp add zenrei --scope user -- npx -y zenrei --root /path/to/repo1 --root /path/to/repo2For English tool responses, append --lang en (default is Japanese; or set ZENREI_LANG=en).
Add three lines to each repo's CLAUDE.md (agent instructions):
## Decision memory (zenrei)
- At session start, call get_context (scope: this repo) to load decided matters
- Before proposing designs or policies, call check_proposal
- File new decision points with record_decision (humans approve)Decision file format: docs/decision-format.en.md(日本語: docs/decision-format.md)
Related MCP server: @context-anchor/mcp-server
Tools (fixed at five)
tool | role |
| Match a proposal against past decisions — "rejected on 2026-07-08, because …" |
| Search by keyword / status / scope / date range |
| File a decision draft ( |
| List drafts and deferred decisions |
| A digest of relevant decisions for session start |
Repository layout
src/— local MCP server (stdio)packages/core/— parsing / matching / formattingpackages/cli/— thezenreinpm packagedocs/— decision format spec (EN / JA)
The hosted version (GitHub App, cross-repo timeline, approval UI, PR gate) is operated separately: https://zenrei.karakurio.com
Development
npm install
npm run build
npm test日本語
Zenrei(前例)は、AI駆動開発のための意思決定メモリです。採用・却下・保留の決定をリポジトリ内のMarkdown(decisions/*.md)で管理し、MCP経由で全AIエージェントに配ります。エージェントが却下済みの設計を蒸し返したら check_proposal が止めます。
git-native: 決定はあなたのgitの中。データを人質に取りません
決定するのは人間: AIが起票できるのは承認待ち(pending)まで
決定論的照合: LLM不使用・APIキー不要・オフライン動作。決定が増えてもプロンプトは太りません
導入は上のQuick startのとおり。仕組み: https://zenrei.karakurio.com / 使い方: https://zenrei.karakurio.com/guide / 決定フォーマット仕様: docs/decision-format.md
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Give your AI agent persistent, governed memory for every project. At task start it recalls the approved decisions, conventions, risks and architecture (semantic search, ranked by importance); at close it proposes what was learned as typed memories that you review and approve — governance, not a notes dump. Agents propose, humans govern: edits go back to pending and deletion is human-only by design. Connect Claude Code, Cursor, Claude Desktop or any MCP client in two minutes with just your API key — hosted (nothing to install) or locally via `uvx solucortex-mcp`. Built by SoluAI and dogfooded daily: SoluCortex is developed using its own living memory.
Team docs served to AI agents over MCP - search, Markdown reads, version pinning, read audit.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceOpen, Git-native memory protocol for MCP agents: stores memories as Markdown files in a Git repo, enabling portability, auditability, and human-editable memory across different AI agents.6815MIT
- FlicenseNot gradedqualityDmaintenanceGit-native MCP server for managing AI context across sessions. Enables LLMs to access project and feature context via markdown files, preserving decisions and constraints.1-
- AlicenseNot gradedqualityCmaintenanceMCP server for managing an OKF markdown knowledge base, enabling AI agents to query, read, write, and auto-sync architectural decisions and rules via Git.MIT
- AlicenseAqualityAmaintenanceRepository-native protocol and MCP server for coordinating work items, documentation, changelogs, and project memory between humans and AI agents, using Markdown files in a Git repository as the canonical data source.302MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pikonori/zenrei'
If you have feedback or need assistance with the MCP directory API, please join our Discord server