MCP is the interface
Your agents call palace_* tools through the Model Context Protocol. The workflow stays familiar, but the memory backend becomes durable and shared.
Palace exposes memory tools over MCP while keeping the server, database, embeddings, and API keys under your control.
Your agents call palace_* tools through the Model Context Protocol. The workflow stays familiar, but the memory backend becomes durable and shared.
A private MCP memory server lets developers coordinate through shared recall while avoiding a scattered set of cloud-side memories per tool or vendor.
Palace focuses on remembered decisions, preferences, prior fixes, session diaries, and provenance rather than generic document chat.