Square Appointments 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. Required to execute tools; tool 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.
Square Appointments through Cotlet.dev. Call square_appointments_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 |
|---|---|
| square_appointments_guideA | How to work in Square Appointments (appointments, staff calendars, services and booking requests): its screens and the sign-in link. Call this first. |
| square_appointments_statusA | Check that your Cotlet.dev account and Square Appointments are ready: account, credits and Square Appointments connection. |
| square_appointments_openB | Open a Square Appointments page in your signed-in Cloud Browser (default https://squareup.com/login) to work with appointments, staff calendars, services and booking requests. |
| square_appointments_readA | Read the current Square Appointments page: its text and numbered buttons, links and fields. |
| square_appointments_clickB | Click a numbered element on the current Square Appointments page. |
| square_appointments_typeB | Type text into a numbered field on the current Square Appointments page. |
| square_appointments_closeA | Close the Square Appointments 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 phase of a browser session: orient (guide/status), open, observe (read), act (click/type), and tear down (close). The verbs are unambiguous and no two tools compete for the same action. Guide vs. status is the only near-neighbor, but one is documentation and the other is a readiness check, and the descriptions make that clear.
Every tool follows the same predictable pattern: a shared `square_appointments_` prefix plus a single action verb (guide, status, open, read, click, type, close). All snake_case, no camelCase or stylistic drift. This makes the set trivially scannable and groupable by action.
Seven tools is well within the sweet spot and each one earns its place by covering a necessary part of the browser-session lifecycle. There is no filler or redundancy; the surface is minimal but sufficient for iterating on a page.
The open → read → click/type → close loop covers the core interaction model for driving a web UI, and guide/status handle onboarding and readiness. Minor gaps exist around navigation helpers (explicit goto/back/scroll/wait or submit/keypress), which agents must work around by clicking links or typing into fields, but the main workflow is closed.