MCP Server
MCP
emem, the verifiable memory protocol for the physical world
Shared memory for AI agents. One address per fact, one signature you check. No key to read.
Install
oci:ghcr.io/vortx-ai/emem:latest
Configuration Example
{
"remotes": [
{
"type": "streamable-http",
"url": "https://emem.dev/mcp"
}
],
"packages": [
{
"registryType": "oci",
"identifier": "ghcr.io/vortx-ai/emem:latest",
"runtimeHint": "docker",
"transport": {
"type": "streamable-http",
"url": "http://localhost:5051/mcp"
},
"environmentVariables": [
{
"description": "PaaS port convention: the container entrypoint binds 0.0.0.0:$PORT when EMEM_BIND is not set explicitly. Falls back to 5051.",
"name": "PORT"
},
{
"description": "Bind address for the HTTP server. When unset, the entrypoint derives it from PORT, falling back to 0.0.0.0:5051.",
"value": "0.0.0.0:5051",
"name": "EMEM_BIND"
},
{
"description": "Path to the persistent data directory (sled cache + ed25519 identity). Mount a volume here; on managed platforms that mount /data, set EMEM_DATA=/data.",
"value": "/var/emem",
"name": "EMEM_DATA"
},
{
"description": "Optional canonical origin for self-referencing URLs in MCP responses (e.g. https://emem.dev). When unset the server falls back to urn:emem.",
"name": "EMEM_PUBLIC_URL"
},
{
"description": "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.",
"name": "EMEM_TLS_DOMAINS"
}
]
}
]
}
mcp
model-context-protocol
streamable-http
oci
By
Comments
Sign in to leave a comment