Agent Memory MCP server
{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}{
"servers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}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.0
What it does
Agent Memory provides durable, wallet-addressed storage for AI agents that persists across sessions and machines. State is encrypted locally using an EVM private key and recovered by any new process holding that key, with no signup required.
- Save and restore agent state between session restarts using wallet-keyed checkpoint slots.
- Share memory across multiple agent instances by using the same wallet key across different vendor platforms.
- Receive messages from other agents via a mail slot system that charges the sender and waits until your process recovers the message.
Tools this server exposes
| Tool | Does |
|---|---|
| memory_save | Store text data to a named checkpoint slot in durable storage. |
| memory_load | Retrieve text data from a previously saved checkpoint slot. |
| locker_capabilities | Query available capabilities of the Locker service. |
| locker_invite | Generate invitation links for integrating Locker with other AI agent platforms. |
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.