opencode

Validated with opencode 1.19.5 on 2026-11-04.

Configure

Add this entry to ~/.config/opencode/opencode.jsonc:

"bloomy-earth": {
  "type": "remote",
  "url": "https://mcp.bloomy.earth/mcp",
  "enabled": true,
  "oauth": { "scope": "mcp:read mcp:write offline_access" }
}

The declared scope string is all three scopes; the consent page derives the granted set from that request.

Authenticate

opencode mcp auth bloomy-earth

opencode registers through Dynamic Client Registration (its documented path, observed) and opens the Bloomy consent page, where all three scope rows rendered at the time of the pass. Sign in with your own Dashboard → Integration API credentials.

Freshness

opencode mcp logout bloomy-earth → opencode mcp auth bloomy-earth → start a new session. The fresh enumeration shows all seven tools, with the one-time confirmationCode parameter visible on all three write schemas (observed). One host gap on this version: the /mcps panel does not itself enumerate tools in 1.19.5.

Confirmation

Confirmation is conversational two-step: the assistant relays the server's "not executed — confirmation required" summary with the one-time code, and your reply is the second call. A full accept → execute → certificate round-trip was observed end-to-end on this host during validation.

Token expiry

The validated session did not refresh silently past the roughly one-hour access-token expiry. If calls start returning Unauthorized, re-run opencode mcp auth bloomy-earth — observed twice during the validation day.