← Registry

General Tools

memoryrouter.ai

Provides persistent memory storage and retrieval for personal or agent contexts.

1 endpoint5 known toolsFirst detected August 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://mcp.memoryrouter.ai/mcp

No auth detected

MCP server metadata

Name
MemoryRouter
Version
1.1.0
Capabilities
toolsresources
Server instructions

MemoryRouter is an external, OAuth-selected memory vault providing persistent memory shared across AI platforms; it is separate from any built-in platform memory. Search it when the user asks about prior decisions, preferences, people, projects, or saved context. Use search_memories for semantic recall and search for compatibility knowledge lookup. Never claim a search or save happened unless a tool result confirms it. Tool use is model-directed, so recall and capture are not guaranteed on every turn. Only store concise durable content with store_memory after the user explicitly asks or confirms. Before full-vault deletion with forget_all_memories, warn in one turn that it permanently deletes the entire vault and cannot delete one item, then require the exact phrase DELETE ALL MEMORIES in a later turn plus separate memories:delete authorization and destructive host confirmation; per-memory deletion is not available through this server. One OAuth connection is bound to one vault. Use separate vaults for strict project or organization isolation; disconnect and reconnect to switch vaults. Use memory_status to show the opaque active vault reference and granted scopes. Retrieval and statistics require read authorization; storing and deleting require separate write and delete authorization.

Known tools 5

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.

Inferred read-only
store_memory

Use this only when the user explicitly asks to remember something or confirms a proposed durable fact.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
search

Use this legacy compatibility alias when a client explicitly requests a tool named search.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.