← saastemly.com

INDIVIDUAL MCP TOOL

delete_memories

Delete your stored memories, like mem0's delete memory and delete all memories.

saastemly.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mem0-cloud.saastemly.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for delete_memories and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a deletion term.

Parent server

saastemly.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

.mcp.json

{
  "mcpServers": {
    "mem0-cloud": {
      "type": "http",
      "url": "https://mem0-cloud.saastemly.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: mem0-cloud
Remote MCP URL: https://mem0-cloud.saastemly.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "mem0-cloud": {
      "type": "http",
      "url": "https://mem0-cloud.saastemly.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "mem0-cloud",
  "transport": "streamable-http",
  "url": "https://mem0-cloud.saastemly.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • 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).
  • 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.
  • get_memories — Read your stored memories, like mem0's get memory and get all memories.