Purpose-built memory tools
Palace exposes MCP tools for search, session context, diary writes, KG facts, verification, and team memory workflows.
MCP memory server
An MCP memory server for AI coding agents
MCP
Palace gives MCP-capable coding agents a durable memory backend for decisions, preferences, fixes, and project history.
Works with Cursor, Claude Code, Codex, and other MCP-capable clients.
Combines semantic retrieval, BM25-style search, diaries, and knowledge graph recall.
Open-source MIT core for solo developers; paid server for shared team memory.
Palace vs wiring a vector DB to MCP yourself
| Feature | Palace | DIY MCP + vector DB |
|---|---|---|
| MCP tools | Search, diary, KG, session, verify | You design and maintain the tool surface |
| Retrieval stack | Hybrid search + KG + diaries | Usually embeddings + your glue code |
| Agent workflow | Install rules + memory protocol | You invent capture and recall rules |
| Team server path | Paid self-hosted Palace Server | Custom ops, auth, and multi-user design |
| Provenance | Built into recall | Only if you build it |
| Time to value | CLI + MCP clients | Weeks of integration work |
Not just a vector DB behind MCP
You can wire embeddings to an MCP stub yourself. Palace ships the coding-agent workflow around that storage: hybrid retrieval, diaries, knowledge graph facts, provenance, and a path from local core to team server.
Cross-agent layer
Instead of each agent keeping isolated context, Palace acts as a shared layer that works across Cursor, Claude Code, Codex, and Claude Desktop.
Self-hosted when it matters
Use local palace-rs for yourself, then deploy Palace Server when your team needs shared memory inside your network.