Memxus

Memxus — Context Engineering

One context layer. Every AI.

Multiply your productivity by giving every AI the right context.

Memxus brings Context Engineering to your entire AI workflow.

Save your real decisions, preferences and work context once. Find them in seconds and give Claude, Cursor, ChatGPT, Gemini or any MCP client the exact context required for each task.

No repeated explanations. No starting from zero. Better answers, faster.

Glama MCP Server License: AGPL-3.0 Node 20+ Railway MCP Registry v1.2.1

Website · Docs · Connect your first AI

Watch the Memxus demo on YouTube

▶️ Watch the demo on YouTube · Demo page

[Memxus Context Engineering hub: save from anywhere, recall in any AI, control via Dashboard]

[remember a decision in Claude, recall it later in Cursor, get the exact answer back]

The problem

AI tools are powerful, but their productivity drops when they do not have the right context.

Claude does not know what Cursor knows. Cursor does not know what ChatGPT knows. Your project decisions, preferences, architecture and workflow context get repeated across every tool and every new conversation.

That creates unnecessary work:

• Re-explaining the same information
• Searching across repositories, documents and conversations
• Correcting answers based on missing context
• Repeating technical and product decisions
• Starting every AI task from zero

Memxus solves this through Context Engineering.

Save what matters once, find it in seconds and give every AI the exact context it needs for the task.

The result is less repetition, less back-and-forth, faster execution and better answers across your entire AI workflow.

Save a decision in Claude → recall it in Cursor → reuse it in ChatGPT.
Need deeper context? Connect GitHub and Notion whenever you are ready.

What is Memxus?

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

It creates a shared context layer across Claude, Cursor, ChatGPT, Gemini and any MCP-compatible client.

The core workflow is simple:

• remember what matters
• recall it from any AI
• find relevant context in seconds
• give each AI the information it needs to produce a better answer

Connect once with OAuth and your decisions, preferences and work context become portable across your entire AI workflow — without local setup, repeated explanations or copying and pasting between tools.

For deeper context, Memxus can also connect to real work sources such as GitHub and Notion. Repositories, documentation, commits, pull requests, issues and selected workspace pages become searchable alongside your manually saved context.

GitHub and Notion connectors are live in production. This deeper synchronization is optional: Memxus delivers value from the first saved decision.

Save once. Find it fast. Give every AI the right context. Work faster.

Why developers use Memxus

• 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
• Build AI apps with persistent context through MCP or API

Real context from GitHub & Notion

Memxus reads your real work — not generic memory snippets. Synced content lands in a unified collection per project: project:<slug>.

What gets synced

How to connect

1. Dashboard — dashboard.memxus.com/integrations (GitHub App + Notion OAuth)
2. From chat (MCP) — connect_source → check_connect_status → list_syncable_items → set_sync_selection

How to use synced context

Call recall or get_context with collection=project:<slug> (or let semantic search find it). GitHub/Notion content is tagged and searchable alongside manual memories.

flowchart LR  Save["💾 Save — from any AI"] --> Memxus["🧠 Memxus — your persistent memory"] --> Recall["✨ Recall anywhere — Claude · Cursor · ChatGPT · Gemini"]

Start saving in one message

After you connect Memxus to any AI, paste a line like this — Memxus calls remember and your context is available everywhere:

Remember this in Memxus: we use Postgres + pgvector for semantic search.

No GitHub/Notion sync needed to start. Sync later when you want deeper project context.

Optional — sync your whole stack: GitHub repos, Notion pages, files, docs and decisions become recallable context too.

Context Engine connector tools (4): connect GitHub/Notion from chat via MCP. Production advertises the 9 core tools; the 4 connector tools are enabled per account, so a newly connected client sees the core 9.

Connect in 1 second, one click

URL:       https://mcp.memxus.com/mcpAuth:      OAuth 2.1 (handled automatically)Transport: Streamable HTTP

Claude Desktop (claude_desktop_config.json)

{  "mcpServers": {    "memxus": {      "url": "https://mcp.memxus.com/mcp",      "transport": "streamable-http"    }  }}

Cursor / VS Code

{  "mcp": {    "servers": {      "memxus": {        "url": "https://mcp.memxus.com/mcp",        "transport": "http"      }    }  }}

