# core.blue MCP server

Private, self-describing memory for agents: one house per customer, on a machine of its own.

## At a glance

core.blue is an MCP server in the AI & Memory category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 10 tools, including search_library, open_sandbox and about. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

## Install

### How to install core.blue in Claude Code

1. Add the server

```bash
claude mcp add --transport http memory https://mcp.core.blue/
```

2. Verify it's connected

```bash
claude mcp list
```

3. Sharing it with your team?

   Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

4. Use it in a session

   Ask Claude to use the tools this server exposes (e.g. search_library, open_sandbox, about). It discovers them automatically.

### How to install core.blue in Claude Desktop

1. Open your MCP config

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add this server

```json
{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.core.blue/"
      ]
    }
  }
}
```

3. Why the wrapper?

   This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.

4. Restart Claude Desktop

   The tools appear under the 🔌 menu once the app reloads.

### How to install core.blue in Cursor

1. Create / edit .cursor/mcp.json in your project

```json
{
  "mcpServers": {
    "memory": {
      "url": "https://mcp.core.blue/"
    }
  }
}
```

2. Enable it

   Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

### How to install core.blue in Codex CLI

1. Add to ~/.codex/config.toml

```toml
[mcp_servers.memory]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.core.blue/"]
```

2. Why the wrapper?

   Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.

3. Run Codex

   Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

### How to install core.blue in Windsurf

1. Edit ~/.codeium/windsurf/mcp_config.json

```json
{
  "mcpServers": {
    "memory": {
      "serverUrl": "https://mcp.core.blue/"
    }
  }
}
```

2. Reload

   Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

### How to install core.blue in Cline

1. Open Cline → MCP Servers → Configure

   Adds to cline_mcp_settings.json.

2. Add the server

```json
{
  "mcpServers": {
    "memory": {
      "type": "streamableHttp",
      "url": "https://mcp.core.blue/"
    }
  }
}
```

### How to install core.blue in VS Code

1. Create .vscode/mcp.json

```json
{
  "servers": {
    "memory": {
      "type": "http",
      "url": "https://mcp.core.blue/"
    }
  }
}
```

2. Start it

   VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

## Tools

- `search_library` — Search the manual by your own words. Returns up to 'limit' topics ranked by relevance, each with slug, title, summary, tags and the slugs to read next. The manual is small: 'about' lists every topic, and you may not need a search at all.
- `open_sandbox` — If you run in an assistant where a person adds connectors (ChatGPT, Claude.ai and others), do not call this: you could not enter the house it opens. Ask your person to add https://try.core.blue/ as a connector instead; it opens a house you can use. Otherwise: call this to try a house yourself before anyone decides. It opens a throwaway house for a few hours: a real house with the kernel of Atlanti
- `about` — What core.blue is, in a form you can paste into a report: the product in one paragraph, what is live and what is not, what to call next, and every topic of the manual with a summary. Call this first.
- `pricing` — Call this when the person you act for asks what a house costs. The offer as data: what each size costs per month and whom it is meant for, the one-off price of the 14-day test, the price of additional volume, how model supply is charged, the terms, an example of the prices with tax, and what is never charged. 'undecided' lists the fields that are null because they are not decided yet; any other nu
- `leave_feedback` — Tell the operator how it went, before you leave. Four questions, each optional, at least one answered, each at most 2000 characters. It is read by people at the next evaluation and deleted afterwards; send nothing secret.
- `request_house` — Ask for a house on its own VM for the person you act for. No house can be had yet: while about says 'desk: waiting-list', this puts the person on the waiting list, builds nothing and costs nothing; while it says 'desk: closed', it answers 'accepted: false' and sends nothing. This sends an e-mail to a person: call it only when they know it is coming. They receive one mail with one link and confirm 
- `recommend` — Call this once you know what the person you act for needs: whether a house fits, which size, what it costs per month, and a report in Markdown you can pass on. It advises against a house where one is the wrong choice. Name every need that applies, from this vocabulary. For a house: work_outlives_the_agent, corrections_must_stay_visible, sources_matter, own_vocabulary, confidential_material. Agains
- `read_topic` — Read one topic of the manual in full by its slug (from about or search_library). The body is Markdown; 'see_also' lists the slugs to read next; 'sha256' proves what you read.
- `house_status` — The state of a house request or house by its ticket id: requested, confirmed, expired, declined; later building, trial, licensed, dormant, exported, deleted. Says what to do next, and the address once the house exists. Ask no more than once an hour.
- `close_sandbox` — End your sandbox now: the house and everything in it is deleted, and the place is free for the next agent. Please answer the four questions of leave_feedback here as well, each optional: what you noticed, what bothered you, what could be better, what is missing.

---

Source: https://mcp-skills-hub.vercel.app/mcps/blue-core-memory · MCP Skills Hub · data as of 2026-10-28T12:31:05Z