Planfy MCP Server

Appointments, customers and recalls in Planfy booking software.

Server MCP Terhosting

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

Terpasang ke Claude Code, Codex, Cursor, dan lainnya

Dokumentasi

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

Planfy MCP server: Let your AI agent run your Planfy bookings.

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.

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.

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Planfy. Planfy is a trademark of its owner. If Planfy's own integrations cover what you need, use them first.

What can your AI agent do in Planfy?

  • Book from messages
  • Find free slots per calendar
  • Move a day off
  • Work through recalls
  • See tomorrow's gaps
  • Find any customer

Does Planfy have an MCP server or an API?

  • Planfy's developer API page says the API is in development.
  • Planfy has no Zapier app.
  • Planfy has no connector in the ChatGPT apps directory or in Claude.
What you needPlanfy APIBy handCotlet
Calendars and free slotsIn developmentYes, one by oneYes
Book or moveIn developmentYes, one by oneYes, after your OK
RecallsIn developmentRecalls tabYes
Ask in ChatGPT or ClaudeNoNoYes
Zapier appNoneNoneNot needed

Checked 8 Nov 2026. Sources: Planfy docs: Developer API, Planfy docs: JavaScript API, Planfy home and pricing

How does the Planfy MCP server work?

  1. Sign in to Planfy. Once, in a browser we host for you.
  2. Connect your AI agent. One address in its settings.
  3. Hand it the busywork. 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.

How to connect Planfy to your AI agent

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

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.

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"

ChatGPT:

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

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: planfy_read

Make, Zapier:

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

All 5 Planfy MCP tools

Calendars

Free slots per staff calendar. Bookings and moves wait for your OK; Planfy sends its usual reminders.

  • List appointments (list_appointments, read): Appointments for a day or range, by staff calendar.
  • Find free slots (find_free_slots, read): Open times for a service, optionally with one staff member.
  • Book appointment (book_appointment, write, asks first): Books a service for a customer.
  • Reschedule appointment (reschedule_appointment, write, asks first): Moves an appointment to a new time or staff member.

Recalls

Customers due back by your recall rules, read only.

  • List customers due a recall (list_recalls, read): Customers due back by your recall rules.

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

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

  • What we store. Your signed-in Planfy profile, AES-256-GCM encrypted, in Finland. No password.
  • What your agent gets. The 5 Planfy tools, never the session cookie.
  • What the session sees. What your login sees: calendars, customers, recalls, services.
  • What no tool touches. Payments, deposits, forms, SMS credits, deletes.
  • If Planfy signs you out. You sign in again yourself, in the same Cloud Browser.
  • How to cut access. 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).

Approvals, undo and mistakes

  1. Reads the request. Service and preferred time.
  2. Checks free slots. On the right calendar.
  3. Proposes the booking. With time and staff.
  4. Waits, then books. The booking shows up in your Cotlet console first.
ActionUndo
Book an appointmentYes, cancel it
Move an appointmentMove 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.

MCP call:

{
  "name": "book_appointment",
  "arguments": {
    "customer_id": "PC-4477",
    "service": "Skin fade",
    "start": "2026-11-13T16:30",
    "staff": "Tariq"
  }
}

REST:

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"}'

Response:

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

How much does the Planfy MCP server cost?

About $23 a month for a salon with 3 staff calendars, 4,050 credits. Your Planfy plan stays as it is.

JobCallsCredits
Booking from a message2 × 901,800
Recalls, weekly1 × 440
Appointment moved3 × 15450
Gaps checked, daily1 × 26260
Cloud Browser, 30 days1,500
Total4,050
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works on Solo, Team and Ultimate

Planfy publishes no booking counts, so the month is our example. Dollars at the $29 pack rate.

Planfy MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
Planfy JavaScript APIShows the booking widget on your website.Widget only; nothing for your own bookings or lists.
Planfy online bookingCustomers book themselves.Only the customer books; no moves or recalls for you.
By handEvery 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.

Also listed on: Odel, mcpbeat

Who runs Cotlet

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.

Planfy MCP server: questions

How do I get access?

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 when you sign up and asks for no card.

How do I connect Planfy to ChatGPT or Claude?

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.

What can ChatGPT do in Planfy?

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.

Is there an official ChatGPT or Claude app for Planfy?

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.

Can ChatGPT book appointments in Planfy?

Yes, with Cotlet. ChatGPT checks free slots on the staff calendars and books the service, after your OK.

Can ChatGPT find customers due a recall in Planfy?

Yes, with Cotlet. ChatGPT reads the Recalls tab and lists customers due back with their last service.

Can ChatGPT reschedule appointments in Planfy?

Yes, with Cotlet. ChatGPT moves appointments to another time or staff member, after your OK.

Is the MCP server different from the REST API?

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.

Is Cotlet affiliated with Planfy?

No. Cotlet is independent and not affiliated with Planfy.


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.