Universal Memory Protocol – a shared format for agent memory
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.
Model Context Protocol standardized how agents call functions and read resources.
Agent2Agent standardized how agents discover and invoke one another.
Universal Memory Protocol standardizes how agents remember - portable knowledge across sessions, agents, and vendors.
Use the MCP server when you want agent memory immediately. Use the TypeScript SDK when you are building a memory-aware app or agent runtime. Use HTTP when the client is Python, Go, Swift, a browser, or anything else that can send JSON.