Use MOOTx01 from a script, an AI harness, a connected service, or your own application. Choose an integration that fits your workflow, connect your notes, and carry useful context forward.
Explore the integration modesUse the modes that fit your tools and applications. Memory-Tool and moot-memory add specific memory interfaces; neither is required to use the other ways into your estate.
Scripts & automation
Work with MOOTx01 from scripts, pipelines, and automation. Anything that can run a local system command can access a memory estate.
Use the command line for individual operations or stdin/stdout for a running connection. This path fits shell scripts, scheduled jobs, and tools that launch local processes.
AI-first tools
Ask your AI to capture, recall, and work with memory. ARIA-MCP exposes tools the AI can discover and learn to use as part of its workflow.
Connect an MCP-capable AI client to MOOTx01’s memory tools. Your AI can work with the estate directly through those tools; the optional Claude-style memory adapter is a separate choice.
Deeper harness integration
Bring MOOTx01 into major AI harnesses through their integrations, with skills and workflows that help the AI use memory throughout a session.
Integrations include Claude Code, Codex, Cursor, Gemini CLI, and more. Use the integration for your harness to bring memory guidance and supported session workflows into the tools you already use.
Claude memory integration
Use MOOTx01 for Claude Code’s project memory. Bring existing memories into your estate and export both old and new project memories back when you return to Claude’s native system.
Setup offers to import Claude Code’s existing project memory files. When you disable the integration, choose the export offer to return both imported memories and newly captured project memories to Claude Code’s native memory files.
mootx01 enable harness-memorymootx01 disable harness-memoryThe optional memory-tool interface gives connected clients the familiar Claude-style memory operations, backed by reviewable MOOTx01 records.
mootx01 enable memory-toolCloud AI with local command access
Give cloud sandboxed AI services (for example GrokBot) that can run commands on your machine a path into your local MOOTx01 estate through BotLink.
BotLink accepts command-line calls and returns structured results. It connects to the local daemon or uses a local subprocess, so the AI service needs permission and a way to execute commands on your machine.
Shared MCP access for stdio clients
Connect stdio-based harnesses to a shared resident MCP server. Claude Desktop’s local MCP connection can use the same estate as your other tools.
MootProxy forwards the client’s stdin/stdout requests to the local MOOTx01 daemon. The daemon owns the estate while multiple clients connect through it.
Client launch command: mootx01 proxy
Multiple memory systems
An optional sample application that mirrors writes to MOOTx01 and another memory system. Useful for migrations, comparisons, or working with both stores.
The moot-bridge sample includes a configuration pairing MOOTx01 with MemPalace. Reads come from the selected primary; configured writes are mirrored to the second system.
Build the sample from source and configure the two backends. It is separate from the standard MOOTx01 installation.
Deterministic application integration
Build applications against a stable API that changes at a more deliberate pace. ARIA-JSON provides predictable contracts for deterministic integrations.
Use the authenticated HTTP + JSON application interface when your software needs stable operations and compatibility checks. It provides a separate contract from the AI-facing MCP interface.
Messages API developers
Add reviewable memory to your own agent loop with the optional Python handler for Anthropic’s memory_20250818 tool.
Use the drop-in SDK integration or the standalone handler with a running MOOTx01 daemon. Your application keeps the tool contract while MOOTx01 stores the underlying records.
pip install moot-memoryWork with Obsidian, LLM Wiki, or Google OKF. MOOTx01 connects your vault with the memory your AI can recall. The bridge works in both directions and belongs to the open-source Community core.
With vault sync enabled, MOOTx01 watches for changes to your Markdown notes and periodically writes exportable memories back to the vault. Notes stay readable as ordinary files, with connections represented as links.
You can also import, export, or check for changes through the MCP tools when you want to manage the exchange yourself.
Continuous sync is optional. Only memories marked exportable are written out by the sync service. Deleting a note in the vault does not delete the corresponding memory in MOOTx01.
Vault sync connects local files with your estate. Personal iCloud sync is a separate feature of the commercial Apple apps.
Capture the ideas, facts, and conversations you choose to keep. MOOTx01 preserves the original material and its source so that the next question can draw on more than the current chat.
A useful record carries more than its words. MOOTx01 keeps provenance, confirmation, and history alongside the content, so you can inspect what your tools remember.
Fulcrum is a personal organizer with native AI integration: on-device intelligence, BYO-AI, and direct connections to frontier models. Beta testing is underway.
Dock it to MOOTx01 Pro to give your connected AI access to the project outline you share and a planner and to-do list of its own. Review and update the plan from any Fulcrum app while your agent carries out assigned work and reports progress.
Start with the open-source engine and Community app.