BuildBook MCP server
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. Export it as the COTLET_API_KEY environment variable; without it, tool calls fail with a message asking you to set it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
BuildBook through Cotlet.dev. Call buildbook_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 |
|---|---|
| buildbook_guideA | How to work in BuildBook (draft estimates, review project tasks and prepare remodeling invoices): its screens and the sign-in link. Call this first. |
| buildbook_statusA | Check that your Cotlet.dev account and BuildBook are ready: account, credits and BuildBook connection. |
| buildbook_openB | Open a BuildBook page in your signed-in Cloud Browser (default https://app.buildbook.co) to work with draft estimates, review project tasks and prepare remodeling invoices. |
| buildbook_readA | Read the current BuildBook page: its text and numbered buttons, links and fields. |
| buildbook_clickB | Click a numbered element on the current BuildBook page. |
| buildbook_typeC | Type text into a numbered field on the current BuildBook page. |
| buildbook_closeA | Close the BuildBook 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 workflow: guide (instructions), status (account/connection check), open (launch session), read (inspect page), click, type, and close. There is no meaningful overlap between any two tools, and the descriptions reinforce clear boundaries.
All tools share a uniform buildbook_ prefix followed by a single lowercase verb or noun (guide, status, open, read, click, type, close). The pattern is predictable and readable throughout.
Seven tools is well-scoped for a browser-automation server: a guide, a health check, and the five core session primitives (open/read/click/type/close). Nothing feels redundant or missing at the count level.
The surface covers the full basic browser lifecycle: open a page, read its contents, click, type, and close the session. Minor gaps exist—no explicit navigation to an arbitrary URL, scrolling, or dropdown/select handling—but agents can likely work around these via click/type and the guide.