Local services & SaaS
Faire
Orders, inventory, reorders and messages for wholesale brands.
12 endpoints
Your AI agent books appointments from DMs and texts, moves a provider's day, finds lapsed clients and unused membership perks. Sign in to Moxie once in your own Cloud Browser. Charts stay untouched.
6 tools Read and write
Moxie has no MCP server, no ChatGPT or Claude app, no public API and no Zapier app of its own (checked 9 Nov 2026). Cotlet runs 6 Moxie tools hosted, over MCP for agents and REST for scripts, in your own Moxie Suite login, for the schedule, clients and memberships only.
| What you need | Moxie API | By hand | Cotlet |
|---|---|---|---|
| Schedule and free times | No API | Yes, one by one | Yes |
| Book or move | No API | Yes, one by one | Yes, after your OK |
| Lapsed clients, memberships | No API | Client by client | Yes |
| Ask in ChatGPT or Claude | No | No | Yes |
| Charts and notes | No API | Yes | Not touched |
Checked 8 Nov 2026. Sources: Moxie help: Log in to Moxie Suite · Moxie help: access from outside the US · Moxie medspa software
Once, in a browser we host for you.
One address in its settings.
It drafts the work, you OK what customers get.
We never keep your Moxie password, the tools never open charts, and no booking or move goes through until you approve it. Who can see your session
Sign in to Moxie in a Cloud Browser. Create a Cotlet account, open Moxie Suite in its Cloud Browser, sign in with your provider login and press Enable for agents.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Moxie shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Moxie on after connecting? Refresh the connector and the 6 tools appear.
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: moxie_read Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: moxie_write Free slots come from the Schedule and working hours. Bookings and moves wait for your OK; Moxie sends its usual messages.
Returns appointments with client, service, provider, start time and status from the Schedule.
MCP callmoxie_read → list_appointments
REST endpointGET https://cotlet.dev/api/v1/moxie/appointments
| Name | Type | Description |
|---|---|---|
| date_from string required | string | ISO date. |
| date_to string | string | ISO date. Default: date_from. |
| provider string | string | Provider name. |
| page integer | integer | Page number. Default: 1. |
{
"date_from": "date from"
} {
"appointments": [
{
"appointment_id": "AP-30122",
"client": "Madison Reyes",
"service": "Botox, forehead",
"provider": "Nurse Kelly",
"start": "2026-11-12T10:00",
"status": "Confirmed"
}
],
"page": 1
} Reads the Schedule and working hours and returns start times where the service fits.
MCP callmoxie_read → find_free_slots
REST endpointGET https://cotlet.dev/api/v1/moxie/free-slots/find
| Name | Type | Description |
|---|---|---|
| service string required | string | Service name as in Services & Products. |
| date string required | string | ISO date. |
| provider string | string | Provider name. |
{
"service": "service",
"date": "date"
} {
"service": "Lip filler",
"slots": [
{
"provider": "Nurse Kelly",
"start": "2026-11-14T13:00"
}
]
} Creates the appointment on the Schedule. Moxie sends its usual confirmation and intake forms by your settings. By default you confirm each call; you can switch that off for this tool.
MCP callmoxie_write → book_appointment
REST endpointPOST https://cotlet.dev/api/v1/moxie/clients/{client_id}/appointments
| Name | Type | Description |
|---|---|---|
| client_id string required | string | Client ID from list_clients. |
| service string required | string | Service name. |
| provider string required | string | Provider name. |
| start string required | string | ISO date and time from find_free_slots. |
{
"client_id": "CL-12140",
"service": "Lip filler",
"provider": "Nurse Kelly",
"start": "2026-11-14T13:00"
} {
"appointment_id": "AP-30177",
"client": "Olivia Chen",
"service": "Lip filler",
"provider": "Nurse Kelly",
"start": "2026-11-14T13:00",
"status": "Confirmed"
} Moves the appointment on the Schedule; your reminder settings decide what the client hears. By default you confirm each call; you can switch that off for this tool.
MCP callmoxie_write → reschedule_appointment
REST endpointPOST https://cotlet.dev/api/v1/moxie/appointments/{appointment_id}/reschedule
| Name | Type | Description |
|---|---|---|
| appointment_id string required | string | Appointment ID from list_appointments. |
| start string required | string | New ISO date and time. |
| provider string | string | New provider. Default: unchanged. |
{
"appointment_id": "appointment_8c41d2",
"start": "start"
} {
"appointment_id": "AP-30122",
"start": "2026-11-13T15:00",
"provider": "Nurse Kelly",
"status": "Confirmed"
} Contact details, last visit and memberships only. No charts, notes or prescriptions.
Returns clients with ID, contact details, last visit and active membership. No chart or medical notes.
MCP callmoxie_read → list_clients
REST endpointGET https://cotlet.dev/api/v1/moxie/clients
| Name | Type | Description |
|---|---|---|
| query string | string | Name, phone or email. |
| not_visited_days integer | integer | Only clients with no visit in this many days. |
| page integer | integer | Page number. Default: 1. |
{
"clients": [
{
"client_id": "CL-12081",
"name": "Brittany Walsh",
"phone": "(512) 555-0142",
"last_visit": "2026-07-30",
"membership": "Glow Club"
}
],
"page": 1
} Returns clients' memberships and packages with renewal date and what is left to use.
MCP callmoxie_read → list_memberships
REST endpointGET https://cotlet.dev/api/v1/moxie/memberships
| Name | Type | Description |
|---|---|---|
| with_unused boolean | boolean | Only memberships or packages with something left to use. |
{
"memberships": [
{
"client": "Brittany Walsh",
"name": "Glow Club",
"renews": "2026-12-01",
"unused": "1 facial"
}
]
} Your signed-in Moxie profile, AES-256-GCM encrypted, in Finland. No password.
The 6 Moxie tools, never the session cookie.
What your login sees on the Schedule, client contact details and memberships.
Charts, notes, prescriptions, payments, inventory, deletes.
You sign in again yourself, in the same Cloud Browser.
Disable for agents, reset the browser, or change your Moxie password.
Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
When Moxie moves a button on the Schedule or renames a client tab, we fix the tool and your agent calls it the same way. status.cotlet.dev checks the site, console and API every 3 minutes.
| Action | Undo |
|---|---|
| Book an appointment | Yes, cancel it |
| Move an appointment | Move it back; a message already sent stays sent |
2 of 6 tools ask first: book_appointment, reschedule_appointment. You can turn the wait off per tool once you trust a routine.
{
"name": "book_appointment",
"arguments": {
"client_id": "CL-12140",
"service": "Lip filler",
"provider": "Nurse Kelly",
"start": "2026-11-14T13:00"
}
} curl -X POST https://cotlet.dev/api/v1/moxie/clients/CL-12140/appointments \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"service":"Lip filler","provider":"Nurse Kelly","start":"2026-11-14T13:00"}' {
"appointment_id": "AP-30177",
"client": "Olivia Chen",
"service": "Lip filler",
"provider": "Nurse Kelly",
"start": "2026-11-14T13:00",
"status": "Confirmed"
} A cron job or n8n flow can call the same tools over REST at /api/v1/moxie with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.
About $32 a monthfor a medspa with 3 providers, 5,480 credits. Your Moxie plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Booking from a message | 3 × 100 | 3,000 |
| Lapsed clients, weekly | 2 × 4 | 80 |
| Unused perks, weekly | 1 × 4 | 40 |
| Appointment moved | 3 × 20 | 600 |
| Tomorrow checked, daily | 1 × 26 | 260 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 5,480 |
Moxie publishes no booking counts, so the month is our example. Dollars at the $29 pack rate.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Moxie retention automations | Moxie's own rebooking messages to lapsed clients. | Fixed rules inside Moxie; nothing you can ask. |
| Moxie online booking | Clients book themselves. | Only the client books; no moves or lists for you. |
| By hand | Every screen of Moxie Suite, one booking at a time. | Your front desk's time. |
Moxie has no API or Zapier app, so there is nothing to connect a script to. To book, move and bring clients back from ChatGPT or Claude this week, Cotlet works in the Moxie account you already have.
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Moxie tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev, open Moxie under Integrations in the console and sign in to Moxie in its Cloud Browser. The trial starts with your first app and asks for no card.
Sign up at cotlet.dev, log in to Moxie 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 Moxie account through Cotlet, in their phone apps too.
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Moxie: book from DMs and texts; win back lapsed clients; use up membership perks. You ask in plain words, and anything that reaches other people waits for your OK first.
No. Moxie has no ChatGPT or Claude connector of its own and Moxie has no official MCP server (checked 9 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.
Yes, with Cotlet. ChatGPT finds the client, checks free slots for the service and books it with the provider you name. Booking waits for your OK by default.
Yes, with Cotlet. ChatGPT lists clients who have not been back in the time you name, with their last service, so your team can reach out.
No. The Moxie tools cover the schedule, client contact details and memberships. Charts, notes and prescriptions are not part of them.
Moxie Suite is meant for US access. Cotlet opens it in your own Cloud Browser; if Moxie asks you to sign in from the US, the sign-in step tells you.
Only in how it is called. Both carry the same 6 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
No. Cotlet is independent and not affiliated with Moxie.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy