# Memxus MCP server

> Save decisions and preferences once and recall that project context from Claude, Cursor, ChatGPT and other MCP clients.

- Listing: https://mcp.tc/i/memxus
- Connect: use the server's own URL `https://mcp.memxus.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [AI & Machine Learning](https://mcp.tc/c/ai-ml)
- Vendor: Memxus
- Homepage: <https://www.memxus.com/>
- Docs: <https://www.memxus.com/docs/mcp>
- Repository: <https://github.com/gpitrella/memxus-remote-mcp>

## About

Memxus is a persistent memory and context layer for AI assistants. You save decisions, preferences and project notes with a remember action, then recall them from any MCP-compatible client. It can also sync GitHub repositories (READMEs, commits, pull requests, issues) and selected Notion pages into per-project collections that are searchable alongside saved memories.

It runs as a hosted Streamable HTTP endpoint at https://mcp.memxus.com/mcp. Users sign in with OAuth 2.1; requested scopes cover reading, writing and deleting memories and reading and writing sources. No local install is needed. The source is AGPL-3.0 licensed.

## What it can do

- Save decisions, preferences and notes with remember
- Recall saved context from any connected AI client
- Fetch context for a task from a project collection
- Sync GitHub repos, commits, pull requests and issues
- Sync selected Notion pages into searchable context
- Connect GitHub and Notion sources from chat

## Tools (9)

- `remember`: Save important information to long-term memory.
- `recall`: Search long-term memory. (read-only)
- `get_context`: Builds a formatted context block for a topic from stored memories; use when the user asks to load or recall project context. (read-only)
- `list_memories`: List recent memories in reverse-chronological order (read-only). (read-only)
- `get_memory`: Retrieve the full content and metadata of one memory by its UUID. (read-only)
- `list_collections`: List memory collections (folders/scopes) for this user. (read-only)
- `forget`: Permanently delete one memory by UUID. (can modify or delete data)
- `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. (read-only)
- `update`: Update an existing memory by ID.

## Example prompts

- "Remember this in Memxus: we use Postgres with pgvector for semantic search."
- "Recall what we decided about the authentication approach."
- "Get context from Memxus for the billing service project."
- "Connect my GitHub repo to Memxus so its pull requests are searchable."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http memxus https://mcp.memxus.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **memxus** and choose **Authenticate**. A browser window opens for the Memxus sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Memxus** and paste this URL:

```url
https://mcp.memxus.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when Memxus asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Memxus&connectorUrl=https%3A%2F%2Fmcp.memxus.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.memxus.com/mcp` and click **Add**.

3. Click **Connect** and sign in when Memxus asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.memxus.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Memxus to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=memxus&config=eyJ1cmwiOiJodHRwczovL21jcC5tZW14dXMuY29tL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "memxus": {
      "url": "https://mcp.memxus.com/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=memxus&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.memxus.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"memxus","type":"http","url":"https://mcp.memxus.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "memxus": {
      "type": "http",
      "url": "https://mcp.memxus.com/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "memxus": {
      "serverUrl": "https://mcp.memxus.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add memxus --url https://mcp.memxus.com/mcp
codex mcp login memxus
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.memxus]
url = "https://mcp.memxus.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http memxus https://mcp.memxus.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth memxus` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.memxus.com/mcp`.

## Recent changes

- 2026-10-27 10:01 UTC: Tracking started: 9 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/memxus#history (Atom feed: https://mcp.tc/i/memxus/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.3.2
- MCP protocol version: 2024-11-05
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-05
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/memxus (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
