# ClariLayer MCP server

> Save selected decisions and definitions from past AI conversations and recall them across projects and sessions.

- Listing: https://mcp.tc/i/clarilayer
- Connect: use the server's own URL `https://app.clarilayer.com/api/mcp/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: ClariLayer
- Homepage: <https://app.clarilayer.com/>

## About

ClariLayer is a memory layer for AI work. It turns selected past conversations into saved context, such as project decisions or analytics definitions, that an assistant can recall in later sessions with its source and scope visible. The vendor describes recall, correct, forget and optional bounded capture.

The hosted endpoint uses streamable HTTP. Users connect from clients such as Claude Code, Cursor, Codex and claude.ai through a guided setup. Access uses OAuth where the client supports it, or a key stored locally by the client as a fallback. A free plan is offered.

## What it can do

- Recall saved decisions and context in new AI sessions
- Correct saved memory entries
- Forget stored memory
- Optional bounded capture of context from conversations
- Show the source and scope of recalled memory

## Example prompts

- "Recall what we decided about the launch page."
- "Save this decision: open with the product demo."
- "Which definition of active customers did I teach you?"
- "Forget the memory about the old billing rule."

## Install

### Claude Code

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

```bash
claude mcp add --transport http clarilayer https://app.clarilayer.com/api/mcp/mcp
```

2. Start Claude Code, type `/mcp`, pick **clarilayer** and choose **Authenticate**. A browser window opens for the ClariLayer 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 **ClariLayer** and paste this URL:

```url
https://app.clarilayer.com/api/mcp/mcp
```

3. Click **Add**, then **Connect**, and sign in when ClariLayer 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=ClariLayer&connectorUrl=https%3A%2F%2Fapp.clarilayer.com%2Fapi%2Fmcp%2Fmcp>) (opens connector settings)

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

3. Click **Connect** and sign in when ClariLayer 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://app.clarilayer.com/api/mcp/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to ClariLayer 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=clarilayer&config=eyJ1cmwiOiJodHRwczovL2FwcC5jbGFyaWxheWVyLmNvbS9hcGkvbWNwL21jcCJ9>) (opens Cursor)

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

`mcp.json`:

```json
{
  "mcpServers": {
    "clarilayer": {
      "url": "https://app.clarilayer.com/api/mcp/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=clarilayer&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapp.clarilayer.com%2Fapi%2Fmcp%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

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

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

`.vscode/mcp.json`:

```json
{
  "servers": {
    "clarilayer": {
      "type": "http",
      "url": "https://app.clarilayer.com/api/mcp/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": {
    "clarilayer": {
      "serverUrl": "https://app.clarilayer.com/api/mcp/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 clarilayer --url https://app.clarilayer.com/api/mcp/mcp
codex mcp login clarilayer
```

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

`config.toml`:

```toml
[mcp_servers.clarilayer]
url = "https://app.clarilayer.com/api/mcp/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http clarilayer https://app.clarilayer.com/api/mcp/mcp
```

Then, inside Gemini CLI, run `/mcp auth clarilayer` 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": {
    "clarilayer": {
      "type": "http",
      "url": "https://app.clarilayer.com/api/mcp/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://app.clarilayer.com/api/mcp/mcp`.

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-03
- Updated: 2026-11-03

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