ai.memoryrouter/memoryrouter · v1.1.0 · agents-and-memory
MemoryRouter is healthy: it completed an MCP handshake in 1759 ms and exposes 10 tools. It scores 59/100.
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Add to my toolfindr inventory →
Healthy · last checked 2026-10-14T09:00:57.015Z UTC
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-14T09:00:57.015Z | ok | 1759 ms |
| health | 19 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 5 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
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. Semantically searches only the OAuth-selected vault and does not modify it. Tier guide: tier 3 holds the highest-level consolidated reflections (identity,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'. Tier guide: tier 3 holds the highest-level consolidated reflections (identity, principles, what matters most), tier 2 holds reflections of specificstore_memory Use this only when the user explicitly asks to remember something or confirms a proposed durable fact. Saves concise user-approved content to the OAuth-selected vault; do not use it for silent conversation capture.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. Does not reveal the memory key.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. Permanently deletes every memory in the OAuth-selected vault. This cannot delete one memory; use delete_memories for specific 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. Checks out a batch of unconsolidated memories from the connected vault under a 15 minute lease and returns their texts plus server inscommit_reflections Use this to complete a consolidation started with consolidate_memories. Submits the reflection entries you wrote for the checked-out batch. Each entry is standalone prose with an importance rating from 1 to 10. The server stores the reflections, links them to their source memories, and marks the souinspect_memory Use this when the user asks why the assistant believes something, or wants to see the source memories behind a reflection. Given a memory id from a search result, returns the lower-tier memories that reflection was built from, or, for a raw memory, which reflections it was consolidated into. Use repdelete_memories Use this only when the user explicitly asks to delete specific memories and confirms after seeing what will be deleted. Permanently deletes the identified memories from the connected vault by their ids from search or inspect results. Deleting a raw memory does not delete reflections built from it. Tsearch Use this legacy compatibility alias when a client explicitly requests a tool named search. It searches the OAuth-selected MemoryRouter vault without modifying it. For normal ChatGPT recall, prefer search_memories; this tool does not provide citable item permalinks or Company Knowledge fetch support.No repository listed · website