Cross-Agent Memory
Local shared memory service that lets AI coding agents search one indexed store over MCP
- Pricing
- Open source
- Platforms
- macOS, Linux, API
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Cross-Agent Memory
Cross-Agent Memory is an open-source MCP server for knowledge and memory. It is available on macOS, Linux, API, CLI and self-hosted.
The README says the service ingests session history from tools like Claude Code, OpenCode and ZCode, plus any project folder you register, and indexes it with local Ollama embeddings into a single SQLite file. Agents reach that store through an HTTP API on port 5370 or through an MCP stdio server that exposes memory_search, memory_write and memory_stats.
Search runs a staged pipeline: a 1-bit Hamming prefilter, sqlite-vec KNN, then re-ranking with time decay and diversity. The project also covers operations such as health endpoints, backups, restore and tier maintenance scripts, and it binds to localhost by default.
It suits developers who switch between several AI coding assistants and want decisions and project context to carry over. The README states macOS and Linux are supported and Windows is not yet, and that multi-user or server mode is only on the roadmap.
Tools this server provides (3)
Taken from the project documentation; the running server may differ.
- memory_search
- Semantic search across all indexed sessions and projects.
- memory_write
- Store a decision, insight or discovery for future sessions.
- memory_stats
- List collections and their sizes.
What it does
- Cross-tool session ingestion
- Connectors pull history from Claude Code, OpenCode and ZCode stores, and a file watcher covers project docs folders.
- Local embeddings and storage
- Embeddings come from a local Ollama model and are stored in a single SQLite file with a sqlite-vec index.
- MCP memory tools
- Exposes memory_search, memory_write and memory_stats to any MCP-capable client over stdio.
- HTTP search API
- Offers search, memory capture, feedback and project registration endpoints on a local port.
- Optional bearer-token auth
- Environment variables can require a bearer token for writes and, optionally, for reads.
- Backups and health checks
- Includes backup and restore endpoints plus a health endpoint that reports degraded reasons.
Good for
- Share decisions made in one coding agent with another agent without re-pasting context
- Search past Claude Code or OpenCode sessions for why an architecture choice was made
- Index a project's docs and notes so any MCP-enabled assistant can recall them
- Keep agent memory entirely on a local machine for privacy-sensitive work
Pricing
Open source
Free, MIT-licensed, self-hosted
Cross-Agent Memory FAQ
Does any data leave my machine?
The README says the service runs locally with no cloud component and that embeddings are computed on the machine through Ollama.
Which operating systems are supported?
The README lists macOS or Linux, and states Windows is not supported yet because the connectors use POSIX file locks.
Which MCP tools does it expose?
The README lists memory_search, memory_write and memory_stats.
What license is it under?
The README and the registry entry both state MIT.
Is Cross-Agent Memory free?
Yes. Cross-Agent Memory is open source, so you can use and self-host it for free.
What are the best alternatives to Cross-Agent Memory?
The closest alternatives to Cross-Agent Memory are MCP Memory, Agent Memory MCP, mcp-memory-rs, Kognite and Compound Memory.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.