Local services & SaaS
Faire
Orders, inventory, reorders and messages for wholesale brands.
12 endpoints
Your AI agent books customers from messages, moves a day off and works through recalls. Sign in to Planfy once in your own Cloud Browser. No waiting for an API.
5 tools Read and write
Planfy has no MCP server, no ChatGPT or Claude app and no Zapier app. Planfy says "An official Planfy API is currently in development"; today only its booking widget has a JavaScript library (Planfy docs, checked 9 Nov 2026). Cotlet runs 5 Planfy tools hosted, over MCP for agents and REST for scripts, in your own Planfy login.
| What you need | Planfy API | By hand | Cotlet |
|---|---|---|---|
| Calendars and free slots | In development | Yes, one by one | Yes |
| Book or move | In development | Yes, one by one | Yes, after your OK |
| Recalls | In development | Recalls tab | Yes |
| Ask in ChatGPT or Claude | No | No | Yes |
| Zapier app | None | None | Not needed |
Checked 8 Nov 2026. Sources: Planfy docs: Developer API · Planfy docs: JavaScript API · Planfy home and pricing
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 Planfy password, and no booking or move goes through until you approve it. Who can see your session
Sign in to Planfy in a Cloud Browser. Create a Cotlet account, open Planfy in its Cloud Browser, sign in with your Planfy 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.
Planfy shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Planfy on after connecting? Refresh the connector and the 5 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: planfy_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: planfy_write Free slots per staff calendar. Bookings and moves wait for your OK; Planfy sends its usual reminders.
Returns appointments with customer, service, staff member, time and status.
MCP callplanfy_read → list_appointments
REST endpointGET https://cotlet.dev/api/v1/planfy/appointments
| Name | Type | Description |
|---|---|---|
| date_from string required | string | ISO date. |
| date_to string | string | ISO date. Default: date_from. |
| staff string | string | Staff member. |
| page integer | integer | Page number. Default: 1. |
{
"date_from": "date from"
} {
"appointments": [
{
"appointment_id": "PA-30122",
"customer": "Eleanor Whitcombe",
"service": "Cut and blow dry",
"staff": "Gemma",
"start": "2026-11-12T10:00",
"status": "Confirmed"
}
],
"page": 1
} Reads the staff calendars and returns start times where the service fits.
MCP callplanfy_read → find_free_slots
REST endpointGET https://cotlet.dev/api/v1/planfy/free-slots/find
| Name | Type | Description |
|---|---|---|
| service string required | string | Service name. |
| date string required | string | ISO date. |
| staff string | string | Staff member. |
{
"service": "service",
"date": "date"
} {
"service": "Skin fade",
"slots": [
{
"staff": "Tariq",
"start": "2026-11-13T16:30"
}
]
} Creates the appointment; Planfy sends its usual confirmation and SMS reminder by your settings. By default you confirm each call; you can switch that off for this tool.
MCP callplanfy_write → book_appointment
REST endpointPOST https://cotlet.dev/api/v1/planfy/customers/{customer_id}/appointments
| Name | Type | Description |
|---|---|---|
| customer_id string required | string | Customer ID from list_customers. |
| service string required | string | Service name. |
| start string required | string | ISO date and time. |
| staff string | string | Staff member. |
{
"customer_id": "PC-4477",
"service": "Skin fade",
"start": "2026-11-13T16:30",
"staff": "Tariq"
} {
"appointment_id": "PA-30177",
"customer": "Sophie Marlowe",
"service": "Skin fade",
"staff": "Tariq",
"start": "2026-11-13T16:30",
"status": "Confirmed"
} Moves the appointment; your settings decide what the customer hears. By default you confirm each call; you can switch that off for this tool.
MCP callplanfy_write → reschedule_appointment
REST endpointPOST https://cotlet.dev/api/v1/planfy/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. |
| staff string | string | New staff member. |
{
"appointment_id": "appointment_8c41d2",
"start": "start"
} {
"appointment_id": "PA-30122",
"start": "2026-11-14T11:00",
"staff": "Gemma",
"status": "Confirmed"
} Customers due back by your recall rules, read only.
Reads the Recalls tab: customers whose recall date has come, with last service.
MCP callplanfy_read → list_recalls
REST endpointGET https://cotlet.dev/api/v1/planfy/recalls
| Name | Type | Description |
|---|---|---|
| due_by string | string | ISO date. Default: today. |
{
"recalls": [
{
"customer_id": "PC-4410",
"customer": "Tariq Hussain",
"last_service": "Eye test",
"due": "2026-11-01"
}
]
} Your signed-in Planfy profile, AES-256-GCM encrypted, in Finland. No password.
The 5 Planfy tools, never the session cookie.
What your login sees: calendars, customers, recalls, services.
Payments, deposits, forms, SMS credits, deletes.
You sign in again yourself, in the same Cloud Browser.
Disable for agents, reset the browser, or change your Planfy 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 Planfy moves a button on the calendar or renames a 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; an SMS already sent stays sent |
2 of 5 tools ask first: book_appointment, reschedule_appointment. You can turn the wait off per tool once you trust a routine.
{
"name": "book_appointment",
"arguments": {
"customer_id": "PC-4477",
"service": "Skin fade",
"start": "2026-11-13T16:30",
"staff": "Tariq"
}
} curl -X POST https://cotlet.dev/api/v1/planfy/customers/PC-4477/appointments \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"service":"Skin fade","start":"2026-11-13T16:30","staff":"Tariq"}' {
"appointment_id": "PA-30177",
"customer": "Sophie Marlowe",
"service": "Skin fade",
"staff": "Tariq",
"start": "2026-11-13T16:30",
"status": "Confirmed"
} A cron job or n8n flow can call the same tools over REST at /api/v1/planfy with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.
About $23 a monthfor a salon with 3 staff calendars, 4,050 credits. Your Planfy plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Booking from a message | 2 × 90 | 1,800 |
| Recalls, weekly | 1 × 4 | 40 |
| Appointment moved | 3 × 15 | 450 |
| Gaps checked, daily | 1 × 26 | 260 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 4,050 |
Planfy 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 |
|---|---|---|
| Planfy JavaScript API | Shows the booking widget on your website. | Widget only; nothing for your own bookings or lists. |
| Planfy online booking | Customers book themselves. | Only the customer books; no moves or recalls for you. |
| By hand | Every calendar in Planfy, one booking at a time. | Your front desk's time. |
Planfy has no API to build on yet. To book, move and work recalls from ChatGPT or Claude this week, Cotlet works in the Planfy 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 Planfy tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev, open Planfy under Integrations in the console and sign in to Planfy in its Cloud Browser. The trial starts with your first app and asks for no card.
Sign up at cotlet.dev, log in to Planfy 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 Planfy account through Cotlet, in their phone apps too.
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Planfy: book from messages; work the recalls; move a day off. You ask in plain words, and anything that reaches other people waits for your OK first.
No. Planfy has no ChatGPT or Claude connector of its own and Planfy 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 checks free slots on the staff calendars and books the service, after your OK.
Yes, with Cotlet. ChatGPT reads the Recalls tab and lists customers due back with their last service.
Yes, with Cotlet. ChatGPT moves appointments to another time or staff member, after your OK.
Only in how it is called. Both carry the same 5 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
No. Cotlet is independent and not affiliated with Planfy.
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