MCP · Model Context Protocol · AI Memory
Give your AI assistant persistent memory — no accounts, no setup. Connect any MCP-compatible client to MantleDB in one line of config.
https://mcp.mantledb.sh/ssehttps://mcp.mantledb.sh/Add MantleDB to your MCP client config. No install, no API keys — just the URL.
{
"mcpServers": {
"mantledb": {
"url": "https://mcp.mantledb.sh/sse"
}
}
}
The AI can call these tools directly. All tools take namespace as a required parameter. key is only needed for claimed (write-protected) namespaces.
Each tool call includes the namespace and optional key directly — the MCP server is stateless. Different conversations, projects, or users can all use their own namespaces independently.
// AI calls write:
namespace: "alice-project"
path: "preferences"
data: { "tone": "concise", "lang": "en" }
key: "sk_abc123"
// AI calls read:
namespace: "alice-project"
path: "preferences"
key: "sk_abc123"
// → { "tone": "concise", "lang": "en" }
The most common use case: give your AI assistant memory that persists across conversations. Add this to your system prompt:
You have access to MantleDB via MCP tools.
Use namespace "alice" with key "sk_abc123" to persist
information across our conversations.
- Before answering, check if relevant context is stored.
- After learning something useful about me, save it.
- Use clear path names like "preferences", "projects/x", "notes/2024".
The AI will then autonomously decide what to save and when — preferences, project context, facts about you — and recall them in future sessions without being asked.
Namespaces require no sign-up. Pick any name and start writing immediately.
claim tool
or GET /v2/claim/:namespace via the HTTP API.
The key is shown once — save it in your system prompt.
Unclaimed namespaces inactive for 30 days are purged automatically. Claimed namespaces are retained for 90 days of inactivity. See Pro for extended retention.