Skip to content

Cross-Agent Memory vs MCP Memory

Cross-Agent Memory is an open-source MCP server for knowledge and memory. MCP Memory is an open-source MCP server for knowledge and memory.

  • Cross-Agent Memory is best for share decisions made in one coding agent with another agent without re-pasting context.
  • MCP Memory is best for let a coding agent remember project decisions across sessions.
What it is
Cross-Agent Memory is an open-source MCP server for knowledge and memory.
MCP Memory is an open-source MCP server for knowledge and memory.
Best for
Share decisions made in one coding agent with another agent without re-pasting context
Let a coding agent remember project decisions across sessions
Kind
MCP server
MCP server
Pricing
Open source
Open source
Platforms
macOS, Linux, API, CLI, self-hosted
CLI, self-hosted, Linux, macOS, Windows
Runs
Locally
Open source
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
Let a coding agent remember project decisions across sessions; Share one memory between Claude Code and Cursor; Keep separate memory per project with namespaces

What Cross-Agent Memory 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.

What MCP Memory does

  • Local SQLite store

    One database file holds every memory, with backup by copying it.

  • BM25 search

    FTS5 ranking with namespace filtering.

  • Namespaces and tags

    Separate memory pools per project, with tags and metadata.

  • Export and import

    Move memories as JSONL between machines.

  • Tool annotations

    Read and destructive hints let clients gate approvals.

  • Two transports

    Use stdio or a local HTTP endpoint.

Cross-Agent Memory vs MCP Memory: questions

Is Cross-Agent Memory or MCP Memory cheaper?

Both are open source. Compare current plans on each official site.

What is the difference between Cross-Agent Memory and MCP Memory?

Cross-Agent Memory is an open-source MCP server for knowledge and memory. MCP Memory is an open-source MCP server for knowledge and memory.

Keep comparing