Bloom MCP server · build blueprint
Not ready to ship.
3 things stand between this server and anyone but its author using it: a decision, a test run, and a second person to sign in.
01Nobody else can reach it
It runs on a local development worker. There is no address to give anyone, and no production installation has been verified.
Decided 25 Sept: plan a guarded deploy. A staging plan goes to the account holder before anything goes live.
02Two people sharing it is unproven
Two service users, two identities each, two businesses each — never verified against live Bloom. Fixture tests are not evidence for this.
Decided 25 Sept: plan a live two-user test. The account holder supplies the second Bloom login.
03Everyone would hand over their Bloom password
Bloom publishes no delegated sign-in we can use. The account holder has decided not to ask, and to keep this server's own login and approval pages. Each additional person types their Bloom email and password into this server.
Decided 25 Sept: not contacting Bloom. Instead a second person's sign-in is tested separately against the deployed server, and a refused sign-in says plainly that it was refused without guessing at a cause.
263 of 594 checklist rows ticked · 331 still open
The bar counts checklist rows, which is the most representative figure this repository holds — it is not a readiness score. Until the first of the three is closed, nobody else can reach this server at all. The other two mean that even once they can, letting them would not yet be safe. The rows also do not close evenly: most of what remains needs a live run against a real Bloom account, a deployment decision, or an owner decision.
Every blueprint capability, scored against the evidence in the repository. Verified means a tracker row ticked against a named artefact. The coral dot means at least one operation in that capability was proven live — not the whole capability. Fully proven and partly proven are always shown separately.
Updated 1 October 2026103 top-level capabilities594 checklist rows174 registered MCP tools492 API catalogue entries244 operations fully proven8 partly proven
Top-level capabilities only.
Built is not proven. A journal proves the action that ran, not the whole operation.
252 operations have at least one action proven. That figure is the two headline numbers added; it is not itself a measure of finished work.
Registry v1 0b0effca01a4, schema v1 — the binding set these figures were derived from.
updateIntegration is additionally blocked on a hosted OAuth redirect that no approval unblocks.
Sending a message is not among these. bloom_message_write is a controlled test harness: the recipient is a single address compiled into mcp-server/src/message-send-policy.ts and the schema refuses any other, the adapter has never run against Bloom, and available reads cannot prove acceptance or delivery. Nothing on this page claims the server can email a client.
Each square is one capability. Dots mark live proof.
The “What users need” view follows the journey through the MCP, from connecting Bloom to shipping it. The “How we build it” view groups the same capabilities by engineering workstream.
Capabilities with at least one operation proven by a live run. The list is kept by hand in the generator, not derived from the tracker, and most of these rows are still in progress. Runs used synthetic records on the owner’s own businesses; most were deleted afterwards and confirmed gone, but not all — three remain stranded, a CDN derivative still answers after its source was deleted, and a bloomer-qa project tag remains in the account vocabulary — all recorded against ACCEPT-11. One of the three cannot even be checked: Bloom returns HTTP 500 for the archived-form filter in both directions, proven across two businesses, so whether that record still exists is unknowable from here. A live tag covers the run that was made, not every action the row names.
Capabilities the tracker records as not started: no adapter, no implementation. Everything not listed here is at least partly built, blocked upstream, or owner-blocked — and partly built is not the same as working.