Universal Memory Protocol – a shared format for agent memory
Key takeaways
- Quickstart Git Hub The third interoperability layer Section titled “The third interoperability layer” Agents can already call tools (MCP) and talk to each other (A2A).
- In simple terms: you already have useful memories scattered across agent files, Claude/Codex project notes, Recall exports, Obsidian folders, Postgres, Redis, SQLite, and vector databases.
- Tools - MCP Model Context Protocol standardized how agents call functions and read resources.
Quickstart Git Hub The third interoperability layer Section titled “The third interoperability layer” Agents can already call tools (MCP) and talk to each other (A2A). What they can’t do is carry memory across sessions, agents, and vendors. Every harness reinvents memory privately and non-portably. UMP fixes that.
In simple terms: you already have useful memories scattered across agent files, Claude/Codex project notes, Recall exports, Obsidian folders, Postgres, Redis, SQLite, and vector databases. UMP turns those into one portable memory shape and one small operation set, so new agents and new stores can extend the same memory instead of starting over.
Tools - MCP Model Context Protocol standardized how agents call functions and read resources.