Windsurf emem, the verifiable memory protocol for the physical world emem_entity
How to: Windsurf emem, the verifiable memory protocol for the physical world emem_entity
Add emem, the verifiable memory protocol for the physical world to Windsurf
-
01
Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"emem": {
"serverUrl": "https://emem.dev/mcp"
}
}
}-
02
Save the file and restart Windsurf.
-
03
Ask for something emem_entity does. Windsurf lists the server's tools on connect and calls emem_entity 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.
Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs
Set these first
emem, the verifiable memory protocol for the physical world will not start until these are set, so emem_entity 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.