WorkQuote MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | API key created in the Cotlet.dev console, used to authenticate with the hosted Cotlet.dev MCP endpoint. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
WorkQuote through Cotlet.dev. Call workquote_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 |
|---|---|
| workquote_guideA | How to work in WorkQuote (manage estimates, jobs and invoices): its screens and the sign-in link. Call this first. |
| workquote_statusA | Check that your Cotlet.dev account and WorkQuote are ready: account, credits and WorkQuote connection. |
| workquote_openB | Open a WorkQuote page in your signed-in Cloud Browser (default https://web.workquote.app) to work with manage estimates, jobs and invoices. |
| workquote_readA | Read the current WorkQuote page: its text and numbered buttons, links and fields. |
| workquote_clickB | Click a numbered element on the current WorkQuote page. |
| workquote_typeB | Type text into a numbered field on the current WorkQuote page. |
| workquote_closeA | Close the WorkQuote 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: onboarding/instructions, readiness, open, read, click, type, and close. The only potential overlap is guide vs. status, but their descriptions clearly separate how-to content from account/connection checks.
All tools use the same workquote_ snake_case prefix and short, readable identifiers. The pattern is mostly action-based, though guide and status are nouns rather than verbs, a minor deviation.
Seven tools is well-scoped for a browser automation MCP: a compact lifecycle of guide/status/open/read/click/type/close without redundant operations.
The core interaction loop for working in WorkQuote through a cloud browser is covered, including orientation and session cleanup. Minor gaps like explicit navigation/wait/scroll controls are not fatal because open/read/click/type can work around them.