Local services & SaaS
GlossGenius
Appointments, clients, waitlist and sales for salon owners.
15 endpoints
Zolmi publishes no public API and no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Zolmi MCP server with 11 tools that ChatGPT and Claude use in your own salon account: commissions, client formulas, stock, gift cards and campaigns. Checkouts, texts and anything a client sees wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Zolmi. Zolmi is a trademark of its owner. If Zolmi's own integrations cover what you need, use them first.
11 tools Read and write
Zolmi publishes no public API. Its home, features and pricing pages offer no developer documentation or API key, and no Zolmi MCP server or official ChatGPT or Claude connector was found.
| What you need | Zolmi official | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude about your salon | No API or MCP server | Copy and paste | Hosted MCP server |
| Commissions and sales figures | Reports in the app | Open each report | Read and summed by your agent |
| Campaigns, review requests and forms | In the app only | Set up each one | Sent after your OK |
| Run from n8n or a script | No API | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: Zolmi home page · Zolmi pricing · Salon accounting · Salon payroll and commissions · Salon client records · Salon POS · Salon gift cards · Salon inventory · Salon consultation forms · Salon memberships · Salon loyalty program · Salon marketing · Salon reputation management
Once, in a browser we host for you.
One address in its settings.
It reads the figures; you approve what clients get.
Your agent works in your own signed-in Cloud Browser. Checkouts, gift cards, campaigns and anything a client sees wait for your OK. Who can see your session
Sign in to Zolmi in a Cloud Browser. Open ai.zolmi.com/login in your Cotlet Cloud Browser and log in with your own Zolmi account.
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.
Zolmi shares https://cotlet.dev/mcp/v1 with every other app you activate, so a single connector reaches them all. Activated Zolmi after connecting? Refresh the connector and its 11 tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth 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/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: zolmi_read One tool per feature Zolmi describes on its website. Tools with an `action` read with `get`, `list`, `low` or `balance` and write with the rest.
Service and retail sales, expenses, and each stylist's commission from what was rung up at checkout.
Zolmi keeps service income (cuts, color, nails) apart from retail product sales, with payment records and expenses by category. Use it for the figures your accountant asks for. Nothing changes, so it runs without asking.
MCP callzolmi_read → review_financial_records
REST endpointGET https://cotlet.dev/api/v1/zolmi/financial-records/review
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO start date. |
| to string required | string | ISO end date. |
{
"from": "from",
"to": "to"
} {
"from": "2026-11-01",
"to": "2026-11-15",
"service_sales": 18420,
"retail_sales": 2310,
"tips": 1960,
"expenses": [
{
"category": "Color and supplies",
"amount": 1140
},
{
"category": "Rent",
"amount": 3200
}
]
} Zolmi calculates service and retail commissions from what was actually rung up at checkout. Read them before payday and use the figures in your payroll process; the tool only reads.
MCP callzolmi_read → review_staff_commissions
REST endpointGET https://cotlet.dev/api/v1/zolmi/staff-commissions/review
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO start date. |
| to string required | string | ISO end date. |
| staff string | string | One staff member. Leave empty for the whole team. |
{
"from": "from",
"to": "to"
} {
"from": "2026-11-01",
"to": "2026-11-15",
"staff": [
{
"name": "Stylist A",
"service_sales": 6840,
"retail_sales": 720,
"commission": 2808
},
{
"name": "Stylist B",
"service_sales": 5120,
"retail_sales": 410,
"commission": 2089
}
]
} Every Zolmi sale is tied to stock, the client record and the stylist's commission, and a deposit taken at booking is applied. A checkout records money, so the agent shows the lines and total first. It records how the client paid; it does not charge a card. By default you confirm each call; you can switch that off for this tool.
MCP callzolmi_write → checkout_appointment
REST endpointPOST https://cotlet.dev/api/v1/zolmi/appointment/checkout
| Name | Type | Description |
|---|---|---|
| appointment string required | string | Client and time, as the calendar shows it. |
| products array | array | Retail products added at checkout, with quantity. |
| tip number | number | Tip amount. |
| payment_method string required | string | `cash`, `card` or another method your salon records. |
| gift_card_code string | string | Gift card to redeem against the total. |
{
"appointment": "Client A, 2026-11-16 14:00",
"products": [
{
"name": "Color-safe shampoo",
"quantity": 1
}
],
"tip": 30,
"payment_method": "card"
} {
"appointment": "Client A, 2026-11-16 14:00",
"services": [
{
"name": "Color and cut",
"price": 165
}
],
"products": [
{
"name": "Color-safe shampoo",
"price": 28
}
],
"deposit": -30,
"tip": 30,
"total": 193,
"payment_method": "card",
"paid": true
} Zolmi creates a unique code for each gift card and keeps its value, redemptions and any expiry date, so `balance` answers the front desk at once. Selling takes money, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzolmi_write → sell_gift_card
REST endpointPOST https://cotlet.dev/api/v1/zolmi/gift-card/sell
| Name | Type | Description |
|---|---|---|
| action string required | string | `balance` or `sell`. `balance` only reads. |
| code string | string | For `balance`: the gift card code. |
| value number | number | For `sell`: amount, or leave empty with a `service`. |
| service string | string | For `sell`: a service the card is for, such as a facial. |
| buyer string | string | For `sell`: who paid. |
{
"action": "action"
} {
"code": "GC-7K2M",
"value": 100,
"balance": 65,
"redeemed": [
{
"date": "2026-11-02",
"amount": 35
}
],
"expires": null
} Profiles with formulas, patch tests and history, and the consultation and consent forms saved to them.
A Zolmi client profile holds contact details, birthday, preferences and notes, color formulas and service notes, allergies and patch tests, before and after photos and the full appointment history with dates and stylists. `get` reads all of it before a visit. `add` writes exactly what you give it; the client does not see the profile, so it runs without asking.
MCP callzolmi_write → manage_client_record
REST endpointPOST https://cotlet.dev/api/v1/zolmi/client-record/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `get` or `add`. `get` only reads. |
| client string required | string | Client name, email or phone as Zolmi shows it. |
| entry object | object | For `add`: type (`note`, `preference`, `color_formula`, `allergy`, `patch_test`) and text, as your stylist gives it. |
{
"action": "action",
"client": "client"
} {
"client": "Client A",
"last_visit": "2026-10-18",
"stylist": "Stylist A",
"color_formula": "7N + 7G 1:1, 20 vol, 35 min",
"patch_test": "2026-10-11, clear",
"preferences": [
"Quiet appointment"
]
} Zolmi forms cover hair, beauty, nail, spa, massage and tattoo treatments; clients sign consent digitally and the completed form is saved to their profile. Sending reaches the client, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzolmi_write → send_consultation_form
REST endpointPOST https://cotlet.dev/api/v1/zolmi/consultation-forms
| Name | Type | Description |
|---|---|---|
| action string required | string | `list`, `create` or `send`. `list` only reads. |
| form string | string | Form name, for example Color consultation. |
| questions array | array | For `create`: preferences, previous treatments, sensitivities and a consent signature. |
| client string | string | For `send`. |
{
"action": "action"
} {
"form": "Color consultation",
"client": "Client B",
"sent": true,
"saved_to_profile": "on completion"
} Retail and backbar levels, lowered as product use is recorded, with your reorder points.
Zolmi tracks retail and backbar stock and lowers it when product use is recorded at checkout. `low` lists products at or under their reorder point. A count correction reaches no client and is undone by setting the old number, so it runs without asking.
MCP callzolmi_write → update_stock
REST endpointPATCH https://cotlet.dev/api/v1/zolmi/stock
| Name | Type | Description |
|---|---|---|
| action string required | string | `list`, `low` or `set`. `list` and `low` only read. |
| product string | string | For `set`. |
| quantity number | number | For `set`: the counted quantity on hand. |
| reorder_point number | number | For `set`: the level that counts as low stock. |
{
"action": "action"
} {
"low": [
{
"product": "Developer 20 vol",
"on_hand": 2,
"reorder_point": 4
},
{
"product": "Color-safe shampoo",
"on_hand": 3,
"reorder_point": 6
}
]
} Membership tiers, loyalty points, email and SMS campaigns to client segments, and Google review requests.
Zolmi memberships carry tiers, recurring service packages, member discounts and priority booking, with recurring payments and renewal reminders. A tier change changes what the client pays, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzolmi_write → manage_membership
REST endpointPOST https://cotlet.dev/api/v1/zolmi/membership/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `get` or `update`. `get` only reads. |
| client string required | string | Client name, email or phone as Zolmi shows it. |
| tier string | string | For `update`: the membership tier, as set up in Zolmi. |
{
"action": "action",
"client": "client"
} {
"client": "Client C",
"tier": "Monthly Blowout",
"benefits": [
"2 blowouts a month",
"10% off retail"
],
"renews": "2026-12-01"
} Zolmi's loyalty program rewards spend on services and retail, with tiers, birthday bonuses and referral rewards, and keeps clients informed about their balance. Points are value the client can spend, so adding them waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzolmi_write → add_loyalty_reward
REST endpointPOST https://cotlet.dev/api/v1/zolmi/loyalty-rewards
| Name | Type | Description |
|---|---|---|
| action string required | string | `get` or `add_points`. `get` only reads. |
| client string required | string | Client name, email or phone as Zolmi shows it. |
| points number | number | For `add_points`. |
| reason string | string | For `add_points`, for example Referral or Birthday. |
{
"action": "action",
"client": "client"
} {
"client": "Client B",
"points": 340,
"added": 50,
"reason": "Referral"
} Campaigns reach many clients at once, and Zolmi bills text messages separately from the plan, so the agent shows you the segment size and the message before it sends. By default you confirm each call; you can switch that off for this tool.
MCP callzolmi_write → send_marketing_campaign
REST endpointPOST https://cotlet.dev/api/v1/zolmi/marketing-campaigns
| Name | Type | Description |
|---|---|---|
| channel string required | string | `email` or `sms`. |
| segment object required | object | Service history (for example color clients), spend, or last visit before a date. |
| message string required | string | The offer as clients will read it. |
{
"channel": "channel",
"segment": "segment",
"message": "message"
} {
"channel": "sms",
"segment": "Color clients, last visit before 2026-09-01",
"recipients": 38,
"sent": true
} Zolmi's review tools send the request after the visit and help the client post on Google. Each request reaches a client, so the agent lists who gets one first. By default you confirm each call; you can switch that off for this tool.
MCP callzolmi_write → request_reviews
REST endpointPOST https://cotlet.dev/api/v1/zolmi/reviews/request
| Name | Type | Description |
|---|---|---|
| clients array required | array | Clients to ask, usually today's appointments. |
| channel string required | string | `sms` or `email`. |
{
"clients": "clients",
"channel": "channel"
} {
"channel": "sms",
"requested": [
"Client A",
"Client B"
],
"sent": 2
} Your signed-in Zolmi browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 11 Zolmi tools. The session cookie stays in the Cloud Browser.
What your Zolmi login and its staff permissions allow, including whether client contact details are visible.
Card processing and payouts, staff hours and permissions, your Zolmi plan and SMS billing, and refunds.
You log in again yourself, in the same Cloud Browser.
Disable Zolmi for agents, reset the browser, or change your Zolmi password.
Cotlet never sees or stores your password: you log in to Zolmi yourself, and the agent only uses the session that leaves. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Stock count entered wrong | Set the right number with update_stock |
| Note or formula on the wrong client | Correct the profile in Zolmi |
| Checkout recorded wrong | Correct the sale in Zolmi; commissions follow the sale |
| Campaign or review request sent | Already with clients: follow up yourself |
7 of the 9 write tools ask first: by default you confirm each call, and you can switch that off per tool. Client notes and stock counts reach no client and run at once, as do the 2 read tools.
{
"name": "checkout_appointment",
"arguments": {
"appointment": "Client A, 2026-11-16 14:00",
"products": [
{
"name": "Color-safe shampoo",
"quantity": 1
}
],
"tip": 30,
"payment_method": "card"
}
} curl -X POST https://cotlet.dev/api/v1/zolmi/appointment/checkout \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"appointment":"Client A, 2026-11-16 14:00","products":[{"name":"Color-safe shampoo","quantity":1}],"tip":30,"payment_method":"card"}' {
"appointment": "Client A, 2026-11-16 14:00",
"services": [
{
"name": "Color and cut",
"price": 165
}
],
"products": [
{
"name": "Color-safe shampoo",
"price": 28
}
],
"deposit": -30,
"tip": 30,
"total": 193,
"payment_method": "card",
"paid": true
} The example checks out a $165 color and cut with a $28 shampoo, less the $30 deposit taken at booking: $163, plus a $30 tip, $193 on card. A cron job or n8n flow can make the same call over REST at /api/v1/zolmi with the same key and price, in JSON. Failed calls are free.
About $19 a monthfor a four-chair salon open 26 days, 3,300 credits. Your Zolmi plan and SMS charges stay as they are.
| Job | Calls | Credits |
|---|---|---|
| Next-day color prep: four profiles and one form | 5 × 26 | 1,300 |
| Review requests after the day's checkouts | 1 × 26 | 260 |
| Gift card balance questions | 1 × 15 | 150 |
| Weekly low stock list | 1 × 4 | 40 |
| Commission summary each pay period | 1 × 2 | 20 |
| Win-back text campaign | 1 × 2 | 20 |
| Month-end figures for the accountant | 1 × 1 | 10 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 180 calls | 3,300 |
The smallest pack, 5,000 credits for $29, covers this month. More chairs mean more client prep and more calls.
Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer usage.
| 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 |
|---|---|---|
| Zolmi reports | Daily sales, staff performance, end-of-day totals and commissions in the app. | You read and add them up yourself. |
| Zolmi marketing automations | Reminders, birthday offers and review requests set up in Zolmi. | Run on Zolmi's rules; not something you ask in plain words. |
| By hand | The front desk or the phone app. | One screen at a time, between clients. |
If Zolmi publishes an API that covers your job, use it: it is the vendor's own route. Until then Cotlet lets ChatGPT, Claude or a script work in Zolmi from your own login, with nothing to host.
Cotlet is a product of Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), working since 2019 under its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Zolmi tools: contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=zolmi, turn on Zolmi under Integrations in the console and log in at https://ai.zolmi.com/login in your Cloud Browser. Then connect your AI agent and ask it for this pay period's commissions. The trial needs no card.
Zolmi publishes no public API: its home, features and pricing pages offer no API documentation or developer key (checked 16 Nov 2026). No Zolmi MCP server and no official ChatGPT or Claude connector was found. Cotlet does not need one: it works in your own signed-in Zolmi account.
In Zolmi, yes: its pricing page says the salon pays for the software plan, with separate charges for text messages, and card processing fees are separate too. Cotlet adds only its own call credits. Zolmi charges no booking commissions (zolmi.com/pricing, checked 16 Nov 2026).
Only if your Zolmi login can. Zolmi sets staff permissions, including who can see client contact details, and the agent works with the permissions of the login you sign in with.
No. It records the sale and how the client paid, the way your front desk does at checkout. Card payments themselves go through your card reader or Zolmi's payment flow as usual.
Only in how it is called. Both carry the same 11 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Zolmi.
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