ConstructionOnline MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | No | Your Cotlet.dev API key. Create one in the Cotlet.dev console and set it in your environment. Required for API-key clients (Codex, Claude Code) and the optional local stdio bridge to execute tools; OAuth-based connectors (ChatGPT, Claude) do not need it, and discovery works without a key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
ConstructionOnline through Cotlet.dev. Call constructiononline_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 |
|---|---|
| constructiononline_guideA | How to work in ConstructionOnline (construction projects, estimates, RFIs and invoices): its screens and the sign-in link. Call this first. |
| constructiononline_statusB | Check that your Cotlet.dev account and ConstructionOnline are ready: account, credits and ConstructionOnline connection. |
| constructiononline_openB | Open a ConstructionOnline page in your signed-in Cloud Browser (default https://app.constructiononline.com) to work with construction projects, estimates, RFIs and invoices. |
| constructiononline_readA | Read the current ConstructionOnline page: its text and numbered buttons, links and fields. |
| constructiononline_clickB | Click a numbered element on the current ConstructionOnline page. |
| constructiononline_typeB | Type text into a numbered field on the current ConstructionOnline page. |
| constructiononline_closeA | Close the ConstructionOnline 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 loop: guide (instructions), status (account readiness), open (start session), read (inspect page), click/type (interact), close (end session). The guide-vs-open and read-vs-status pairs are separated clearly by their descriptions and sequencing hints. No two tools appear to do the same thing.
All seven tools share the same 'constructiononline_' prefix in snake_case, which makes the set instantly recognizable. The only minor deviation is that guide and status are nouns while the rest use verbs, but the prefix convention keeps it predictable.
Seven tools is well-scoped for a browser-automation server: setup (guide, status), session lifecycle (open, close), and page interaction (read, click, type). Every tool earns its place with no filler.
The core act-observe loop is covered end to end, including credit-saving close and a guide/status onboarding path. Minor gaps remain for common automation needs such as scrolling, waiting for load, navigation/back, or submitting a form (pressing Enter) without a click.