Bolster 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. Used as a Bearer token for the hosted Cotlet.dev server; without it a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Bolster through Cotlet.dev. Call bolster_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 |
|---|---|
| bolster_guideA | How to work in Bolster (review the contractor pipeline, draft estimates and schedule jobs): its screens and the sign-in link. Call this first. |
| bolster_statusA | Check that your Cotlet.dev account and Bolster are ready: account, credits and Bolster connection. |
| bolster_openB | Open a Bolster page in your signed-in Cloud Browser (default https://app.bolsterbuilt.com) to work with review the contractor pipeline, draft estimates and schedule jobs. |
| bolster_readA | Read the current Bolster page: its text and numbered buttons, links and fields. |
| bolster_clickB | Click a numbered element on the current Bolster page. |
| bolster_typeB | Type text into a numbered field on the current Bolster page. |
| bolster_closeA | Close the Bolster 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 step in a browser workflow: guide (docs), status (account check), open/read/click/type/close (session control), so selection is mostly straightforward. Minor overlap exists between bolster_guide and bolster_open, whose descriptions both mention reviewing the contractor pipeline and scheduling jobs, which could cause a brief hesitation about which to call first.
All tools share the consistent bolster_ prefix and snake_case form, with short, readable names. The only deviation is that guide and status are nouns while the rest are action verbs, which is a small inconsistency but still predictable.
Seven tools is well-scoped for a browser-automation server: one onboarding guide, one readiness check, and five primitives covering the session lifecycle (open, read, click, type, close). Nothing feels redundant or padded.
The surface covers the core loop of open, inspect, interact, and close, but lacks common browser operations such as scrolling, navigating to a specific URL, keyboard/submit actions, and dropdown selection. These gaps will cause dead ends on longer pages or multi-step forms where scrolling or explicit navigation is required.