MCP
Connect Blue to AI assistants like Claude, Cursor, and other MCP-compatible clients.
The Model Context Protocol (MCP) is an open standard that lets AI assistants interact with external tools and data. Blue’s MCP server allows AI assistants to read and write data in your Blue workspaces — listing records, creating tasks, managing checklists, and more.
With Blue’s MCP integration, you can ask your AI assistant things like “Show me all records due this week”, “Create a new record in the Sales workspace”, or “Add a checklist to that record with three items” — and it will do it directly in Blue.
Endpoint
https://mcp.blue.cc/mcpBlue uses the Streamable HTTP transport (the current MCP standard). It works directly with Claude Code, Cursor, Windsurf, and other clients that support remote MCP servers. Claude Desktop only speaks local stdio transport, so its setup below uses the mcp-remote bridge to connect.
Authentication
Blue’s MCP server uses Personal Access Tokens (PATs) for authentication. You’ll need three headers on every request:
| Header | Description |
|---|---|
x-bloo-token-id | Your Personal Access Token ID |
x-bloo-token-secret | Your Personal Access Token secret |
x-bloo-company-id | Your organisation slug or ID |
Generating a Personal Access Token
- Log in to Blue
- Go to Account → API
- Click Create Token
- Copy the Token ID and Token Secret — you’ll need both
Your token secret is only shown once when created. Store it securely. If you lose it, you’ll need to create a new token.
Setup
Claude Desktop
Add the following to your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"blue": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.blue.cc/mcp",
"--header", "x-bloo-token-id:YOUR_TOKEN_ID",
"--header", "x-bloo-token-secret:YOUR_TOKEN_SECRET",
"--header", "x-bloo-company-id:YOUR_COMPANY_SLUG"
]
}
}
}Restart Claude Desktop after saving. This uses mcp-remote to bridge the remote MCP server to Claude Desktop’s local transport.
mcp-remote is a Node.js package and needs Node 18+ (Node 20 LTS or newer recommended). If npx on your system resolves to an older Node, the server will fail to start with a SyntaxError. Either upgrade Node, or replace "command": "npx" with the absolute path to a newer Node’s npx (e.g. /Users/you/.nvm/versions/node/v22.21.1/bin/npx).
Claude Code
claude mcp add \
-t http \
-H "x-bloo-token-id: YOUR_TOKEN_ID" \
-H "x-bloo-token-secret: YOUR_TOKEN_SECRET" \
-H "x-bloo-company-id: YOUR_COMPANY_SLUG" \
-- blue https://mcp.blue.cc/mcpRestart Claude Code after adding. To verify: claude mcp list. To remove: claude mcp remove blue.
Cursor
Add the following to .cursor/mcp.json in your project directory (or ~/.cursor/mcp.json for global access):
{
"mcpServers": {
"blue": {
"url": "https://mcp.blue.cc/mcp",
"headers": {
"x-bloo-token-id": "YOUR_TOKEN_ID",
"x-bloo-token-secret": "YOUR_TOKEN_SECRET",
"x-bloo-company-id": "YOUR_COMPANY_SLUG"
}
}
}
}Or via the UI: Settings → Tools & MCP → Add Server.
Windsurf
Add the following to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"blue": {
"serverUrl": "https://mcp.blue.cc/mcp",
"headers": {
"x-bloo-token-id": "YOUR_TOKEN_ID",
"x-bloo-token-secret": "YOUR_TOKEN_SECRET",
"x-bloo-company-id": "YOUR_COMPANY_SLUG"
}
}
}
}Or via the UI: Plugins → Manage plugins → View raw config.
Other MCP Clients
Any MCP-compatible client that supports the Streamable HTTP transport can connect to Blue. Configure it with:
- URL:
https://mcp.blue.cc/mcp - Transport: Streamable HTTP
- Headers: The three authentication headers listed above
Available Tools
Blue’s MCP server provides 21 tools organised into read and write operations.
Read Tools
| Tool | Description | Workspace ID |
|---|---|---|
list-workspaces | List all workspaces in your organisation | No |
list-records | List records with filtering by workspace, list, status, assignees, and tags | Optional |
get-record | Get full record details including checklists, custom fields, tags, and assignees | No |
count-records | Count records matching a filter | Optional |
list-lists | List all lists (columns/statuses) in a workspace | Yes |
list-tags | List tags in a workspace | Yes |
list-users | List users in your organisation | No |
list-custom-fields | List custom fields and their options in a workspace | Yes |
Write Tools
| Tool | Description | Workspace ID |
|---|---|---|
create-record | Create a new record with title, description, assignees, and tags | Yes |
update-record | Update a record’s title, description, status, dates, or colour | Yes |
move-record | Move a record to a different list | Yes |
delete-record | Permanently delete a record | Yes |
create-workspace | Create a new workspace in the organisation | No |
create-list | Create a new list (column/status) in a workspace | Yes |
create-tag | Create a new tag in a workspace | Yes |
set-tags-on-record | Set tags on a record | Yes |
set-custom-field-value | Set a custom field value on a record | Yes |
create-checklist | Add a checklist to a record | No |
create-checklist-item | Add an item to a checklist | No |
update-checklist-item | Update or complete a checklist item | No |
add-comment | Add a comment to a record | No |
Workspace Scoping
Blue’s data is organised as Organisation → Workspaces → Lists → Records.
- Your organisation is set globally via the
x-bloo-company-idheader when you configure the MCP connection - Workspace is passed as a parameter on tools that need it — most write tools and several read tools require a workspace ID
- Read-only tools like
get-recordonly need the entity ID — the workspace is resolved automatically
This means your AI assistant can work across multiple workspaces in a single conversation.
Examples
Here are some things you can ask your AI assistant once Blue is connected:
Reading data:
- “List my workspaces”
- “Show me the open records in the Sales workspace”
- “Get the details of record [ID]”
- “How many records are overdue?”
- “What custom fields are set up in the Onboarding workspace?”
Writing data:
- “Create a record called ‘Follow up with client’ in the Sales workspace”
- “Mark that record as done”
- “Move it to the Completed list”
- “Add a checklist with three items: send proposal, schedule call, get signature”
- “Tag it as ‘urgent’”
- “Add a comment: ‘Discussed in today’s meeting, needs follow-up by Friday’”
Rate Limits
MCP requests are rate-limited to 60 requests per minute per user. This is more than sufficient for interactive AI assistant usage.
Security
- All requests are authenticated with your Personal Access Token
- Tokens respect the same permissions as your user account — MCP tools can only access data you have access to
- All communication uses HTTPS with TLS encryption
- Blue’s MCP server runs on the same infrastructure as the main API with the same security controls