Breezeway 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, available at https://cotlet.dev/app. Required for tool calls; without it, tool calls return an error asking you 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.
Breezeway through Cotlet.dev. Call breezeway_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 |
|---|---|
| breezeway_guideA | How to work in Breezeway (create, assign, comment on and approve property tasks): its screens and the sign-in link. Call this first. |
| breezeway_statusA | Check that your Cotlet.dev account and Breezeway are ready: account, credits and Breezeway connection. |
| breezeway_openB | Open a Breezeway page in your signed-in Cloud Browser (default https://app.breezeway.io) to work with create, assign, comment on and approve property tasks. |
| breezeway_readB | Read the current Breezeway page: its text and numbered buttons, links and fields. |
| breezeway_clickB | Click a numbered element on the current Breezeway page. |
| breezeway_typeC | Type text into a numbered field on the current Breezeway page. |
| breezeway_closeA | Close the Breezeway 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 phase of a browser-automation loop (status, guide, open, read, click, type, close), so an agent can generally pick correctly. The only mild overlap is between breezeway_status (account/connection readiness) and breezeway_guide (how-to orientation), which both serve as entry points and could be confused at the start of a session.
All seven tools use the same breezeway_ prefix followed by a single lowercase verb or noun, matching a predictable pattern throughout. There are no mixed conventions or casing inconsistencies.
Seven tools is a tight, well-scoped set for a single-site browser automation surface, with no redundant entries. Each tool corresponds to a concrete step (session setup, observation, interaction, teardown) and earns its place.
The surface covers the full loop: connect/check, orient, open, read, click, type, close, which is enough for create/assign/comment/approve task workflows. Minor gaps exist around navigation beyond the default page, scrolling, and explicit keyboard submit, though these can mostly be worked around via clicking numbered buttons.