StyleSeat 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 and export it as COTLET_API_KEY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
StyleSeat through Cotlet.dev. Call styleseat_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 |
|---|---|
| styleseat_guideA | How to work in StyleSeat (appointments, refunds, reviews and client campaigns): its screens and the sign-in link. Call this first. |
| styleseat_statusA | Check that your Cotlet.dev account and StyleSeat are ready: account, credits and StyleSeat connection. |
| styleseat_openA | Open a StyleSeat page in your signed-in Cloud Browser (default https://www.styleseat.com) to work with appointments, refunds, reviews and client campaigns. |
| styleseat_readA | Read the current StyleSeat page: its text and numbered buttons, links and fields. |
| styleseat_clickB | Click a numbered element on the current StyleSeat page. |
| styleseat_typeC | Type text into a numbered field on the current StyleSeat page. |
| styleseat_closeA | Close the StyleSeat 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 browser-automation action or setup step: status, guide, open, read, click, type, and close. The numbered-element model for read/click/type prevents overlap, and status versus open are clearly separated.
All tools use the styleseat_ prefix followed by a single lowercase verb or noun (status, type, close, guide, open, read, click). The pattern is consistent and predictable throughout.
Seven tools are well-scoped for a browser automation server: setup, page interaction, and session teardown. No redundant tools are present.
Core lifecycle is covered: check readiness, open, read, click, type, close, plus a guide. Minor gaps like explicit scroll, wait, or back navigation exist, but agents can likely work around them via read/click.