Mem0 Cloud MCP Server

by saastemly Your server? Claim it

answering

Mem0 Cloud is answering right now. Last checked 10 min ago. It exposes 4 tools.

A hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):...

Uptime history 9 days of history · worst day 99%

9 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

104 ms

Response time

average over 24h

open, no key

Access

streamable-http

Mem0 Cloud missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mem0-cloud --transport http https://mem0-cloud.saastemly.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mem0-cloud": {
      "url": "https://mem0-cloud.saastemly.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mem0-cloud]
url = "https://mem0-cloud.saastemly.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mem0-cloud": {
      "url": "https://mem0-cloud.saastemly.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mem0-cloud": {
      "url": "https://mem0-cloud.saastemly.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

memories

delete_memories

Delete your stored memories, like mem0's delete memory and delete all memories. With memory_id: deletes that one memory (404 if it is not yours). Without it: deletes up to 200 of your memories matching user_id, agent_id, app_id or run_id (at least one), and says if more remain. Requires your memory_key (a secret string you generate): other keys cannot delete your memories. Price: $0.002 a call (3 free calls a day without an API key).

get_memories

Read your stored memories, like mem0's get memory and get all memories. With memory_id: returns that one memory (404 if it is not yours). Without it: returns a page {count, next, previous, results} of the memories matching user_id, agent_id, app_id or run_id (at least one; "*" matches any value), newest first. Requires your memory_key (a secret string you generate): a different key sees nothing. Price: $0.002 a call (3 free calls a day without an API key).

search_memories

Search your stored memories by meaning, like mem0's search: embeds the query and returns the closest memories with a relevance score from 0 to 1. Only memories stored under the same memory_key (your secret string; required) are searched. filters must name at least one of user_id, agent_id, app_id, run_id. Returns {results:[{id, memory, score, metadata, ...}]}. Price: $0.004 a call (3 free calls a day without an API key).

memory

add_memory

Store memories from a conversation, like mem0's add: an AI model extracts durable facts about the user from the messages (or, with infer=false, stores each message as is), embeds them and saves them privately under your memory_key (a secret string you generate; required). Identical facts are stored once. Needs at least one of user_id, agent_id, app_id, run_id. Memories are kept for 365 days. Returns {event_id, status, results:[{id, memory, event: ADD|NONE}]}. Price: $0.008 a call (3 free calls a day without an API key).

Endpoints

URL	Transport	State	Latency	Checked
https://mem0-cloud.saastemly.com/mcp	streamable-http	answering	175 ms	10 min ago

Alternatives to Mem0 Cloud

same job, measured the same way

gjalla

by gjalla

Hosted self-curating shared memory that keeps your agents working like a high-performing team

answering

Strata

by agenerationforwordz-tech

Self-hosted AI memory server. Persistent memory on your hardware, not the cloud.

14 installs/wk local only

Dakera MCP

by dakera-ai

Agent memory engine — 102 MCP tools, self-hosted, single Rust binary

local only

gjalla

by gjalla

Self-curating shared memory that keeps your agents working like a high-performing team

3 449 installs/wk local only

Pindoc

by var-gg

Code-pinned team memory for AI coding agents — typed artifacts, MCP-native, self-host.

local only

ShareBox

by zalaso

Publish the web tools your agent builds to a self-hosted ShareBox and share them like a Google Doc

922 installs/wk local only

super-log Cloud

by super-log

Read your team's hosted journal from an AI agent: every machine's streams, in hub order.

answering

Myco Brain

by thegoodguysla

Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres.

33 installs/wk local only

Mem0 Cloud — questions

Answers built from our own checks of this server.

What can Mem0 Cloud do?

It exposes 4 tools, read directly from the server on our last check. Among them: add_memory, delete_memories, get_memories, search_memories. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Mem0 Cloud working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 104 ms. The bar chart above shows every period we have measured.

How do I connect Mem0 Cloud?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Mem0 Cloud need an API key?

No. Mem0 Cloud completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Mem0 Cloud?

It answers our handshake in 104 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.