Local services & SaaS
Faire
Orders, inventory, reorders and messages for wholesale brands.
12 endpoints
Planity has no API for the agenda, client records or statistics. Sign in to Planity once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.
Not affiliated with Planity.
| What you need | Planity's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Agenda, clients, statistics | No | No | Yes, 14 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when Planity changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 23, 2026. Sources: Planity Pro: Agenda · Planity Help: All new features (appointment export, 22 July 2026) · Planity Help: Where to find my appointment statistics · Planity Help: How to manage a client record
AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.
Add Cotlet to your agent once. Planity and every other app you connect show up as its tools.
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" {
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
Every tool is an endpoint under /api/v1/planity with its own method and path, such as POST /api/v1/planity/services/{service_id}/appointments, with the same API key. Our open-source repo has ready scripts to start from.
14 tools on your own Planity account. Agents call them as operations of the MCP tools planity_read and planity_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_appointments | Reads the appointments of the Agenda tab for a date range, for the whole salon or one staff member. | read |
| get_appointment | Reads one appointment with its notes, extra services and the client's contact details. | read |
| list_clients | Searches the Clients tab by name and returns matching client records. | read |
| get_client | Reads one client record with upcoming and past appointments and the technical sheet. | read |
| list_services | Lists the services (prestations) the salon offers with their duration. | read |
| list_staff | Lists the staff members (collaborateurs) whose agenda columns the salon runs. | read |
| get_appointment_stats | Reads Admin > Statistiques RDV for a period: bookings, online share, new clients, no-shows, per service and per staff member. | read |
| list_no_shows | Lists appointments marked "Pas venu" in the agenda for a date range, as the tab RDV pas venus does. | read |
| create_appointment | Adds an appointment to the agenda the way you do for a client who books by phone. | writeasks first |
| update_appointment | Changes the date, time, service, staff member or notes of an existing appointment. | writeasks first |
| delete_appointment | Deletes one appointment from the agenda with Supprimer. | writeasks first |
| block_time | Blocks a staff member's agenda for a period, once or repeating, so no client can book online in it. | write |
| remove_block | Removes a block made with block_time, so the time can be booked online again. | write |
| set_client_online_booking | Ticks or clears "Empêcher ce client de prendre RDV en ligne" on a client record. | writeasks first |
Scroll the table for all 14 tools.
You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.
One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Each call uses 10 credits, and your Cloud Browser uses 50 credits a day while Planity is enabled for agents, so 20 calls a day come to 250 credits.
| 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.
Planity has no public API, no developer docs and no official MCP server (checked 23 Oct 2026). Its own ways to get data out are manual: statistics can be exported or printed from Admin > Statistiques RDV, and an appointment export that Planity support switches on by email on request.
Sign up free, open Planity under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.
No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.
Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Planity yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Planity sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.
Not on anything that reaches other people: create_appointment, update_appointment, delete_appointment, set_client_online_booking wait for your OK by default. You can switch that off per tool for scheduled runs.
No. get_appointment_stats returns the estimated revenue that Statistiques RDV shows, which Planity computes from bookings in the agenda. Payment tickets and product purchases belong to the cash register (Caisse), and no tool reads them.
Planity's help articles on changing and deleting an appointment do not say whether the client is notified. The agent reads the appointment back after each change and reports what Planity shows. Each change waits for your OK by default.
You do. Planity states that the client database belongs exclusively to the salon and that you keep it if you leave. Client records are personal data, so tools read one record or a name search at a time and never the whole file.
Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Planity changes. Pick Cotlet if you want it hosted and kept working for you.
Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.
Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.
No. Cotlet is independent and not affiliated with Planity.
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