Breely MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Breely/Cotlet.dev API key. Get it at https://cotlet.dev/app and export it as COTLET_API_KEY. Without it, tool calls fail with instructions to set COTLET_API_KEY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Breely through Cotlet.dev. Call breely_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 |
|---|---|
| breely_guideA | How to work in Breely (bookings, availability, forms, invoices and client reports): its screens and the sign-in link. Call this first. |
| breely_statusA | Check that your Cotlet.dev account and Breely are ready: account, credits and Breely connection. |
| breely_openB | Open a Breely page in your signed-in Cloud Browser (default https://app.breely.com) to work with bookings, availability, forms, invoices and client reports. |
| breely_readA | Read the current Breely page: its text and numbered buttons, links and fields. |
| breely_clickB | Click a numbered element on the current Breely page. |
| breely_typeB | Type text into a numbered field on the current Breely page. |
| breely_closeA | Close the Breely 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 maps to a distinct role: guide (instructions), status (readiness check), open/close (session lifecycle), and read/click/type (page interaction primitives). There is no meaningful overlap between any pair, and the 'call this first' hint on breely_guide further reduces ordering ambiguity.
All seven tools share a uniform breely_ prefix and are short, lowercase, and single-token. The only minor deviation is that guide/status are nouns while open/click/read/type/close are verbs, but the pattern remains highly predictable.
Seven tools is tightly scoped for a browser-automation wrapper: one onboarding pair, one session lifecycle pair, and three interaction primitives. Nothing feels redundant or missing at the count level.
The set covers the core browse loop (open, read, click, type, close) plus onboarding, which is enough to drive bookings, forms, and invoices. However, there is no explicit navigate/goto, scroll, or select-dropdown operation, so some flows depend on link-clicking or may dead-end on non-link controls.