[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Planity API and MCP server

> 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.

Booking and management software for beauty salons, barbers and nail studios: an online agenda with a listing on planity.com, client records, a cash register and statistics.

## What is the Planity API?

Cotlet's Planity API exposes 14 endpoints for your own Planity account: list appointments, get appointment, search clients, get client record, list services, list staff, get appointment statistics, list no-shows, add appointment, change appointment, delete appointment, block staff time, remove staff time block and allow or stop online booking for a client. The list_appointments endpoint returns reads the appointments of the Agenda tab for a date range, for the whole salon or one staff member. Each endpoint takes simple JSON inputs like staff_id, client_id or date_from and works both as an operation of the planity_read or planity_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 14 (8 read, 6 write)
- **Updated:** 2026-10-17

Planity has no public API, no developer docs and no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Planity with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Planity have an official API?

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.

| Task | Planity official | Cotlet |
|---|---|---|
| List appointments in the agenda | Partly: Appointment export, switched on by Planity support on request | Yes |
| Booking statistics for a period | Partly: Exporter and Imprimer give an email or paper copy, by hand | Yes |
| List no-shows (RDV pas venus) | No | Yes |
| Search and read client records | No | Yes |
| Add an appointment | No | Yes |
| Move or delete an appointment | No | Yes |
| Block a staff member's time | No | Yes |
| Stop a client booking online | No | Yes |

Sources: [Planity Pro: Agenda](https://info.planity.com/solution/agenda-en-ligne), [Planity Help: All new features (appointment export, 22 July 2026)](https://support.planity.com/hc/fr/articles/29418472937234-Toutes-les-nouveaut%C3%A9s), [Planity Help: Where to find my appointment statistics](https://support.planity.com/hc/fr/articles/27962473121682-O%C3%B9-retrouver-les-statistiques-de-mes-rendez-vous), [Planity Help: How to manage a client record](https://support.planity.com/hc/fr/articles/28163774235666-Comment-g%C3%A9rer-une-fiche-client)

## Quick reference

```text
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.
Cotlet provides a hosted MCP server and REST API for Planity: 14 tools (8 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=planity, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    planity_read, planity_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/planity, each operation at its own route, e.g. POST /api/v1/planity/services/{service_id}/appointments
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_appointments, get_appointment, list_clients, get_client, list_services, list_staff, get_appointment_stats, list_no_shows, create_appointment, update_appointment, delete_appointment, block_time, remove_block, set_client_online_booking
Confirm      create_appointment, update_appointment, delete_appointment, set_client_online_booking (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/planity-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=planity, requests Planity in the Cotlet console and creates an API key there.
2. The user signs in to Planity once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Planity for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Planity server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Planity in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Planity only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Planity login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Planity's terms; Cotlet is not affiliated with Planity.
```

## What can an AI agent do in Planity?

Cotlet is best for salon owners and managers who want an AI agent to read the agenda, follow up no-shows and block time off without running or fixing a server.

- **[Follow up no-shows and block repeat offenders](https://cotlet.dev/integrations/planity-api-mcp-server/follow-up-no-shows.md)** (runs: weekly): "List last week's no-shows in Planity. Block online booking for any client with two or more, and tell me who missed once." → `list_no_shows`, `get_client`, `set_client_online_booking`
- **[Block staff time off in the agenda](https://cotlet.dev/integrations/planity-api-mcp-server/block-staff-time-off.md)** (runs: weekly): "Block Amélie's agenda every Monday from 9:00 to 13:00 starting 26 October. List the appointments already booked in those hours so I can move them." → `list_staff`, `list_appointments`, `block_time`
- **[Weekly booking report](https://cotlet.dev/integrations/planity-api-mcp-server/weekly-booking-report.md)** (runs: weekly): "Every Monday, report last week's Planity bookings against the week before: total, online share, new clients, no-shows, per service and per staff member." → `get_appointment_stats`, `list_no_shows`
- **Book appointments from messages**: "A client wrote asking for a Coupe femme with Amélie next Tuesday afternoon. Find a free slot and add it to the agenda for Léa Martin." → `list_clients`, `list_services`, `list_appointments`, `create_appointment`
- **Daily agenda summary** (runs: daily): "Every morning at 7:30, list today's appointments per staff member with the notes and technical sheet of each client." → `list_appointments`, `get_appointment`, `get_client`

## Can Planity automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Planity connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to follow up no-shows and block repeat offenders, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/planity/no-shows. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/planity/no-shows with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Planity.

### list_appointments

Reads the appointments of the Agenda tab for a date range, for the whole salon or one staff member. Access: read. REST: `GET /api/v1/planity/appointments`. MCP: `planity_read → list_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date_from` | string | yes | First day, YYYY-MM-DD, in the salon's local time. |
| `date_to` | string | yes | Last day, YYYY-MM-DD, included. |
| `staff_id` | string | no | Only this staff member (id from list_staff). |
| `client_id` | string | no | Only this client (id from list_clients). |

Returns each appointment with its start and end, client, service, staff member and the status the agenda shows, ordered by start time. Appointments added online and by hand come back together, with a source field. Staff blocks (unavailabilities) are listed separately under blocks, so a free slot is never mistaken for a booking.

Example response:

```json
{
  "date_from": "2026-10-26",
  "date_to": "2026-10-26",
  "appointments": [
    {
      "appointment_id": "a_9120",
      "start": "2026-10-26T09:30:00",
      "end": "2026-10-26T10:30:00",
      "client": {
        "client_id": "c_1042",
        "name": "Léa Martin"
      },
      "service": "Coupe femme",
      "staff": {
        "staff_id": "st_01",
        "name": "Amélie"
      },
      "status": "confirmed",
      "source": "online"
    },
    {
      "appointment_id": "a_9124",
      "start": "2026-10-26T11:00:00",
      "end": "2026-10-26T12:30:00",
      "client": {
        "client_id": "c_0877",
        "name": "Noah Petit"
      },
      "service": "Couleur",
      "staff": {
        "staff_id": "st_03",
        "name": "Inès"
      },
      "status": "confirmed",
      "source": "salon"
    }
  ],
  "blocks": []
}
```

### get_appointment

Reads one appointment with its notes, extra services and the client's contact details. Access: read. REST: `GET /api/v1/planity/appointments/{appointment_id}`. MCP: `planity_read → get_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Id from list_appointments. |

Returns the fields the appointment window shows: client, date and start time, service, staff member, extra services, notes and title. It does not return payment tickets; the cash register is not covered.

Example response:

```json
{
  "appointment_id": "a_9120",
  "start": "2026-10-26T09:30:00",
  "end": "2026-10-26T10:30:00",
  "client": {
    "client_id": "c_1042",
    "name": "Léa Martin",
    "phone": "+33 6 00 00 00 00"
  },
  "service": "Coupe femme",
  "extra_services": [],
  "staff": {
    "staff_id": "st_01",
    "name": "Amélie"
  },
  "status": "confirmed",
  "notes": "Wants to keep the length."
}
```

### list_clients

Searches the Clients tab by name and returns matching client records. Access: read. REST: `GET /api/v1/planity/clients`. MCP: `planity_read → list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Part of the client's name, as typed in the search bar of the Clients tab. |
| `include_deleted` | boolean | no | Also search records deleted with Supprimer le client (Afficher les clients supprimés). Default false. |

Returns the id, name, email and phone of each match, enough to pick the right client before get_client or create_appointment. Client records are personal data: the result goes to your agent, so keep the query narrow. The tool never lists the whole client file.

Example response:

```json
{
  "query": "martin",
  "clients": [
    {
      "client_id": "c_1042",
      "name": "Léa Martin",
      "email": "client@example.com",
      "phone": "+33 6 00 00 00 00"
    },
    {
      "client_id": "c_1190",
      "name": "Hugo Martin",
      "email": "client2@example.com",
      "phone": "+33 6 00 00 00 01"
    }
  ]
}
```

### get_client

Reads one client record with upcoming and past appointments and the technical sheet. Access: read. REST: `GET /api/v1/planity/clients/{client_id}`. MCP: `planity_read → get_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Id from list_clients. |

Returns the fields of the record (name, phone, email, date of birth, address), whether the client may book online, and the appointments and technical sheet (fiche technique) the record shows. Payment tickets and product purchases stay in the cash register and are not returned.

Example response:

```json
{
  "client_id": "c_1042",
  "name": "Léa Martin",
  "phone": "+33 6 00 00 00 00",
  "email": "client@example.com",
  "online_booking_allowed": true,
  "upcoming_appointments": [
    {
      "appointment_id": "a_9120",
      "start": "2026-10-26T09:30:00",
      "service": "Coupe femme"
    }
  ],
  "past_appointments": [
    {
      "appointment_id": "a_8812",
      "start": "2026-10-13T10:00:00",
      "service": "Coupe femme",
      "status": "no_show"
    }
  ],
  "technical_sheet": "Color 6.3, 20 vol."
}
```

### list_services

Lists the services (prestations) the salon offers with their duration. Access: read. REST: `GET /api/v1/planity/services`. MCP: `planity_read → list_services`.

No parameters.

Returns the services set up under Admin, with the duration of each. Use the ids in create_appointment and update_appointment. Prices and products linked to a service are not returned.

Example response:

```json
{
  "services": [
    {
      "service_id": "sv_11",
      "name": "Coupe femme",
      "duration_minutes": 60
    },
    {
      "service_id": "sv_12",
      "name": "Couleur",
      "duration_minutes": 90
    },
    {
      "service_id": "sv_14",
      "name": "Brushing",
      "duration_minutes": 30
    }
  ]
}
```

### list_staff

Lists the staff members (collaborateurs) whose agenda columns the salon runs. Access: read. REST: `GET /api/v1/planity/staffs`. MCP: `planity_read → list_staff`.

No parameters.

Returns the id and name of each staff member, as the agenda shows them. Use the ids to filter list_appointments and to block time with block_time.

Example response:

```json
{
  "staff": [
    {
      "staff_id": "st_01",
      "name": "Amélie"
    },
    {
      "staff_id": "st_02",
      "name": "Lucas"
    },
    {
      "staff_id": "st_03",
      "name": "Inès"
    }
  ]
}
```

### get_appointment_stats

Reads Admin > Statistiques RDV for a period: bookings, online share, new clients, no-shows, per service and per staff member. Access: read. REST: `GET /api/v1/planity/appointment-stats`. MCP: `planity_read → get_appointment_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date_from` | string | yes | First day, YYYY-MM-DD. |
| `date_to` | string | yes | Last day, YYYY-MM-DD, included. |
| `compare_previous` | boolean | no | Also return the previous period of the same length, as the compare option does. Default false. |

Returns the figures of the tabs Indicateurs clés, Prestations, Collaborateurs, RDV and RDV pas venus. All figures come from the appointments recorded in the agenda. estimated_revenue is Planity's estimate from bookings, not takings from the cash register.

Example response:

```json
{
  "date_from": "2026-10-12",
  "date_to": "2026-10-18",
  "appointments": 154,
  "online": 96,
  "in_salon": 58,
  "online_rate_percent": 62.3,
  "new_clients": 21,
  "no_shows": 3,
  "estimated_revenue": 6120,
  "by_service": [
    {
      "service": "Coupe homme",
      "appointments": 55
    },
    {
      "service": "Coupe femme",
      "appointments": 41
    },
    {
      "service": "Brushing",
      "appointments": 35
    },
    {
      "service": "Couleur",
      "appointments": 23
    }
  ],
  "by_staff": [
    {
      "staff": "Amélie",
      "appointments": 62
    },
    {
      "staff": "Lucas",
      "appointments": 51
    },
    {
      "staff": "Inès",
      "appointments": 41
    }
  ],
  "previous": {
    "date_from": "2026-10-05",
    "date_to": "2026-10-11",
    "appointments": 141,
    "online": 83,
    "in_salon": 58
  }
}
```

### list_no_shows

Lists appointments marked "Pas venu" in the agenda for a date range, as the tab RDV pas venus does. Access: read. REST: `GET /api/v1/planity/no-shows`. MCP: `planity_read → list_no_shows`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date_from` | string | yes | First day, YYYY-MM-DD. |
| `date_to` | string | yes | Last day, YYYY-MM-DD, included. |
| `staff_id` | string | no | Only this staff member (id from list_staff). |

Returns each no-show with its client, service and staff member, oldest first, and no_shows_in_period for that client within the range. Only appointments someone marked "Pas venu" appear: a client who did not come and was never marked is not in the list.

Example response:

```json
{
  "date_from": "2026-10-12",
  "date_to": "2026-10-18",
  "no_shows": [
    {
      "appointment_id": "a_8812",
      "start": "2026-10-13T10:00:00",
      "client": {
        "client_id": "c_1042",
        "name": "Léa Martin"
      },
      "service": "Coupe femme",
      "staff": "Amélie",
      "no_shows_in_period": 2
    },
    {
      "appointment_id": "a_8830",
      "start": "2026-10-15T14:30:00",
      "client": {
        "client_id": "c_0877",
        "name": "Noah Petit"
      },
      "service": "Couleur",
      "staff": "Inès",
      "no_shows_in_period": 1
    },
    {
      "appointment_id": "a_8851",
      "start": "2026-10-17T11:00:00",
      "client": {
        "client_id": "c_1042",
        "name": "Léa Martin"
      },
      "service": "Brushing",
      "staff": "Amélie",
      "no_shows_in_period": 2
    }
  ]
}
```

### create_appointment

Adds an appointment to the agenda the way you do for a client who books by phone. Access: write, asks the user first. REST: `POST /api/v1/planity/services/{service_id}/appointments`. MCP: `planity_write → create_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `service_id` | string | yes | Id from list_services. |
| `staff_id` | string | yes | Id from list_staff. |
| `start` | string | yes | Date and start time, ISO 8601, in the salon's local time. |
| `client_id` | string | no | Existing client from list_clients. Leave out to enter a new client with client_name. |
| `client_name` | string | no | Name of a client without a record. Required when client_id is left out. |
| `client_phone` | string | no | Phone of a client without a record. |
| `notes` | string | no | Note on the appointment. |

Returns the new appointment as the agenda shows it. The end time follows the duration of the service. The help article on adding an appointment does not say whether Planity notifies the client, so the agent reports what Planity shows after saving. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "a_9201",
  "start": "2026-10-27T15:00:00",
  "end": "2026-10-27T16:00:00",
  "client": {
    "client_id": "c_1042",
    "name": "Léa Martin"
  },
  "service": "Coupe femme",
  "staff": {
    "staff_id": "st_01",
    "name": "Amélie"
  },
  "status": "confirmed",
  "source": "salon"
}
```

### update_appointment

Changes the date, time, service, staff member or notes of an existing appointment. Access: write, asks the user first. REST: `PATCH /api/v1/planity/appointments/{appointment_id}`. MCP: `planity_write → update_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Id from list_appointments. |
| `start` | string | no | New date and start time, ISO 8601, in the salon's local time. |
| `staff_id` | string | no | New staff member. |
| `service_id` | string | no | New service. |
| `notes` | string | no | New note. |

Returns the appointment after the change. Only the fields you pass change. It moves the booking of a real client, and the help article does not say whether Planity notifies them, so the agent reads the appointment back to check. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "a_9120",
  "start": "2026-10-27T09:30:00",
  "end": "2026-10-27T10:30:00",
  "client": {
    "client_id": "c_1042",
    "name": "Léa Martin"
  },
  "service": "Coupe femme",
  "staff": {
    "staff_id": "st_01",
    "name": "Amélie"
  },
  "status": "confirmed"
}
```

### delete_appointment

Deletes one appointment from the agenda with Supprimer. Access: write, asks the user first. REST: `DELETE /api/v1/planity/appointments/{appointment_id}`. MCP: `planity_write → delete_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Id from list_appointments. |

Returns the id and the details of the deleted appointment. Deleting from the agenda ignores the cancellation deadline you set for online bookings. Planity deletes one appointment at a time and has no bulk delete, so the agent calls this once per appointment. A deleted appointment is not restored by Cotlet; add it again with create_appointment. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "a_9124",
  "deleted": true,
  "start": "2026-10-26T11:00:00",
  "client": {
    "client_id": "c_0877",
    "name": "Noah Petit"
  },
  "service": "Couleur"
}
```

### block_time

Blocks a staff member's agenda for a period, once or repeating, so no client can book online in it. Access: write. REST: `POST /api/v1/planity/staffs/{staff_id}/time/block`. MCP: `planity_write → block_time`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `staff_id` | string | yes | Id from list_staff. |
| `start` | string | yes | Start of the block, ISO 8601, in the salon's local time. |
| `end` | string | yes | End of the block, same day as start. |
| `repeat` | string | no | How the block repeats: none (default), daily or weekly. |

Returns the block with an id. Planity says no client can book online in the blocked time. It does not move or delete appointments already in the period: list_appointments shows them. A block reaches no one and is undone with remove_block, so it does not wait for your OK.

Example response:

```json
{
  "block_id": "b_330",
  "staff": {
    "staff_id": "st_01",
    "name": "Amélie"
  },
  "start": "2026-10-26T09:00:00",
  "end": "2026-10-26T13:00:00",
  "repeat": "weekly",
  "online_booking_blocked": true
}
```

### remove_block

Removes a block made with block_time, so the time can be booked online again. Access: write. REST: `DELETE /api/v1/planity/blocks/{block_id}`. MCP: `planity_write → remove_block`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `block_id` | string | yes | Id from block_time or from the blocks of list_appointments. |

Returns the id of the removed block. It reaches no one and block_time puts the block back, so it does not wait for your OK. For a repeating block it removes the whole series.

Example response:

```json
{
  "block_id": "b_330",
  "removed": true
}
```

### set_client_online_booking

Ticks or clears "Empêcher ce client de prendre RDV en ligne" on a client record. Access: write, asks the user first. REST: `PUT /api/v1/planity/clients/{client_id}/online-booking`. MCP: `planity_write → set_client_online_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Id from list_clients. |
| `allowed` | boolean | yes | false stops the client booking on Planity online, true lets them book again. |

Returns the client with the new setting. Planity names this option for clients who miss appointments. It governs online booking and leaves the record and its appointments as they are. It decides whether a person can book, so each call asks for your OK. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "client_id": "c_1042",
  "name": "Léa Martin",
  "online_booking_allowed": false
}
```

## How do I connect Planity to Claude Code, Codex or Cursor?

Connecting Planity takes three steps: sign up, sign in to Planity once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Planity to your agent.

1. **Create an account** Sign up and add Planity in the console. Your API key is there too.

2. **Sign in to Planity in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Planity there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

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

4. **Ask your agent** Ask in plain words. Your agent finds the Planity tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List last week's no-shows in Planity. Block online booking for any client with two or more, and tell me who missed once.
```

### Call Planity from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/planity with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/planity/services/sv_11/appointments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"staff_id":"st_01","start":"2026-10-27T15:00:00","client_id":"c_1042"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "appointment_id": "a_9201",
  "start": "2026-10-27T15:00:00",
  "end": "2026-10-27T16:00:00",
  "client": {
    "client_id": "c_1042",
    "name": "Léa Martin"
  },
  "service": "Coupe femme",
  "staff": {
    "staff_id": "st_01",
    "name": "Amélie"
  },
  "status": "confirmed",
  "source": "salon"
}
```

## Why use Cotlet for Planity?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Planity yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Planity changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Planity to Cotlet?

Yes. You sign in to Planity yourself, in your own Cloud Browser, and we never save your password. Your agents only get Planity once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

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.

**Is this an official Planity integration?**

No, Cotlet is independent of Planity. Planity has no public API. Cotlet works through your own Planity account, the way you use Planity in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Planity in your console: your agents lose access at once and you stay signed in. Signing out of Planity in the browser works too, and Reset browser deletes the whole profile.

## Is there a Planity MCP server on GitHub?

Planity itself offers exports, not a connection: appointment export on request and statistics you email or print. They are read-only and run by hand, so a script or an agent cannot add, move or block anything. Cotlet reads and edits the agenda for you in your own Planity session, and our team keeps it working when Planity changes.

|  | Planity exports | Cotlet |
|---|---|---|
| Setup | Email contact@planity.com from the admin address to switch on appointment export, then export from your account | Sign up, sign in to Planity once, add one MCP server or API key |
| What you get | Exported appointment details and statistics sent by email or printed | Live reads of the agenda, clients and statistics, plus adding, moving, deleting and blocking |
| When Planity changes | Planity maintains its own export | Our team tests it daily and fixes it for you; failed calls are free |
| Your Planity session | Nothing to connect: you work in your own browser | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | You sign in again by hand | Your Cloud Browser keeps you signed in; if Planity logs you out, your agent gets a link to sign in again |
| Where it runs | By hand, in the Planity Pro screens | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | No separate fee is listed in Planity's help pages | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Planity changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Planity API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Planity API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| 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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Planity account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Planity yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Planity only after you enable it. When Planity signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Planity, sign out of Planity in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Planity's terms:** You use your own Planity account and stay responsible for following Planity's terms. Cotlet is independent and not affiliated with Planity. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Planity in the console and press Request access. Then you create your API key and connect Planity there.

**Do I need to be technical?**

No. You sign in to Planity once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Planity to Cotlet?**

Yes. You sign in to Planity yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Planity once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Planity sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Planity cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Planity's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Planity sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Planity login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Planity offers no OAuth or API for this, so there is no scoped token to hold. That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Does the agent read the revenue from my cash register?**

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.

**Are clients told when my agent moves or deletes an appointment?**

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.

**Who owns the client data my agent reads?**

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.

**Can my agent post or send messages in Planity without asking me?**

No. Every call to create_appointment, update_appointment, delete_appointment or set_client_online_booking waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. block_time and remove_block run without asking, because they send nothing to anyone and one call undoes it.

**Can I use the Planity API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/planity from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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](https://cotlet.dev/about.md)

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.