zaxy — Claude Code MCP server: what it does, how to install
Auditable agent memory powered by Eventloom event sourcing and LadybugDB. Keeps session provenance intact with cited facts and replayable execution logs.
claude mcp add zaxy -- uvx zaxy-memoryWhat zaxy does
Zaxy organizes agent activity into a verifiable project memory log. It records task missions, worker findings, and approval records directly into append-only JSONL files located in the .eventloom directory.
Local reasoning runs through an embedded LadybugDB graph projection without external services. Retrieval combines vector embeddings and graph traversal. The server exposes dedicated MCP tools such as memory_append, memory_query, memory_feedback, memory_replay, and memory_invalidate.
The standard setup operates entirely locally. External backends like Neo4j or Pathlight tracing remain strictly optional and require installing explicit package extras like zaxy-memory[neo4j] or zaxy-memory[pathlight].
What it helps with
- track agent findings in an auditable append-only log
- isolate worker sessions before merging facts into main context
- query past decisions via hybrid vector search and graph traversal
- replay provenance steps behind model conclusions
Example prompts for the agent
- Query Zaxy memory for recent architecture decisions using
memory_query. - Append verified validation rules to project history with
memory_append. - Replay past tool observations for the specified task session.
How to install zaxy
Platform CLI
claude mcp add zaxy -- uvx zaxy-memoryuvx runs the command named after the package; if the README names another one, use uvx --from zaxy-memory <command>
Platform CLI
codex mcp add zaxy -- uvx zaxy-memoryuvx runs the command named after the package; if the README names another one, use uvx --from zaxy-memory <command>
Config file
{
"mcpServers": {
"zaxy": {
"command": "uvx",
"args": [
"zaxy-memory"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from zaxy-memory <command>
Config file
{
"servers": {
"zaxy": {
"type": "stdio",
"command": "uvx",
"args": [
"zaxy-memory"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from zaxy-memory <command>
Platform CLI
gemini mcp add zaxy uvx zaxy-memoryuvx runs the command named after the package; if the README names another one, use uvx --from zaxy-memory <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about zaxy
How to install zaxy in Claude Code?
Run claude mcp add zaxy -- uvx zaxy-memory in your terminal. This registers the server using uvx without requiring manual repository cloning.
What does zaxy do?
It builds an event-sourced memory fabric for autonomous agents. Facts are preserved in append-only JSONL records and projected onto a local LadybugDB graph.
Does zaxy require a running Neo4j instance?
No, the default configuration uses an embedded LadybugDB graph runtime. Neo4j is purely optional and needs the zaxy-memory[neo4j] package extra.
