Treatwell 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. Get one 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.
Treatwell through Cotlet.dev. Call treatwell_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 |
|---|---|
| treatwell_guideA | How to work in Treatwell (manage salon appointments, clients, offers, reviews and reports): its screens and the sign-in link. Call this first. |
| treatwell_statusA | Check that your Cotlet.dev account and Treatwell are ready: account, credits and Treatwell connection. |
| treatwell_openB | Open a Treatwell page in your signed-in Cloud Browser (default https://connect.treatwell.co.uk) to work with manage salon appointments, clients, offers, reviews and reports. |
| treatwell_readA | Read the current Treatwell page: its text and numbered buttons, links and fields. |
| treatwell_clickB | Click a numbered element on the current Treatwell page. |
| treatwell_typeB | Type text into a numbered field on the current Treatwell page. |
| treatwell_closeA | Close the Treatwell 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 role: guide is documentation, status is an account/connection health check, and open/read/click/type/close form an unambiguous browser-automation loop. The descriptions explicitly sequence them (guide first, read before click/type, close when done), so an agent can pick the right tool without guessing.
All seven tools share the treatwell_ prefix followed by a single, consistent action verb (guide, status, open, read, click, type, close). There are no mixed conventions, casing inconsistencies, or redundant verb styles.
Seven tools is a tight, well-scoped set: two onboarding/health tools plus five browser primitives that each earn their place. Nothing appears redundant or padded, and the surface is large enough to complete real work.
The open/read/click/type/close loop covers navigation, inspection, and form interaction for the Treatwell web UI, with open accepting a target URL. Minor gaps exist around keyboard actions (Enter/submit shortcuts) and native selects, but those are largely workable by clicking numbered elements or submit buttons.