AestheticsPro MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet API key from https://cotlet.dev/app. Used to authenticate with the hosted Cotlet.dev MCP server; without it, tool calls respond asking you to set 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.
AestheticsPro through Cotlet.dev. Call aestheticspro_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 |
|---|---|
| aestheticspro_guideA | How to work in AestheticsPro (schedule appointments and manage client contacts): its screens and the sign-in link. Call this first. |
| aestheticspro_statusA | Check that your Cotlet.dev account and AestheticsPro are ready: account, credits and AestheticsPro connection. |
| aestheticspro_openA | Open a AestheticsPro page in your signed-in Cloud Browser (default https://www.aestheticspro.com/Login) to work with schedule appointments and manage client contacts. |
| aestheticspro_readB | Read the current AestheticsPro page: its text and numbered buttons, links and fields. |
| aestheticspro_clickB | Click a numbered element on the current AestheticsPro page. |
| aestheticspro_typeB | Type text into a numbered field on the current AestheticsPro page. |
| aestheticspro_closeA | Close the AestheticsPro 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 of a browser session (guide, status, open, read, click, type, close) and verbs make the intent clear. Minor overlap between `aestheticspro_guide` and `aestheticspro_status`, which both read as "call this first" onboarding checks, could cause a momentary hesitation about which to use at startup.
Every tool uses the same `aestheticspro_` prefix plus a single lowercase verb (guide, status, open, read, click, type, close). Predictable, uniform snake_case pattern with no deviation.
Seven tools is exactly the right size for a thin browser-automation wrapper: one per primitive action plus session lifecycle and onboarding. No tool appears redundant or bolted on.
The core loop (open -> read -> click/type -> close) is covered, but common browser operations are missing: scroll, wait/retry for page load, dropdown selection, and keyboard submit/navigation. An agent working a real appointment-scheduling flow will hit dead ends on long pages or select fields with no listed escape hatch.