Covered Beauty MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/covered-beauty'

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Covered Beauty API and MCP server: Let your AI agent get every form signed before they arrive.

Covered Beauty publishes no API. Its website, features and help pages show no developer documentation, and no Covered Beauty MCP server or official ChatGPT or Claude connector was found.

Covered Beauty publishes no API and no MCP server (checked 14 Nov 2026). Cotlet runs a hosted Covered Beauty MCP server with 8 tools that ChatGPT and Claude use in your own salon account. Form links, prices and anything a client sees wait for your OK.

• Free 7-day trial, no card
• Unofficial, not affiliated with Covered Beauty
• Page: https://cotlet.dev/integrations/covered-beauty-api-mcp-server

What can your AI agent do in Covered Beauty?

• Chase forms before tomorrow's clients
• Link the right form to each treatment
• Turn a price list into treatments
• Set a deposit per treatment
• Change your opening hours
• Brief yourself on each client

Does Covered Beauty have an MCP server or an API?

• Covered Beauty is UK booking software from HAMR Ltd, on the web and as an iPhone app with the same login.
• Every plan includes the booking page, card deposits, consent forms, client records and data export: Solo £9, Pro £14 and Team £19.99 a month.
• Its free tools on the website (price list maker, booking page from a photo, form builder) work without an account and do not touch your salon.

What you need	By hand	Data export	Cotlet
Ask ChatGPT or Claude to do the work	Copy and paste	A file to upload	Hosted MCP server
See whose form is still due	Booking by booking	A copy, not today's diary	view_diary
Send form links, set treatments and hours	One screen at a time	Read only	8 tools, writes after your OK
Run from n8n or a script	Manual only	Parse the files yourself	REST, same key

Checked 14 Nov 2026. Sources: Covered Beauty, How it works, Online booking, Client records, Consultation forms, Pricing, Log in

How does the Covered Beauty MCP server work?

1. Log in to Covered Beauty. Once, in a browser we host for you.
2. Connect your AI agent. One address in its settings.
3. Hand it the forms. Find who is due, then approve the links.

Cotlet never sees or stores your password. Writes, and anything that reaches a client, wait for your OK.

How to connect Covered Beauty to your AI agent

1. Log in to Covered Beauty in a Cloud Browser. Open beauty.covered.technology/login in your Cotlet Cloud Browser and sign in with your own email, by password or email code.
2. Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
3. Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.

Covered Beauty shares the address https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector covers them all. Turned Covered Beauty on after connecting? Refresh the connector and the 8 Covered Beauty tools appear.

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Claude:

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"

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: view_diary

All 8 Covered Beauty MCP tools

One tool per Covered Beauty feature you use between clients. Tools with an action read on list and get; the other actions write and ask first.

Booking page and diary

What clients can book, when, and for how much deposit, and the bookings that came in.

• Add and price treatments (manage_treatments, write, asks first): List your treatments, or add or change one with its duration, price and deposit.
• Set working hours (set_working_hours, write, asks first): Read or change the times you take appointments.
• View the diary (view_diary, read): Read the confirmed bookings in your Covered Beauty diary for a day or week.
• Copy the booking link (get_booking_link, read): Read the link to your booking page, for Instagram, Facebook or your website.

Clients and consultation forms

Records, notes and the forms clients sign before they arrive. No tool returns form answers.

• Keep client records and notes (manage_client_records, write, asks first): Find a client, read their visits, notes and signed forms, or add a client or a note.
• Send consultation form links (send_form_link, write, asks first): Email a client a private link to fill in and sign up to 10 forms on their phone, or cancel a link.
• Link forms to treatments (manage_forms, write, asks first): List your consultation forms, switch on a ready-made one, or link a form to the treatments it covers.
• Export records (export_records, read): Download your Covered Beauty records as an export.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/covered-beauty-api-mcp-server#tools

Who can see my Covered Beauty session, and how do I revoke it?

• What we store. Your signed-in Covered Beauty browser profile, AES-256-GCM encrypted, in Finland. Never your password.
• What your agent gets. The 8 Covered Beauty tools. The session cookie stays in the Cloud Browser.
• What the session sees. Your own diary, treatments, clients and forms. On the Team plan, what your own login sees.
• What no tool touches. Form answers, your Stripe account and payouts, refunds, your plan and billing, and the kiosk PIN.
• If Covered Beauty signs you out. You log in again yourself, in the same Cloud Browser, by password or email code.
• How to cut access. Turn Covered Beauty off for agents, reset the browser, or change your Covered Beauty password.

