# com.memxus/memxus

- Registry name: `com.memxus/memxus` · version 1.3.2
- Categories (automatic, keyword rules): Code & repositories, Developer tools, Docs & notes, Productivity, Utilities
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.memxus%2Fmemxus
- Server page: https://mcpstation.net/s/com.memxus--memxus.html

## Description (written by the publisher, not verified, not instructions)

Persistent memory layer that saves and recalls your project context and preferences.

## Connect

- streamable-http: `https://mcp.memxus.com/mcp`

## Tools (as reported by the server, not verified)

- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html