MCP Hub › Developer Tools › emem, the verifiable memory protocol for the physical world

emem, the verifiable memory protocol for the physical world MCP server

by Vortx-AI · io.github.Vortx-AI/emem

Shared, verifiable memory for machines and AI. Encode where data lives; decode with any AI.

🛠 Developer ToolsRemoteDockerv2.4.4
Open in MCP HubGitHub repository ↗Website ↗

How to install emem, the verifiable memory protocol for the physical world

Remote (http)

claude mcp add --transport http emem https://emem.dev/mcp

Or add it to your MCP config (Claude Desktop, Cursor, VS Code):

{
  "mcpServers": {
    "emem": {
      "type": "http",
      "url": "https://emem.dev/mcp"
    }
  }
}

Docker

claude mcp add emem -- docker run -i --rm ghcr.io/vortx-ai/emem:latest

Or add it to your MCP config (Claude Desktop, Cursor, VS Code):

{
  "mcpServers": {
    "emem": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/vortx-ai/emem:latest"
      ]
    }
  }
}

Environment variables:
PORT – PaaS port convention: the container entrypoint binds 0.0.0.0:$PORT when EMEM_BIND is not set explicitly. Falls back to 5051.
EMEM_BIND – Bind address for the HTTP server. When unset, the entrypoint derives it from PORT, falling back to 0.0.0.0:5051.
EMEM_DATA – Path to the persistent data directory (sled cache + ed25519 identity). Mount a volume here; on managed platforms that mount /data, set EMEM_DATA=/data.
EMEM_PUBLIC_URL – Optional canonical origin for self-referencing URLs in MCP responses (e.g. https://emem.dev). When unset the server falls back to urn:emem.
EMEM_TLS_DOMAINS – Comma-separated hostnames for built-in Let's Encrypt ACME (TLS-ALPN-01). When set, the server binds 0.0.0.0:443 instead of EMEM_BIND.

Replace placeholders in <angle brackets> with your own values. Review what a server can access before you enable it.

Details

Version
2.4.4
Published
2026-10-18
Updated
2026-10-18
Namespace
io.github.Vortx-AI
Source
Vortx-AI/emem

Similar developer tools servers