> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bloom.diy/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Bloom MCP to an AI client

> Connect ChatGPT, Codex, Claude, Cursor, or another MCP client to Bloom's hosted server.

Bloom's hosted MCP server is available at:

```text theme={null}
https://api.bloom.diy/mcp
```

It uses **Streamable HTTP** and browser-based **OAuth**. Add that URL as a remote MCP server in your
client, then sign in to Bloom and approve the connection in your browser. You do not need to create
or copy an API token. Bloom's OAuth discovery endpoints tell compatible clients how to authenticate.

Before sign-in, clients can discover the OAuth flow, but cannot initialize MCP or see the tool list.
Your account needs Canvas early access to approve an MCP connection or use MCP tools. If that access
is removed later, existing connections stop working. Each tool also respects your project permissions.

## Before you start

You need:

* A Bloom account with Canvas early access and access to at least one project.
* An MCP client that supports remote Streamable HTTP servers and OAuth.
* Permission to open a browser and approve the Bloom connection.

The consent screen shows the access Bloom MCP is requesting. Review it before approving. Your client
stores and refreshes its own OAuth session; it never needs your Bloom password. For a client without
specific instructions below, choose **Streamable HTTP** or **remote MCP**, enter the URL above, and
follow the client's OAuth sign-in flow.

## ChatGPT

In ChatGPT settings, add a custom MCP connector with the server URL above, then connect your Bloom
account through the browser OAuth flow. Availability of custom connectors depends on your ChatGPT
plan and workspace settings. A workspace administrator may need to enable or add the connector.

## Cursor

Add Bloom to your global Cursor MCP configuration at `~/.cursor/mcp.json`, or to a project's
`.cursor/mcp.json`. If the file already contains other servers, add the `Bloom` entry to its existing
`mcpServers` object instead of replacing the file.

```json theme={null}
{
    "mcpServers": {
        "Bloom": {
            "type": "http",
            "url": "https://api.bloom.diy/mcp"
        }
    }
}
```

<Steps>
  <Step title="Open Bloom in Cursor">
    Open **Cursor Settings → Tools & MCP**, then find **Bloom**.
  </Step>

  <Step title="Connect your account">
    Select **Connect** or **Authenticate**. Sign in to Bloom in the browser, review the
    requested access, and approve it.
  </Step>

  <Step title="Return to Cursor">
    Bloom should appear as connected, and its tools should be available to Agent.
  </Step>
</Steps>

If you use Cursor Agent from the terminal, start authentication after saving the configuration:

```bash theme={null}
cursor-agent mcp login Bloom
```

## Claude

### Claude and Claude Desktop

Remote custom connectors are available on Claude plans that support them.

<Steps>
  <Step title="Add the connector">
    Open **Settings → Connectors**, select **Add custom connector**, and name it `Bloom`.
  </Step>

  <Step title="Enter the server URL">
    Enter `https://api.bloom.diy/mcp` as the remote MCP server URL, then select **Add**.
  </Step>

  <Step title="Connect your account">
    In a chat, open **Search and tools**, find Bloom, and select **Connect**. Sign in to Bloom
    in the browser, review the requested access, and approve it.
  </Step>
</Steps>

On Team or Enterprise plans, an owner may need to add Bloom under **Organization connectors** before
individual members can connect it. Claude Desktop remote connectors must be added through
**Settings → Connectors**. Adding this hosted URL to `claude_desktop_config.json` does not configure a
remote connector.

### Claude Code

Run:

```bash theme={null}
claude mcp add --transport http --scope user Bloom https://api.bloom.diy/mcp
```

Start Claude Code, enter `/mcp`, select **Bloom**, and follow the browser authentication flow. Verify
the saved configuration with:

```bash theme={null}
claude mcp get Bloom
```

Use `--scope project` instead of `--scope user` only if you intentionally want to share the server
definition through the project's `.mcp.json`. Authentication remains personal to each user.

## Codex

Run these commands once:

```bash theme={null}
codex mcp add Bloom --url https://api.bloom.diy/mcp
codex mcp login Bloom
```

Complete Bloom sign-in and consent in the browser, then start a new Codex task. The Codex CLI and
desktop app use the same MCP configuration. Verify it with:

```bash theme={null}
codex mcp get Bloom
```

If your organization manages Codex configuration centrally, ask an administrator to add the same URL
as a Streamable HTTP MCP server. Each user still completes their own Bloom OAuth connection.

## Confirm the connection

Open a new chat or task and ask:

> Use Bloom's `whoami` tool to tell me which Bloom account is connected. Do not change anything.

A working connection calls Bloom's `whoami` tool and identifies your Bloom account. Your client may
ask you to approve the tool call. Bloom does not expose a `list_projects` MCP tool.

Before allowing an edit, check the tool name and arguments shown by your client. Read-only tools are
marked as read-only. Editing canvas content, deleting frames, and other writes can change project data.

## Disconnect or reconnect

You can disconnect Bloom from your client's MCP or connector settings. To revoke the server-side
session too, remove Bloom from your connected applications in Bloom account settings. The next tool
call should require a new connection.

If Bloom remains disconnected after you approve access:

1. Confirm the URL is exactly `https://api.bloom.diy/mcp`.
2. Remove any older Bloom MCP entry that uses a personal access token or `mcp-remote`.
3. Disconnect or clear Bloom authentication in the client, then connect again.
4. Restart the client or open a new chat so it reloads its MCP configuration.

Never paste access tokens or authorization codes into chat, configuration files, support messages, or
issue reports.