AestheticsPro MCP Server
# AestheticsPro MCP server for ChatGPT and Claude
Connect AestheticsPro to ChatGPT, Claude and other AI agents through Cotlet. Work with appointment scheduling, client contact details, leads and outreach in your own signed-in account. Cotlet is independent and not affiliated with AestheticsPro. If AestheticsPro offers an official API for your needs, we recommend it.
## What you can ask
> Show tomorrow's appointment calendar by provider.
> Find the appointment I specify and prepare a move to the new time I choose. Ask me before saving.
> Create a lead from the contact details I provide and ask me before assigning it to my chosen staff member.
## Connect in 2 minutes
Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.
### ChatGPT
Settings → Apps → add connector URL `https://cotlet.dev/mcp/v1`, then sign in with Cotlet.dev. No API key needed.
### Claude Code
```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```
### Cursor
Copy `.cursor/mcp.json` from this repo into your project:
```json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}
```
## Run it locally (stdio)
This repo is a real MCP server. It speaks MCP over stdio, lists its AestheticsPro tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
```json
{"mcpServers":{"aestheticspro":{"command":"uvx","args":["aestheticspro-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}
```
Or with Docker:
```bash
docker build -t aestheticspro-mcp .
docker run -i --rm -e COTLET_API_KEY aestheticspro-mcp
```
Tools: `aestheticspro_guide`, `aestheticspro_status`, `aestheticspro_open`, `aestheticspro_read`, `aestheticspro_click`, `aestheticspro_type`, `aestheticspro_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
## Command line
Python 3.10+, nothing else to install. From PyPI:
```bash
pip install aestheticspro-mcp # or run it once: uvx aestheticspro-mcp connect
aestheticspro-mcp connect
```
Or straight from this repo:
```bash
export COTLET_API_KEY="your-key"
python3 aestheticspro_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 aestheticspro_agent.py status # is AestheticsPro ready in your Cotlet.dev account
python3 aestheticspro_agent.py guide # AestheticsPro screens and sign-in link
python3 aestheticspro_agent.py read # open AestheticsPro, read the page, close the browser
python3 aestheticspro_agent.py tools # list Cotlet.dev tools
python3 aestheticspro_agent.py serve # start the stdio MCP server (same as no argument)
```
## Questions from AestheticsPro users
**How do I connect AestheticsPro to ChatGPT or Claude?**
Sign up at cotlet.dev, log in to AestheticsPro once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your AestheticsPro account through Cotlet, in their phone apps too.
**Can ChatGPT book an appointment in AestheticsPro?**
ChatGPT books the client, service, provider and time you give it on your AestheticsPro calendar, after you approve the booking. Confirmations and reminders then follow your AestheticsPro settings.
**Can ChatGPT reschedule an appointment in AestheticsPro?**
ChatGPT moves an existing AestheticsPro appointment to the new time, provider or room you choose, after you approve the change.
**Can ChatGPT add a new lead in AestheticsPro?**
ChatGPT creates the lead from the name and contact details you give it and assigns it to the staff member you pick in AestheticsPro, after you approve the assignment.
**Is Cotlet affiliated with AestheticsPro?**
No. Cotlet is independent and not affiliated with AestheticsPro.
## Find it on
- [AestheticsPro on Cotlet](https://cotlet.dev/integrations/aestheticspro-api-mcp-server)
- [All Cotlet packages](https://github.com/cotlet-connect)
---
More: https://cotlet.dev/integrations/aestheticspro-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=aestheticspro
Request access: https://cotlet.dev/signup?app=aestheticspro&utm_source=github&utm_medium=readme&utm_campaign=aestheticspro
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.