CleanManager 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. Required for CleanManager tool calls. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
CleanManager through Cotlet.dev. Call cleanmanager_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 |
|---|---|
| cleanmanager_guideA | How to work in CleanManager (manage cleaning schedules, check-ins, customers, quality reports and storage): its screens and the sign-in link. Call this first. |
| cleanmanager_statusA | Check that your Cotlet.dev account and CleanManager are ready: account, credits and CleanManager connection. |
| cleanmanager_openB | Open a CleanManager page in your signed-in Cloud Browser (default https://cleanmanager.com) to work with manage cleaning schedules, check-ins, customers, quality reports and storage. |
| cleanmanager_readB | Read the current CleanManager page: its text and numbered buttons, links and fields. |
| cleanmanager_clickC | Click a numbered element on the current CleanManager page. |
| cleanmanager_typeB | Type text into a numbered field on the current CleanManager page. |
| cleanmanager_closeA | Close the CleanManager 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 the browser-session lifecycle: status (readiness check), guide (instructions), open (start session), read (inspect page), click, type, close. Even the two informational tools are clearly separated—status is about account/connection state, guide is about how to operate the UI.
All seven tools share the same cleanmanager_ prefix followed by a short, lowercase action word (status, guide, open, read, click, type, close). The pattern is predictable and unambiguous.
Seven tools is well-scoped for a browser-automation wrapper: enough to cover the full session lifecycle without redundant or filler operations.
The surface covers opening, reading, interacting (click/type), and closing a session, which is the core workflow. Minor gaps exist: no explicit navigation to an arbitrary URL, no scroll, and no dedicated select/dropdown handling, though click may cover many of these.