memtree
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., "@memtreesearch memory for 'database schema'"
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.
memtree
Codex and Claude Code session JSONL is collected outside the model context, consolidated into local SQLite memory, and exposed through MCP.
This is an intentionally small first implementation:
Codex and Claude Code Hook queueing
crash-recovery transcript scanning
byte-offset incremental JSONL collection
secret redaction and user/final-assistant filtering
deterministic per-session Sleep memory
SQLite FTS search
MCP read, search, explicit write, forget, Sleep, and status tools
stdio and Streamable HTTP transports
The current Sleep implementation creates a bounded session digest. It does not yet perform LLM-based profile/entity/decision extraction.
Setup
cd ~/repos/memtree
uv sync
uv run memtree init
uv tool install --editable .The editable tool install makes memtree available to lifecycle hooks.
Related MCP server: waypath
Configure hooks
Merge the relevant example into the user-level configuration:
Codex:
integrations/codex/hooks.json.exampleinto~/.codex/hooks.jsonClaude Code:
integrations/claude-code/settings.json.exampleinto~/.claude/settings.json
Review and trust the Codex hook through /hooks. Hooks only enqueue
session_id, transcript_path, and cwd; they do not invoke MCP or a model.
Collect and Sleep
Run manually or from cron/systemd:
memtree collect --scan all
memtree sleep
memtree status
memtree memory list --cwd "$PWD"Suggested daily command:
memtree collect --scan all && memtree sleepConfigure MCP
Codex stdio configuration:
[mcp_servers.memtree]
command = "memtree"
args = ["serve", "--transport", "stdio"]
enabled = trueClaude Code:
claude mcp add --scope user memtree -- \
memtree serve --transport stdioAvailable tools:
memory_contextmemory_searchmemory_getmemory_putmemory_forgetmemory_sleepmemory_status
Write and forget tools are annotated with their side effects. Automatic transcript ingestion is deliberately not exposed as an MCP tool.
Pass cwd to memory_context or memory_search to include the matching
project memory. Use include_all_projects=true only for an intentional
cross-project review.
Docker
Docker runs the Streamable HTTP MCP server with a private persistent volume:
docker compose up --build -dThe HTTP endpoint is http://127.0.0.1:8765/mcp. Collection normally runs on
the host because the transcript directories are private host state.
Development
uv run ruff format --check .
uv run ruff check .
uv run pyright
uv run pytestThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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/aiagate/memtree'
If you have feedback or need assistance with the MCP directory API, please join our Discord server