memxus-remote-mcp

# Memxus — AI Context Engine

**One context engine. Every AI.**

Save what matters once — recall it in Claude, Cursor, ChatGPT, Gemini, and any MCP client. Not generic memory: your real decisions, preferences and work context, portable across every AI. Multiply your productivity by giving your AI the right context — without repeating yourself.

[Glama MCP Connector](https://glama.ai/mcp/connectors/com.memxus/memxus)
[License: AGPL-3.0](LICENSE)
[Node 20+](https://nodejs.org)
[Railway](https://railway.app)
[MCP](https://modelcontextprotocol.io)
[Registry v1.2.1](https://registry.modelcontextprotocol.io)

[Website](https://memxus.com) · [Docs](https://memxus.com/docs/mcp) · [Connect your first AI](https://memxus.com/install) · [Glama Inspector](https://glama.ai/mcp/connectors/com.memxus/memxus)

---

[Watch the Memxus demo on YouTube](https://www.youtube.com/watch?v=Tg7BVuEXFm0)

▶️ **[Watch the demo on YouTube](https://www.youtube.com/watch?v=Tg7BVuEXFm0)** · [Demo page](https://www.memxus.com/demo)

---

<p align="center">
  <img src="docs/assets/memxus-flow.svg" alt="Save context from anywhere → one Memxus context engine → recall it in any AI → you stay in control" width="820">
</p>

<p align="center">
  <img src="docs/assets/memxus-code.svg" alt="remember a decision in Claude, recall it later in Cursor, get the exact answer back" width="680">
</p>

---

## 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, and not generic memory. The fix is simple: save something once, recall it in any AI. Connect, save, done — it's instantly available everywhere. Sync your full stack (repos, docs, decisions) later, only if you want more depth.

> Save a decision in Claude → recall it in Cursor → reuse it in ChatGPT. Want deeper context? Sync your GitHub and Notion too — optional, whenever you're ready.

---

## What is Memxus?

Memxus is the **AI context engine** — a hosted remote MCP server for your AI clients. The core gesture is dead simple: `remember` to save (a decision, a preference, a note), `recall` to bring it back in any AI. Connect once with OAuth and your context is portable across your entire AI workflow — no local setup, no file syncing, no copy-pasting between tools.

Want more? Sync real work sources — GitHub repos, Notion docs, commits, PRs, issues — and they become searchable context too. **GitHub and Notion connectors are live in production (v1.2.0).** Skill routing suggests official AI skills matched to your stack. But this is the optional deep layer — you get value from the first `save`.

---

## 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**


| Source     | Content indexed into context                     |
| ---------- | ------------------------------------------------ |
| **GitHub** | Repos, READMEs, commits, pull requests, issues   |
| **Notion** | Selected workspace pages and docs                |
| **Manual** | Decisions, preferences, and notes via `remember` |


**How to connect**

1. **Dashboard** — [dashboard.memxus.com/integrations](https://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.

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

> **Optional — sync your whole stack:** GitHub repos, Notion pages, files, docs and decisions become recallable context too. But you don't have to: just `save` and it's instantly available everywhere.



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

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

### Cursor / VS Code

```json
{
  "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](REVIEWER.md) for OAuth and Bearer token setup.

---

## Supported platforms


| Platform                   | Integration                              | Status         |
| -------------------------- | ---------------------------------------- | -------------- |
| Claude Desktop / claude.ai | Remote MCP                               | ✅ Live         |
| Cursor                     | Remote MCP                               | ✅ Live         |
| VS Code / Copilot MCP      | Remote MCP                               | ✅ Live         |
| ChatGPT                    | Custom GPT / API                         | ✅ Live         |
| Gemini                     | MCP-compatible workflow                  | ✅ Live         |
| Telegram                   | Bot connector                            | ✅ Live         |
| **GitHub**                 | Repo sync (commits, PRs, issues, README) | ✅ Live         |
| **Notion**                 | Workspace page sync                      | ✅ Live         |
| Discord                    | Bot connector                            | 🔜 Coming soon |
| Slack                      | Bot connector                            | 🔜 Coming soon |
| Any MCP-compatible client  | Remote MCP                               | ✅ Live         |


---

## 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)


| Tool               | Description                                                                                |
| ------------------ | ------------------------------------------------------------------------------------------ |
| `remember`         | Save context — manual input, decisions, or notes; optional `project:<slug>` collection     |
| `recall`           | Semantic search across memories; GitHub/Notion synced content via `project:<slug>` 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:<slug>`                             |
| `forget`           | Delete a memory permanently                                                                |
| `memory_stats`     | Stats by type and collection                                                               |
| `update`           | Patch or append existing memory content, tags, or type                                     |


### Context Engine connector tools (4) — v1.2.1


| Tool                   | Description                                                        |
| ---------------------- | ------------------------------------------------------------------ |
| `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:<slug>` |
| `check_connect_status` | Poll connection status after `connect_source`                      |


Full tool reference: [memxus.com/docs/mcp](https://memxus.com/docs/mcp) · Marketplace reviewers: [REVIEWER.md](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