Emem MCP Server

by vortx-aiio.github.Vortx-AI/ememv2.4.2

Signed geospatial facts with citable receipts for place-based questions: elevation, land cover, surface water, vegetation and built-up areas.

65Dockerremoteofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active1d ago

Install Emem MCP server

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

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

{
  "mcpServers": {
    "emem": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://emem.dev/mcp"
      ]
    }
  }
}

Or add it as a custom connector under Settings → Connectors. The config above bridges via mcp-remote.

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

{
  "mcpServers": {
    "emem": {
      "serverUrl": "https://emem.dev/mcp"
    }
  }
}

Configuration

Variable	Required	Secret	Description
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.