Nucleus
Give long-running coding agents a .brain directory for persistent memory, verified execution traces, and lightweight governance rules.
Overview
io.github.eidetic-works/nucleus is a MCP server for the Build phase that provides persistent .brain memory, execution verification, and governance tooling for coding agents.
What is this MCP server?
- Persistent memory backed by configurable NUCLEUS_BRAIN_PATH (.brain/ default)
- Execution verification hooks for agent-run commands and outcomes
- Governance and compliance-oriented tooling in nucleus-mcp npm package
- stdio transport via npx nucleus-mcp (registry versions 1.8.0 / 1.8.1)
Community signal: 2 GitHub stars.
What problem does it solve?
Your agent forgets prior decisions and you cannot trust whether it actually ran commands or followed your rules across sessions.
Who is it for?
Indie builders running multi-session agent workflows who need memory and accountability without a full enterprise GRC suite.
Skip if: One-off script generation with no continuity, or teams that only need a single REST API MCP with no local brain store.
What do I get? / Deliverables
After install, agents can read and write durable brain state with verification and governance guardrails aligned to your repo.
- On-disk .brain persistent memory for agent sessions
- Execution verification aligned with agent tool runs
- Governance and compliance helpers exposed as MCP tools
Recommended MCP Servers
Journey fit
Agent-tooling is the primary shelf because Nucleus is installed to extend how agents remember and verify work during product build. Persistent brain storage and execution verification matter most while you iterate features with Claude Code or similar agents daily.
How it compares
Agent memory and execution governance MCP, not a cloud observability platform or generic database server.
Common Questions / FAQ
Who is io.github.eidetic-works/nucleus for?
Solo developers and small teams using long-horizon coding agents who want persistent .brain memory plus execution verification and governance helpers.
When should I use io.github.eidetic-works/nucleus?
Use it during build and agent-tooling when sessions span days, and again in operate when you need traceable agent actions and compliance notes.
How do I add io.github.eidetic-works/nucleus to my agent?
Configure stdio MCP with npx nucleus-mcp, set NUCLEUS_BRAIN_PATH if needed, and commit or back up your .brain directory per your policy.