← memoryrouter.ai

INDIVIDUAL MCP TOOL

delete_memories

Use this only when the user explicitly asks to delete specific memories and confirms after seeing what will be deleted.

memoryrouter.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.memoryrouter.ai/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

memoryrouter.ai

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.memoryrouter]
url = "https://mcp.memoryrouter.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "memoryrouter": {
      "type": "http",
      "url": "https://mcp.memoryrouter.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: memoryrouter
Remote MCP URL: https://mcp.memoryrouter.ai/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": {
    "memoryrouter": {
      "url": "https://mcp.memoryrouter.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "memoryrouter": {
      "type": "http",
      "url": "https://mcp.memoryrouter.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "memoryrouter",
  "transport": "streamable-http",
  "url": "https://mcp.memoryrouter.ai/mcp"
}
MCP Inspector

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

Related tools

  • search_memories — Use this when the user asks about a prior decision, preference, person, project, or other fact that may be in their connected MemoryRouter vault.
  • date_search_memories — Use this to retrieve memories from a specific time window, for questions like 'what happened last week' or 'most important things this month or lately'.
  • store_memory — Use this only when the user explicitly asks to remember something or confirms a proposed durable fact.
  • memory_status — Use this when the user asks whether MemoryRouter is connected, which opaque vault binding is active, or how many memories/tokens the connected vault contains.
  • forget_all_memories — Use this only after the user explicitly requests a full-vault deletion, receives a permanent whole-vault warning, and provides the exact confirmation phrase in a later turn.
  • consolidate_memories — Use this when the user asks to consolidate, reflect on, or organize their memories, or when memory_status or a search result reports that consolidation is available.
  • commit_reflections — Use this to complete a consolidation started with consolidate_memories.
  • inspect_memory — Use this when the user asks why the assistant believes something, or wants to see the source memories behind a reflection.