com.memxus/memxus · v1.3.2 · agents-and-memory
com.memxus/memxus is healthy: it completed an MCP handshake in 3664 ms and exposes 9 tools.
Persistent memory layer that saves and recalls your project context and preferences.
Endpoint: https://mcp.memxus.com/mcp (streamable-http)
Repository · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 9 |
| Latency | 3664 ms |
| Last checked (UTC) | 2026-10-14T20:35:44.320Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T20:35:44.320Z | Healthy | 3664 |
remember | Save important information to long-term memory. Always set collection when the topic is clear: project work → project:<slug>, personal tastes → personal:preferences. Use append_to to extend an existing memory instead of creating duplicates. Vector search indexing completes asynchronously within a fe |
recall | Search long-term memory. Call list_collections when scope is unclear. For GitHub/Notion synced content use collection project:<slug> (unified per project) or tags github/notion. Connect at dashboard.memxus.com/integrations. To search a team workspace instead of personal memory, pass workspace: <name |
get_context | Builds a formatted context block for a topic from stored memories; use when the user asks to load or recall project context. Omit topic and collection to show the text collection picker (Memxus menu flow). Call list_collections when unsure of the exact slug. Partial collection names are resolved ser |
list_memories | List recent memories in reverse-chronological order (read-only). When to use: audit what is saved, browse a collection, or collect memory IDs for get_memory or forget. When NOT: semantic search by topic → recall; one full record → get_memory; aggregate counts only → memory_stats. Behavior: default 2 |
get_memory | Retrieve the full content and metadata of one memory by its UUID. Use after list_memories or recall returned a truncated preview and you need the complete text. Returns content, memory_type, tags, collection, importance, and the creation timestamp. Get the UUID from a prior list_memories or recall r |
list_collections | List memory collections (folders/scopes) for this user. GitHub/Notion syncs appear under project:<slug> when unified collections are enabled. Use before a scoped recall/get_context when the user mentions a project name, or to look up the team workspace names accepted by the workspace parameter of th |
forget | Permanently delete one memory by UUID. When to use: user asks to remove outdated or incorrect context, or to free plan storage. When NOT: fix content → update (mode=replace); find the ID first → list_memories or recall. Requires delete OAuth scope. Non-idempotent: deleting the same memory_id twice f |
memory_stats | Show aggregate statistics about stored memories: the total count, a breakdown by memory_type and by collection, and storage bytes used versus the plan limit. Use to understand what is stored before browsing with list_memories, or to check remaining storage capacity. To show stats for a team workspac |
update | Update an existing memory by ID. Use mode replace (default) to patch fields, or append to extend content. Re-embeds only when content changes. The target workspace is always the one the memory itself belongs to (echoed in resolved_workspace); optionally pass workspace: <name> as a safety confirmatio |