Billdr 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 to authenticate the hosted MCP connection (Bearer token) and required by the local stdio server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Billdr through Cotlet.dev. Call billdr_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 |
|---|---|
| billdr_guideA | How to work in Billdr (projects, quotes, change orders, invoices, budgets, timesheets and daily logs): its screens and the sign-in link. Call this first. |
| billdr_statusA | Check that your Cotlet.dev account and Billdr are ready: account, credits and Billdr connection. |
| billdr_openA | Open a Billdr page in your signed-in Cloud Browser (default https://app.billdr.co) to work with projects, quotes, change orders, invoices, budgets, timesheets and daily logs. |
| billdr_readB | Read the current Billdr page: its text and numbered buttons, links and fields. |
| billdr_clickB | Click a numbered element on the current Billdr page. |
| billdr_typeB | Type text into a numbered field on the current Billdr page. |
| billdr_closeA | Close the Billdr 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 the browser workflow: guidance, readiness check, session opening, reading, clicking, typing, and closing. There is no meaningful overlap between tools, and the descriptions make the intended sequence clear.
All tools use a consistent billdr_ prefix followed by a short, predictable verb or noun. The pattern is uniform across the entire set.
Seven tools is well-scoped for a browser automation server focused on a single application. Each tool corresponds to a necessary lifecycle action without bloat.
The core browser interaction lifecycle is covered: open, read, click, type, and close, plus onboarding and status helpers. Minor gaps exist around scrolling, waiting for page load, or selecting dropdown values, though these may be workable through links and clicks.