- Sign in with Bloom (OAuth) — the default. A browser sign-in on first connect, with nothing to set up in advance. Recommended; per-client setup is below.
- API key — a static
bloom_sk_...key in a request header. The better fit when there’s no browser to sign in with, when a team shares one setup, or when you’re running headless — CI, a server, an automation host.
Sign in with Bloom
The default path — nothing to create ahead of time; you sign in when the client first connects.Claude
Works in the Claude desktop app and on claude.ai (Pro, Max, Team, and Enterprise).1
Open the connector settings
Go to Settings → Connectors and click Add custom connector.
2
Add the server
Paste the server URL and click Connect.
3
Sign in
Sign in with Bloom when the browser opens.
Claude Code
1
Add the server
--scope user to make it available across all your projects.2
Sign in
Run
/mcp inside Claude Code and sign in with Bloom when prompted.Cursor
1
Add the server
Add Bloom to
~/.cursor/mcp.json (global) or .cursor/mcp.json (project):2
Sign in
Sign in with Bloom when Cursor prompts.
VS Code
1
Add the server
Add Bloom to
.vscode/mcp.json:2
Sign in
Sign in with Bloom when VS Code prompts.
ChatGPT
1
Enable Developer mode
Turn on Developer mode under Settings → Apps & Connectors → Advanced.
2
Add the server
Add a connector with the server URL.
3
Sign in
Choose OAuth and sign in with Bloom.
OpenClaw
1
Add the server
2
Sign in
Run
openclaw mcp login bloom and complete the browser sign-in.Hermes Agent
1
Add the server
2
Sign in
Complete the browser sign-in, then verify with
hermes mcp test bloom.API keys
Create a key from your account settings and treat it like a password: reference it from an environment variable or your client’s secret store rather than hard-coding it, and never commit it or expose it client-side. Bloom keys look likebloom_sk_....
The key goes in a request header, in either of two forms — use whichever your client expects:
Not every client can carry a static key. Claude Code, Cursor, VS Code, OpenClaw, and Hermes support custom headers, and Claude Desktop can do so through a bridge (below). claude.ai and ChatGPT are sign-in only — use OAuth for those (see Sign in with Bloom).
Claude Code
Pass the key as a header when you add the server:--scope user to make the server available across all your projects.
Cursor
Add aheaders block to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
"x-api-key": "${env:BLOOM_API_KEY}".
VS Code
Use aninputs block in .vscode/mcp.json so VS Code prompts for the key once and stores it securely, instead of hard-coding it:
Claude
Claude’s connector UI is sign-in only. To use a key with the Claude desktop app, add Bloom toclaude_desktop_config.json (Settings → Developer → Edit Config) through the mcp-remote bridge, which connects the remote server through a local process:
OpenClaw
Pass the key as a header when you add the server:~/.openclaw/openclaw.json:
Hermes Agent
Add the server, and paste your key when Hermes prompts for authentication:bloom_sk_... key. Verify with hermes mcp test bloom.