com.memxus/memxus

com.memxus/memxus · v1.3.2

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

MCPremoteno credentialsFiles & storageDeveloper toolsKnowledge & docs

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 9 tools, protocol 2024-11-05 · checked 2026-10-17

Test & rating

B 88/100

What it does: 9 tools · 6 read, 3 write (incl. delete/pay) · Developer tools, Files & storage, AI & LLM

Test call list_memories: needs a key: HTTP 401 (967 ms)

How the rating is made

Answers without login: +30
Speed of first answer: +10
Lists tools: +10
Tool descriptions: +15
Parameter descriptions: +10
Read/write annotations: +5
Safe test call: +8
More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL

https://mcp.memxus.com/mcp

Tools

9 tools listed at last check

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

Badge

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/com.memxus/memxus.svg)](https://clawy.uk/mcp/s/com.memxus/memxus)

Repository