Memxus Remote MCP Server

Memxus — AI Context Engine

One context engine. Every AI.

Builds persistent context from GitHub, Notion, and your saved decisions — delivered to Claude, Cursor, ChatGPT, VS Code, and any MCP-compatible client.

Glama MCP Connector License: AGPL-3.0 Node 20+ Railway MCP Registry v1.2.0

Website · Docs · Connect your first AI · Glama Inspector

---

Watch the Memxus demo on YouTube

▶️ Watch the demo on YouTube · Demo page

---

The problem

Every AI tool starts from zero.

Claude doesn't know what Cursor knows. Cursor doesn't know what ChatGPT knows.
Your stack, project decisions, coding preferences and workflow context get repeated again and again.

Memxus fixes that with a shared context engine for your AI tools — not another chatbot, but persistent context built from your real work sources.

Sync GitHub once → every AI knows your stack. Save a decision in Claude → recall it in Cursor → reuse it in ChatGPT.

---

What is Memxus?

Memxus is the AI context engine — a hosted remote MCP server that automatically builds and delivers persistent project context to every AI client you use.

GitHub repos, Notion docs, commits, PRs, issues, and saved decisions become searchable context. GitHub and Notion connectors are live in production (v1.2.0) — connect from the dashboard or directly from chat via MCP connector tools.

No local setup.
No file syncing.
No copy-pasting context between tools.

Connect once with OAuth and your context becomes portable across your entire AI workflow.

---

Why developers use Memxus

• 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
  GitHub[GitHub repos] --> Sync[Memxus sync]
  Notion[Notion pages] --> Sync
  Manual[Manual remember] --> Sync
  Sync --> Collection["project:slug"]
  Collection --> Tools["recall / get_context"]
  Tools --> Clients[Claude Cursor ChatGPT]

Context Engine connector tools (4): connect GitHub/Notion from chat via MCP. Production ships a 13-tool public manifest (9 core + 4 connect) with skill routing deferred.

---

Connect in 30 seconds

URL:       https://mcp.memxus.com/mcp
Auth:      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.0 — 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.0

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   ┘                                              │
                                                            │ pgvector
MCP 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-server
2. Client  →  GET  /oauth/authorize  →  redirect to dashboard login
3. User signs in (Google) in the dashboard
4. Client  →  POST /oauth/token  (PKCE)  →  aimem_* bearer token
5. 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 install
npm run dev       # tsx watch
npm 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 install
npm run dev        # tsx watch
npm run lint       # ESLint
npm run typecheck  # tsc --noEmit
npm 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.0

---

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 committed
git log --all --full-history -- .env .env.local .env.production

# 2. Check for .env* files added in history
git 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 keys
git log --all -p --follow -S "service_role" -- . | head -100
git 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 Server
Copyright (C) 2026 Gabriel Pitrella - Memxus