MemoryRouter MCP server

What tools does MemoryRouter expose? (10)

Read from the live server. Click any tool for its input schema.

• search_memoriesUse 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, principles, what matters most), tier 2 holds reflections of specific meaningful events, tier 1 hold
• date_search_memoriesUse 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 specific meaningful events, tier 1 holds raw verbatim memories. Match filters to the question. Time-bounded
• store_memoryUse 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_statusUse 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_memoriesUse 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 items. Requires separate memories:delete authorization and destructive host confirmation.
• consolidate_memoriesUse 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 instructions for writing reflection entries. Follow the returned instructions to write the entries, the
• commit_reflectionsUse 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 sources consolidated. Safe to retry: committing the same batch twice returns the original result.
• inspect_memoryUse 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 repeatedly to drill down from a high-level reflection to the tier 2 reflections and raw memories beneat
• delete_memoriesUse 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. This cannot be undone. For deleting everything, forget_all_memories is the separate whole-vault tool.
• searchUse 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.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%not measurable

  No commit history available.

• Adoption20%not measurable

  No usage data available.

• Transparency20%25%

  1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

• Provenance15%0%

  No source repository to trace the code back to.

• Packaging15%75%

  Remote endpoint; authentication requirements not declared.

Maintain MemoryRouter? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![MemoryRouter on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/ai-memoryrouter-memoryrouter)](https://mcp-skills-hub.vercel.app/mcps/ai-memoryrouter-memoryrouter)