Bloom MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Required for tool calls when running the local stdio server; set it via the environment (e.g. env in mcpServers config or -e for Docker). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Bloom through Cotlet.dev. Call bloom_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bloom_guideA | How to work in Bloom (manage client bookings, invoices and contracts): its screens and the sign-in link. Call this first. |
| bloom_statusB | Check that your Cotlet.dev account and Bloom are ready: account, credits and Bloom connection. |
| bloom_openB | Open a Bloom page in your signed-in Cloud Browser (default https://app.bloom.io) to work with manage client bookings, invoices and contracts. |
| bloom_readA | Read the current Bloom page: its text and numbered buttons, links and fields. |
| bloom_clickC | Click a numbered element on the current Bloom page. |
| bloom_typeB | Type text into a numbered field on the current Bloom page. |
| bloom_closeA | Close the Bloom browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: guide, status check, browser open/close, and page read/click/type. No two tools overlap in purpose, so an agent can easily select the right one.
All tools share the bloom_ prefix and snake_case, but most are verbs (open, read, click, type, close) while guide and status are noun-based. The pattern is still predictable and readable.
Seven tools are well-scoped for a browser-automation server: one setup guide, one readiness check, and five core session/page operations. Each tool earns its place.
The surface covers session lifecycle and basic page interaction (open, read, click, type, close), which is sufficient for core UI workflows. Minor gaps like scroll, select, or keyboard shortcuts exist but agents can work around them.