Cursor emem, the verifiable memory protocol for the physical world emem_memory_token_resolve
How to: Cursor emem, the verifiable memory protocol for the physical world emem_memory_token_resolve
Add emem, the verifiable memory protocol for the physical world to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"emem": {
"url": "https://emem.dev/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something emem_memory_token_resolve does. Cursor lists the server's tools on connect and calls emem_memory_token_resolve itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that emem, the verifiable memory protocol for the physical world's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
emem, the verifiable memory protocol for the physical world will not start until these are set, so emem_memory_token_resolve never becomes available.
-
PORT -
EMEM_BIND -
EMEM_DATA -
EMEM_PUBLIC_URL -
EMEM_TLS_DOMAINS
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.