Memxus MCP Server

Multi-platform AI memory. One save, recall everywhere—Claude, ChatGPT, Cursor, and more.

Remote serverstreamable-http

What is the Memxus MCP server?

Multi-platform AI memory. One save, recall everywhere—Claude, ChatGPT, Cursor, and more. The memxus mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Memxus brings Context Engineering to your entire AI workflow.

Memxus is a Context Engineering designed to multiply your productivity by giving every AI the right context.

  • Save once, recall in every AI — — stop repeating your stack, decisions and preferences across Claude, Cursor and ChatGPT
  • Ask once — — no more hunting through 5 tools to remember why you chose X
  • Keep project architecture and stack context available across Claude, Cursor, and ChatGPT
  • Sync GitHub and Notion into unified project collections — one context per repo
  • Stop pasting the same context into every new AI session
  • Share team context across agents and workflows

Its toolset

Everything the assistant can do here goes through one of these:

  • remember — Save context — manual input, decisions, or notes; optional project: collection
  • recall — Semantic search across memories; GitHub/Notion synced content via project: or tags
  • get_context — Formatted context block from GitHub, Notion, and saved decisions for agent prompts
  • list_memories — Browse memories by collection, tags, type, or visibility
  • get_memory — Retrieve full content and metadata by memory ID
  • list_collections — List scopes; GitHub/Notion syncs appear under project:
  • forget — Delete a memory permanently
  • memory_stats — Stats by type and collection
  • update — Patch or append existing memory content, tags, or type
  • connect_source — Start GitHub App install or Notion OAuth from chat
  • list_syncable_items — List repos or Notion pages available after connecting
  • set_sync_selection — Choose what to sync and trigger initial sync into project:

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 6 environment variables: MCP_PUBLIC_URL, DASHBOARD_URL, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, OAUTH_CLIENT_ID, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node 20+ - Supabase project (run supabase/migration.sql after the dashboard migration) - Railway account (or any Node host)

When to reach for it

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Memxus's toolset — remember, recall, get_context and 11 more — is a fair guide to whether it matches your workflow. It is maintained by com.memxus; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Memxus's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Memxus.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the memxus mcp server does with a few real requests.

Available tools

ToolWhat it does
rememberSave context — manual input, decisions, or notes; optional project:<slug> collection
recallSemantic search across memories; GitHub/Notion synced content via project:<slug> or tags
get_contextFormatted context block from GitHub, Notion, and saved decisions for agent prompts
list_memoriesBrowse memories by collection, tags, type, or visibility
get_memoryRetrieve full content and metadata by memory ID
list_collectionsList scopes; GitHub/Notion syncs appear under project:<slug>
forgetDelete a memory permanently
memory_statsStats by type and collection
updatePatch or append existing memory content, tags, or type
connect_sourceStart GitHub App install or Notion OAuth from chat
list_syncable_itemsList repos or Notion pages available after connecting
set_sync_selectionChoose what to sync and trigger initial sync into project:<slug>
check_connect_statusPoll connection status after connect_source
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the Memxus MCP server

{
  "mcpServers": {
    "memxus": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "MCP_PUBLIC_URL": "your-value",
        "DASHBOARD_URL": "your-value",
        "SUPABASE_URL": "your-value",
        "SUPABASE_SERVICE_ROLE_KEY": "your-value",
        "OAUTH_CLIENT_ID": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node 20+ - Supabase project (run supabase/migration.sql after the dashboard migration) - Railway account (or any Node host)
VariableDescriptionRequired
MCP_PUBLIC_URLEndpoint or connection string the server talks to.Yes
DASHBOARD_URLEndpoint or connection string the server talks to.Yes
SUPABASE_URLEndpoint or connection string the server talks to.Yes
SUPABASE_SERVICE_ROLE_KEYCredential the server authenticates with.Yes
OAUTH_CLIENT_IDConfiguration value read at startup.Optional
OPENAI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Memxus to remember.
  • Use Memxus to recall.
  • Use Memxus to get context.

Frequently asked questions

It connects Memxus to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (remember, recall, get_context, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Memxus directly.