{
  "manifest_version": "1",
  "slug": "mem0",
  "title": "Mem0",
  "headline": "Self-host Mem0, one memory for agents on all your VMs",
  "description": "Self-host the Mem0 server with Docker on an exe.dev VM: pgvector, the dashboard, MCP for Claude Code and Codex, models without an OpenAI key.",
  "category": "ai-agents",
  "tags": [
    "mem0",
    "mem0 self-host",
    "mem0 docker",
    "openmemory",
    "agent memory",
    "mcp memory server",
    "pgvector",
    "claude code memory",
    "codex memory",
    "long-term memory"
  ],
  "url": "https://exe.dev/deploy/mem0",
  "markdown_url": "https://exe.dev/deploy/mem0.md",
  "upstream": {
    "website": "https://mem0.ai",
    "source": "https://github.com/mem0ai/mem0",
    "docs": "https://docs.mem0.ai/open-source/setup",
    "license": "Apache-2.0"
  },
  "example_vm_name": "my-mem0",
  "time": "15 minutes",
  "stack": [
    {
      "name": "Mem0 server 2.2.1",
      "detail": "Mem0's FastAPI REST server, built from the v2.2.1 tag, in Docker Compose",
      "port": 8888,
      "data": "~/mem0/data/history"
    },
    {
      "name": "PostgreSQL 17 with pgvector",
      "detail": "pgvector/pgvector:pg17; the memories, their vectors, users and API keys",
      "data": "~/mem0/data/postgres"
    },
    {
      "name": "Dashboard and MCP",
      "detail": "Mem0's Next.js dashboard and a small MCP bridge, behind nginx",
      "port": 8000
    },
    {
      "name": "exe.dev LLM integration",
      "detail": "gpt-5.4-mini extracts memories, text-embedding-3-small indexes them; no API key"
    },
    {
      "name": "Nightly backup",
      "detail": "pg_dumpall, the history log and the secrets; a systemd timer keeps two weeks",
      "data": "~/mem0-backups"
    }
  ],
  "access": [
    {
      "url": "https://my-mem0.exe.xyz/",
      "who": "private",
      "what": "the dashboard, behind exe.dev login and Mem0's own login"
    },
    {
      "url": "https://my-mem0.exe.xyz/mcp",
      "who": "private",
      "what": "MCP for Claude Code, Codex and Cursor; a VM token plus a Mem0 API key"
    },
    {
      "url": "https://my-mem0.exe.xyz:8888/",
      "who": "private",
      "what": "the REST API and its /docs; a VM token plus a Mem0 API key"
    }
  ],
  "delivers": [
    "Mem0 2.2.1's REST server, dashboard and pgvector database in Docker Compose, back by themselves after a reboot",
    "Memories extracted and embedded through exe.dev's LLM integration, with no OpenAI key on the VM",
    "The dashboard at `https://\u003cvm\u003e.exe.xyz/`, behind exe.dev login, with the owner as Mem0's admin",
    "An MCP endpoint at `/mcp` and the REST API on port 8888, each needing a VM token and a Mem0 API key from outside",
    "A memory added and found again through the API and through MCP",
    "Nightly backups of the database, history and secrets in `~/mem0-backups`"
  ],
  "owner_runs_after": [
    "ssh exe.dev ssh-key generate-api-key --vm=my-mem0 --label=mem0-agents --exp=90d"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Mem0%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fmem0.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-mem0.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-mem0.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20Mem0%202.2.1%27s%20REST%20server%2C%20dashboard%20and%20pgvector%20database%20in%20Docker%20Compose%2C%20back%20by%20themselves%20after%20a%20reboot%0A-%20Memories%20extracted%20and%20embedded%20through%20exe.dev%27s%20LLM%20integration%2C%20with%20no%20OpenAI%20key%20on%20the%20VM%0A-%20The%20dashboard%20at%20%60https%3A%2F%2F%3Cvm%3E.exe.xyz%2F%60%2C%20behind%20exe.dev%20login%2C%20with%20the%20owner%20as%20Mem0%27s%20admin%0A-%20An%20MCP%20endpoint%20at%20%60%2Fmcp%60%20and%20the%20REST%20API%20on%20port%208888%2C%20each%20needing%20a%20VM%20token%20and%20a%20Mem0%20API%20key%20from%20outside%0A-%20A%20memory%20added%20and%20found%20again%20through%20the%20API%20and%20through%20MCP%0A-%20Nightly%20backups%20of%20the%20database%2C%20history%20and%20secrets%20in%20%60~%2Fmem0-backups%60%0A%0ARead%20the%20whole%20recipe%2C%20closed%20details%20included%2C%20and%20follow%20%22Set%20up%20by%0Ahand%22%20in%20order%2C%20skipping%20VM%20creation%3B%20the%20walkthrough%20above%20it%20is%20for%20the%0Aowner.%20Make%20the%20owner%20Mem0%27s%20admin%20with%20the%20email%20from%20the%20reflection%0Aintegration%2C%20as%20written.%20Never%20overwrite%20an%20existing%20~%2Fmem0%2F.env%20or%0Aadmin.json.%20Don%27t%20make%20the%20VM%20public%20or%20share%20it.%20Don%27t%20run%20Restore%20or%0AUpdate%2C%20and%20don%27t%20reboot.%20The%20VM%20can%27t%20reach%20its%20own%0Ahttps%3A%2F%2F%3Cvm%3E.exe.xyz%2C%20so%20checks%20use%20localhost.%20Finish%20by%20telling%20the%0Aowner%20the%20dashboard%20URL%2C%20that%20the%20admin%20password%20is%20in%0A~%2Fmem0%2Fadmin.json%2C%20and%20the%20%60ssh%20exe.dev%20ssh-key%20generate-api-key%60%0Acommand%20to%20run%20on%20their%20computer%2C%20then%20point%20them%20to%20%22Connect%20your%0Aagents%22.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open%20and%20these%20commands%2C%20which%20only%20I%20can%20run%2C%20from%20my%20own%20computer%20%28with%20this%20VM%27s%20name%20in%20them%29%3A%0A%20%20ssh%20exe.dev%20ssh-key%20generate-api-key%20--vm%3Dmy-mem0%20--label%3Dmem0-agents%20--exp%3D90d%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/mem0/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Mem0 on this VM by following the exe.dev recipe at https://exe.dev/deploy/mem0.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-mem0. This VM's name is the output of `hostname`: use it wherever the recipe writes my-mem0. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- Mem0 2.2.1's REST server, dashboard and pgvector database in Docker Compose, back by themselves after a reboot\n- Memories extracted and embedded through exe.dev's LLM integration, with no OpenAI key on the VM\n- The dashboard at `https://\u003cvm\u003e.exe.xyz/`, behind exe.dev login, with the owner as Mem0's admin\n- An MCP endpoint at `/mcp` and the REST API on port 8888, each needing a VM token and a Mem0 API key from outside\n- A memory added and found again through the API and through MCP\n- Nightly backups of the database, history and secrets in `~/mem0-backups`\n\nRead the whole recipe, closed details included, and follow \"Set up by\nhand\" in order, skipping VM creation; the walkthrough above it is for the\nowner. Make the owner Mem0's admin with the email from the reflection\nintegration, as written. Never overwrite an existing ~/mem0/.env or\nadmin.json. Don't make the VM public or share it. Don't run Restore or\nUpdate, and don't reboot. The VM can't reach its own\nhttps://\u003cvm\u003e.exe.xyz, so checks use localhost. Finish by telling the\nowner the dashboard URL, that the admin password is in\n~/mem0/admin.json, and the `ssh exe.dev ssh-key generate-api-key`\ncommand to run on their computer, then point them to \"Connect your\nagents\".\n\nFinish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them):\n  ssh exe.dev ssh-key generate-api-key --vm=my-mem0 --label=mem0-agents --exp=90d\n",
    "prompt_url": "https://exe.dev/deploy/mem0/prompt.txt"
  },
  "published": "2026-11-21",
  "updated": "2026-11-21",
  "verified": "2026-11-21",
  "related": [
    "claude-mem",
    "gbrain",
    "claude-code",
    "codex",
    "hermes-agent",
    "openclaw"
  ],
  "alternatives": [
    "Mem0 Platform",
    "Zep"
  ],
  "files": [
    "https://exe.dev/deploy/mem0/mem0-mcp.py"
  ]
}
