emem — Earth memory protocol
Content-addressed, ed25519-signed memory of every place on Earth. Apache-2.0, no keys for reads.
Streamable HTTP / SSE endpoint. Add to any MCP client that supports remote servers.
https://emem.dev/mcp{
"mcpServers": {
"emem": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/vortx-ai/emem:latest"
],
"env": {
"EMEM_BIND": "<emem_bind>",
"EMEM_DATA": "<emem_data>",
"EMEM_PUBLIC_URL": "<emem_public_url>",
"EMEM_TLS_DOMAINS": "<emem_tls_domains>"
}
}
}
}EMEM_BINDBind address for the HTTP server. Defaults to 0.0.0.0:5051 inside the container.
EMEM_DATAPath to the persistent data directory (sled cache + ed25519 identity). Mount a volume here.
EMEM_PUBLIC_URLOptional 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_DOMAINSComma-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.
Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.
Expert-curated knowledge graphs for AI agents — PSFK Retail, Beauty, Sports and more.
Memory for deep conversational context across any platform