Joist MCP
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. Required for tool calls; 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.
Joist through Cotlet.dev. Call joist_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 |
|---|---|
| joist_guideA | How to work in Joist (estimates, invoices and clients): its screens and the sign-in link. Call this first. |
| joist_statusB | Check that your Cotlet.dev account and Joist are ready: account, credits and Joist connection. |
| joist_openB | Open a Joist page in your signed-in Cloud Browser (default https://pro.joistapp.com) to work with estimates, invoices and clients. |
| joist_readB | Read the current Joist page: its text and numbered buttons, links and fields. |
| joist_clickB | Click a numbered element on the current Joist page. |
| joist_typeB | Type text into a numbered field on the current Joist page. |
| joist_closeA | Close the Joist 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, status, open, read, click, type, close), so misselection risk is low. The only mild overlap is between joist_guide (instructions/screens) and joist_status (account and connection readiness), both described as first-call tools, which could cause a hesitant agent to pick the wrong one initially.
All tools use the same joist_ prefix followed by a short, lowercase verb (guide, status, open, read, click, type, close). The pattern is predictable and readable throughout.
Seven tools is a tight, well-scoped set for a browser-automation wrapper: one per primitive action plus onboarding/status helpers. No tool feels redundant or out of place.
The surface covers the core loop (open, read, click, type, close) plus onboarding, but generic browser primitives like selecting a dropdown option, pressing keys/Enter, scrolling, or waiting for page loads are absent. In Joist forms with dropdowns or multi-step flows, these gaps could create dead ends, though agents may work around some by clicking.