Cotlet never sees or stores your password. You sign in to Covered Beauty yourself, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

What happens when Covered Beauty changes?

Cotlet watches the apps it serves and updates the Covered Beauty server when Covered Beauty changes its pages, so your agent keeps working without a change on your side.

Some features depend on your plan, such as your own web address on Pro and the shared diary on Team. The agent works with what your account shows.

If Covered Beauty signs you out, one click in the Cotlet console reopens the Cloud Browser so you can log in again.

Approvals, undo and mistakes

1. Read tomorrow. view_diary shows whose form is not done.
2. Pick the forms. The ones linked to each treatment.
3. Show you the list. Clients and forms, before any email goes out.
4. Send after your OK. send_form_link emails each client a 14-day link.

Action	How to put it right
Treatment, price, deposit or hours	Call manage_treatments or set_working_hours again with the earlier values
Form link sent to the wrong client	Cancel it with send_form_link; the link stops working
Form linked to the wrong treatment	Link it again with manage_forms
Client note	Add a correcting note with manage_client_records

All 5 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 3 read tools, the diary, booking link and export, run at once.

MCP call:

{
  "name": "send_form_link",
  "arguments": {
    "action": "send",
    "client": "Example Client B",
    "forms": [
      "Brow lamination",
      "New client medical history"
    ]
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/covered-beauty/form-links \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"send","client":"Example Client B","forms":["Brow lamination","New client medical history"]}'

Response:

{
  "client": "Example Client B",
  "forms": [
    "Brow lamination",
    "New client medical history"
  ],
  "sent_by": "email",
  "valid_days": 14
}

The example emails one client a private link to two forms, valid for 14 days and only for her. A cron job or n8n flow can make the same call over REST at /api/v1/covered-beauty with the same key and price, in JSON. Failed calls are free.

How much does the Covered Beauty MCP server cost?

About $17 a month for a solo lash and brow pro, 3,010 credits. Your Covered Beauty plan stays as it is.

Job	Calls	Credits
Evening check of tomorrow's forms	2 × 24	480
Morning brief on the day's clients	2 × 24	480
Notes after appointments	1 × 40	400
Treatment and price changes	1 × 10	100
Hours for busy weeks	1 × 4	40
Monthly data export	1 × 1	10
Cloud Browser, 30 days		1,500
Total	151 calls	3,010

The smallest pack, 5,000 credits for $29, covers this month with room left. Reminders Covered Beauty sends by itself, 48 hours before, need no call.

• Free 7-day trial, no card
• 10 credits per successful call, MCP or REST
• 50 credits a day for the Cloud Browser
• Your Covered Beauty plan applies as it is

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

Covered Beauty MCP server: other ways to connect

Option	What it does	Where it stops
Covered Beauty by hand	Every tool on this page, on the web or in the iPhone app.	One screen at a time, only between clients.
Data export	Your records as a download, on every plan.	A copy to read; it sends and changes nothing.
Calendar sync	Your bookings in another calendar, on every plan.	Bookings only; no forms, clients or treatments.

If you only need your bookings in your phone's calendar, Covered Beauty's own sync is enough. Cotlet fits when you want ChatGPT, Claude or a script to chase forms and keep your treatments and hours up to date, from your own login, with nothing to host.

Who runs Cotlet

Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Covered Beauty tools.

Covered Beauty MCP server: questions

How do I get access?

Sign up free at https://cotlet.dev/signup?app=covered-beauty, turn on Covered Beauty under Integrations in the console and log in at https://beauty.covered.technology/login in your Cloud Browser. Then connect your AI agent and ask who is in tomorrow. The trial needs no card.

Does Covered Beauty have an API?

Covered Beauty publishes no API (checked 14 Nov 2026). Its website, features and help pages show no developer documentation, and no Covered Beauty MCP server or official ChatGPT or Claude connector was found. Cotlet does not need one: it works in your own signed-in Covered Beauty account.

Which Covered Beauty plan do I need?

Any. Covered Beauty's Solo plan (£9 a month) already includes the booking page, deposits, consent forms, client records and data export. Your own web address and the shared team diary come with Pro and Team.

Does the agent read clients' form answers?

No. manage_client_records returns which forms a client signed and when, not the answers. Open a signed form in Covered Beauty yourself before a treatment.

Can the agent hand my tablet to a client in kiosk mode?

No. Hand to client runs on your own phone or tablet in the salon, behind your kiosk PIN. The agent sends private form links by email instead.

Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 8 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.

Is Cotlet affiliated with Covered Beauty?

No. Cotlet is independent and not affiliated with Covered Beauty.

---

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.