Grok emem, the verifiable memory protocol for the physical world emem_memory_token
How to: Grok emem, the verifiable memory protocol for the physical world emem_memory_token
Add emem, the verifiable memory protocol for the physical world to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"emem": {
"type": "http",
"url": "https://emem.dev/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something emem_memory_token does. Grok lists the server's tools on connect and calls emem_memory_token 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.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
emem, the verifiable memory protocol for the physical world will not start until these are set, so emem_memory_token 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.