Not what was said. Not raw data. The actual learned structure — associative pathways, activation patterns, consolidated knowledge — transferred directly between agents.
M2MP is the missing memory layer in the AI agent stack. An open protocol for privacy-preserving transfer of learned associative memory between any AI agents.
The AI agent protocol stack has three established layers — and one gap.
When Agent A has spent months learning a user's preferences — Hebbian-strengthened pathways, consolidated semantic clusters — and Agent B needs that knowledge, there is no standard way to transfer it.
Today, agents share knowledge by serializing into text and hoping the other side reconstructs something useful.
M2MP transfers the associative structure itself — not its description.
A travel agent with 50+ sessions of learned preferences hands off to a restaurant agent that has never seen the user. Here's what happens.
Travel Assistant
Semantic privacy level
Restaurant Agent
M2MP combines established models from cognitive science into a unified memory architecture that produces a weighted association graph as a natural byproduct of operation.
These layers produce a weighted, directed graph of learned associations — the memory graph. This graph is what M2MP transfers.
MCP-compatible. M2MP operations are implemented as MCP tools. Any MCP-capable host can participate. No new transport layer. No new auth system.
Three configurable privacy levels. Strip content, keep structure. Transfer what agents learned without exposing what was said.
Graph shape, edge weights, activation patterns, BCM thresholds. No content, no embeddings.
Observation · Research · Analytics
Topology + textual memory content. Agent B can re-embed and query immediately. No embeddings.
Default · Cross-agent handoff
Everything: content, embedding vectors, and node ID mappings. Complete carbon copy.
Migration · Backup · Development
Privacy is graduated, not binary. The semantic level is the sweet spot for collaboration — Agent B receives enough content to re-embed and query, while the sender's raw embedding vectors and original IDs stay private. Structure + content transfers. Raw representations don't.
Open protocol. Open source. Be first to build with M2MP.