emem, the verifiable memory protocol for the physical world

MCP server · by Vortx-AI

Knowledge & Memory DockerStreamable HTTP v2.4.4

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

View source ↗ Website ↗ Generate config for multiple servers More servers

Install

unavailable — the image reference already carries a tag

Docker
docker run -i --rm ghcr.io/vortx-ai/emem:latest
Streamable HTTP
https://emem.dev/mcp

Setup by client

Pick your client — the config below is generated for this server (both local and hosted-endpoint forms). Copy respects the “Pin version” switch above.

claude_desktop_config.json

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

Remote (hosted) endpoint

https://emem.dev/mcp

Claude Desktop: Settings → Connectors → Add custom connector, paste this URL.

Format verified against the official Claude Desktop docs ↗.

Environment variables

Defined in the server's official registry manifest. Required secrets are shown as <YOUR_…> placeholders in the configs above.

  • 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.

GitHub

⭐ 69 stars · 最近更新于 18 天前 · Apache-2.0 license

About this server

Encode where the data lives. Decode with any AI. emem is shared, verifiable memory for machines and AI. The proof travels; the files stay where they are. Try it, no key…

Summary from the project README — github.com/Vortx-AI/emem

Distributed as Docker, Streamable HTTP, listed under Knowledge & Memory. Review our MCP security guide before granting access to real data.

Frequently asked questions

What does the emem, the verifiable memory protocol for the physical world MCP server do?

Encode where the data lives. Decode with any AI. emem is shared, verifiable memory for machines and AI. The proof travels; the files stay where they are. Try it, no key

How do I install emem, the verifiable memory protocol for the physical world?

Run the install command shown above, then paste the config for your client (Claude Desktop, Claude Code, Cursor, VS Code or Windsurf) into its MCP settings and restart the client.

Is emem, the verifiable memory protocol for the physical world free to use?

The MCP server itself is free to install. The source is public on https://github.com/Vortx-AI/emem. Any third-party service it calls may require its own API key and account.

Which clients support emem, the verifiable memory protocol for the physical world?

Any MCP-compatible client can use it, including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and custom agents.

Add this badge

Publish this server? Link back with a badge on your README or site — copy either snippet.

Listed on MCPNav

Markdown

[![Listed on MCPNav](https://mcpnav.net/badge/emem.svg)](https://mcpnav.net/server/emem/)

HTML

<a href="https://mcpnav.net/server/emem/"><img src="https://mcpnav.net/badge/emem.svg" alt="Listed on MCPNav" height="20"></a>