bloomgrowth-mcp

Bloom Growth MCP server — exposes the Bloom Growth REST API (EOS/Traction-style meetings, rocks, scorecards, to-dos, and org-chart management) as MCP tools.

Naming note: app.mspbots.ai calls this integration "Bloom Growth" (sys_integration.subject_code = BLOOMGROWTH). MSPbots' own integration only calls one endpoint (GET /api/v1/scorecard/user/mine). Per a 2026-08-04 scope decision, this build was trimmed from an original full-API 123-tool build down to 10 tools covering that endpoint's category (scorecard) plus measurables (the resource scorecards are a computed view over) — see Tool List below for the exact rationale.

Overview

This server implements the Model Context Protocol (Streamable HTTP/SSE transport) and wraps the Bloom Growth REST API v1 — 10 tools across 2 files / 2 API tag categories (scorecard, measurables), including write operations (create/update). It follows the MSPbots Vendor MCP Service SOP: stateless, no stored credentials, per-request header authentication.

The underlying API authenticates via OAuth2 Resource-Owner-Password-Credentials grant: POST https://app.bloomgrowth.com/Token with form-urlencoded body grant_type=password&userName=<email>&password=<password>, returning a bearer access token valid for ~2 weeks. This server does not perform that token exchange itself — it receives an already-obtained bearer access token per request; the caller (Agent Platform / upstream gateway) obtains and refreshes the token from the account's email/password, and only the resulting token reaches this server (same pattern as bizratings-mcp, connectwise-asio-mcp, and acronis-mcp in this MCP fleet).

Related MCP server: Workboard MCP

Quick Start

Docker (recommended)

docker compose up --build

The server starts on http://localhost:8080.

Local (uv)

uv sync
python -m bloomgrowth_mcp

Health Check

curl http://localhost:8080/health
# {"status": "ok"}

No token is required for the health endpoint.

授权参数说明 (Authentication)

Every request to /mcp must include the following HTTP header:

Missing the header returns 401 Unauthorized.

Environment Variables

MCP Endpoint

POST http://localhost:8080/mcp

Connect your MCP client with:

• Transport: http (Streamable HTTP / SSE)

• Headers: X-BloomGrowth-Token: <access_token> (required)

Tool List

10 tools, trimmed down from an original 123-tool full-API build (2026-08-04). MSPbots' own integration only calls one endpoint (GET /api/v1/scorecard/user/mine -> bloomgrowth_get_my_scorecard); per the "actual usage + same-category core CRUD" scope decision, this build keeps the scorecard category plus measurables (the underlying resource a scorecard is a computed view over — Bloom Growth scorecards are tables of measurables and their weekly values, so there is no separate "scorecard" CRUD to speak of). Everything else from the original 123-tool build (L10 Meetings, Headlines, Issues, Milestones, Process, Rocks, Role, Seats, Teams, Todos, Users, Misc — 12 categories, ~113 tools) was removed as unused by MSPbots and out of scope for this server's purpose. If a removed category is needed later, the vendor's own OpenAPI/Swagger spec (linked below) still documents its exact operations and they can be re-added the same way the kept tools were generated.

Measurables (7)

Scorecard (3)

测试示例 (Test Example)

Get the calling user's scorecard (matches MSPbots' existing integration usage):

{
  "method": "tools/call",
  "params": { "name": "bloomgrowth_get_my_scorecard", "arguments": {} }
}

Equivalent curl against the running server (streamable HTTP MCP endpoint):

curl -X POST http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "X-BloomGrowth-Token: <access_token>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "bloomgrowth_get_my_scorecard", "arguments": {} }
  }'

A parameterized call:

{
  "method": "tools/call",
  "params": {
    "name": "bloomgrowth_get_rock",
    "arguments": { "rock_id": 12345 }
  }
}

API Reference

• Swagger UI: https://dev-api.bloomgrowth.com/swagger/index.html

• OpenAPI spec (v1): https://dev-api.bloomgrowth.com/swagger/v1/swagger.json

• Token endpoint guide: shown on the Swagger UI page ("Generating a Token")

Known Gaps / Implementation Notes

• Trimmed from 123 to 10 tools on 2026-08-04. The original build covered the full public API across 18 tag categories per an earlier scope decision. A later scope decision cut this back to MSPbots' actually-used category (scorecard) plus measurables — see the Naming note and Tool List above for the exact rationale. If a removed category (L10 Meetings, Headlines, Issues, Milestones, Process, Rocks, Role, Seats, Teams, Todos, Users, Misc — ~113 tools total) is needed later, the vendor's OpenAPI/ Swagger spec (linked below) still documents its exact operations and they can be re-added the same way the kept tools were generated.

• Not yet tested against a live Bloom Growth account — only protocol-level verification (health check, 401 on missing token, tools/list returning all 10 tools, and JSON-schema validation) has been done so far.

• bloomgrowth_create_measurable and bloomgrowth_update_measurable expose their request bodies as named optional parameters rather than a generic body: dict, since the Bloom Growth schemas are shallow (no deep nesting) — this differs from the body/extra_params dict pattern used in larger/deeper-nested vendor APIs elsewhere in this MCP fleet.

• Endpoints whose exact request/response shape wasn't fully described by the OpenAPI spec (a few return simple 200 with no documented body) are implemented to match the spec's declared parameters; verify against a real account before relying on edge-case behavior.