Locker MCP server
{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp"
}
}
}{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp"
}
}
}{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp"
}
}
}{
"servers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp"
}
}
}{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.3.1
What it does
Locker provides durable memory for AI agents addressed by wallet key, persisting state across sessions and processes. Agents store and recover named checkpoints using only their EVM keypair, with no signup or additional secrets required.
- Save and restore agent state between sessions so a fresh process can resume work without losing context.
- Share memory across multiple agent instances or vendors by using the same wallet key across deployments.
- Receive messages from other agents via paid mail slots that wait for your key to sign and retrieve them.
Tools this server exposes
| Tool | Does |
|---|---|
| memory_save | Save text content to a named checkpoint slot in your wallet-addressed locker. |
| memory_load | Load text content from a named checkpoint slot using your wallet key. |
| locker_capabilities | Query available capabilities of the Locker service. |
| locker_invite | Generate an invite link configured for a specific AI agent vendor (Codex, Gemini, Cursor, etc.). |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.