DaySmart MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Cotlet API key used to authenticate API clients and the local stdio bridge. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
DaySmart through Cotlet.dev. Call daysmart_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 |
|---|---|
| daysmart_guideA | How to work in DaySmart (manage appointments, clients, pets and sales): its screens and the sign-in link. Call this first. |
| daysmart_statusA | Check that your Cotlet.dev account and DaySmart are ready: account, credits and DaySmart connection. |
| daysmart_openB | Open a DaySmart page in your signed-in Cloud Browser (default https://daysmart.co) to work with manage appointments, clients, pets and sales. |
| daysmart_readA | Read the current DaySmart page: its text and numbered buttons, links and fields. |
| daysmart_clickB | Click a numbered element on the current DaySmart page. |
| daysmart_typeB | Type text into a numbered field on the current DaySmart page. |
| daysmart_closeA | Close the DaySmart 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: guide (docs), status (readiness), and the five browser primitives (open/read/click/type/close) are clearly separated by resource and action. The only mild overlap is between daysmart_guide and daysmart_status, since both are framed as 'call this first' setup-style tools, but their purposes (instructions vs. account/connection check) remain distinguishable.
All seven tools share a uniform daysmart_ prefix with short, lowercase, single-token names, giving a very predictable pattern. Minor deviation: guide and status are nouns while open/read/click/type/close are verbs, so the action-style grammar isn't perfectly uniform.
Seven tools is a tight, well-scoped set for a browser-driven SaaS automation surface, with no redundant or filler entries. Onboarding, session control, and page interaction are each covered by exactly the tools needed.
The core loop (open, read, click, type, close) is present, but common browser operations are missing: navigation to a different URL or back, scrolling when content exceeds the visible page, keyboard keys (Enter/Escape/Tab) and dropdown/select handling, and any screenshot or verification affordance. These gaps create plausible dead ends in multi-step appointment/client/pet workflows.