Or open directly in Glama Inspector →
[https://glama.ai/mcp/inspector?url=https://mcp.memxus.com/mcp](https://glama.ai/mcp/inspector?url=https://mcp.memxus.com/mcp)

For marketplace reviewers: see REVIEWER.md for OAuth and Bearer token setup.

Supported platforms

Available tools

Registry com.memxus/memxus v1.2.1 — 9 core tools always available, plus 4 connector tools for GitHub/Notion sync from chat.

Core tools (9)

Context Engine connector tools (4) — v1.2.1

Full tool reference: memxus.com/docs/mcp · Marketplace reviewers: REVIEWER.md

Architecture

GitHub App ──┐Notion OAuth ┼──► sync (API + connector tools) ──► Supabase  project:<slug>Manual MCP   ┘                                              │                                                            │ pgvectorMCP Client (Claude, Cursor, etc.)                           │        │                                                   │        │  POST /mcp   Bearer aimem_*                       │        ▼                                                   ▼  mcp.memxus.com  ← This repo (Railway) ──────────►  Supabase (Postgres + pgvector)        │        ▼  Dash-AIMemory (Dashboard + integrations)

Sync runs server-side via dashboard or MCP connector tools — no local files to manage.

Transport: Streamable HTTP (MCP 2.0)
Auth: OAuth 2.1 + PKCE + Dynamic Client Registration (RFC 9728)

Security

• OAuth 2.1 + PKCE — no passwords, no API keys to manage
• Encrypted at rest (AES-256)
• User-controlled memory — view, edit and delete anytime from the dashboard
• No local files or manual syncing
• Pre-publication secrets audit passed: 2026-06-17
• Memory is advisory context, not instruction authority — see TRUST-POLICY.md for what is read automatically, what requires an explicit write, and what the memory layer never does.

OAuth flow

1. Client  →  GET  /.well-known/oauth-authorization-server2. Client  →  GET  /oauth/authorize  →  redirect to dashboard login3. User signs in (Google) in the dashboard4. Client  →  POST /oauth/token  (PKCE)  →  aimem_* bearer token5. Client  →  POST /mcp  Authorization: Bearer aimem_*

Dynamic Client Registration is supported — clients register automatically on first connect.

Self-hosting

Prerequisites

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

Environment variables

cp .env.example .env

Run locally

npm installnpm run dev       # tsx watchnpm run build     # tsc → dist/npm start         # node dist/index.js

Deploy to Railway

Set all variables under Settings → Variables (never commit .env).
MCP_PUBLIC_URL = your Railway networking URL (no trailing /mcp).
Health check endpoint: /health (configured in [railway.toml](railway.toml)).

Note: Node 20 on Railway — Supabase Realtime needs the ws package (configured in src/lib/supabase.ts).
Optional: set RAILPACK_NODE_VERSION=22 for native WebSocket support.

Development

npm installnpm run dev        # tsx watchnpm run lint       # ESLintnpm run typecheck  # tsc --noEmitnpm run build      # compile → dist/npm start          # node dist/index.js

Marketplace reviewers: REVIEWER.md · MCP docs: memxus.com/docs/mcp · Registry: com.memxus/memxus v1.2.1

Releases

1. Add entries under ## [Unreleased] in [CHANGELOG.md](CHANGELOG.md)
2. Bump version in package.json, server.json, src/mcp/server.ts, and src/mcp/public-discovery.ts
3. Move the changelog section to ## [X.Y.Z] - YYYY-MM-DD
4. Commit, tag, and push:

git tag -a vX.Y.Z -m "Memxus MCP vX.Y.Z"git push origin vX.Y.Z

Pushing a v* tag triggers [.github/workflows/release.yml](.github/workflows/release.yml) — quality gate + GitHub Release with server.json attached.

Secrets audit

Run from the repo root before making the repository public.
Last audit: 2026-06-17 — PASSED

# 1. Verify .env was never committedgit log --all --full-history -- .env .env.local .env.production
# 2. Check for .env* files added in historygit log --all --oneline --diff-filter=A -- "*.env*"
# 3. Grep current tree for dangerous patterns (exclude .example)git grep -rn -E "(service_role|anon_key|sk-[a-zA-Z0-9]{20,}|aimem_[a-zA-Z0-9]+|eyJ[a-zA-Z0-9_-]{20,})" \  -- ":(exclude)*.example" ":(exclude)CHANGELOG*"
# 4. Search full git history for leaked keysgit log --all -p --follow -S "service_role" -- . | head -100git log --all -p --follow -S "SUPABASE_SERVICE_ROLE_KEY=" -- . | head -100

If commands 1 or 4 find real secrets, rotate keys immediately and run git filter-repo --path .env --invert-paths before publishing.

Roadmap

• GitHub connector (repo sync → project:<slug>)
• Notion connector (workspace page sync)
• MCP Registry v1.2.0 (com.memxus/memxus — AI Context Engine)
• Context Engine connector tools (GitHub/Notion from chat)
• Skill routing (deferred)
• Discord bot connector
• Slack bot connector
• Refresh tokens
• Multi-client OAuth UX
• npm publish

License

Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).

You can use, modify, and distribute this code freely. If you use it to run a network service (SaaS), you must publish your source code under the same license.

© 2026 Gabriel Pitrella · memxus.com

Memxus Remote MCP ServerCopyright (C) 2026 Gabriel Pitrella - Memxus