[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.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) # Appointy MCP server: Let your AI agent handle Appointy bookings. > Appointy has no MCP server and no ChatGPT or Claude app. Its private API is listed only on the top Enterprise plan, and its Zapier app has a single action, create customer (checked 8 Nov 2026). Cotlet runs 9 Appointy tools hosted, over MCP for agents and REST for scripts, in your own Appointy login on any plan. Your AI agent books appointments from emails and messages, approves pending requests, moves a day when staff are out and tells you who is on tomorrow. Sign in to Appointy once in your own Cloud Browser. No Enterprise plan needed. - Free 7-day trial, no card - Unofficial, not affiliated with Appointy - Page: https://cotlet.dev/integrations/appointy-api-mcp-server ## What can your AI agent do in Appointy? - Book appointments from emails and messages - Approve pending booking requests - Reschedule when staff are out - Find free slots for a service - See tomorrow's schedule per staff member - Look up a customer's bookings ## Does Appointy have an MCP server or an API? - Zapier triggers on new, updated and cancelled appointments and new customers. - The only Zapier action creates a customer; nothing books, moves or approves. - Appointy has no connector in the ChatGPT apps directory or in Claude. | What you need | Appointy API | Zapier app | Cotlet | |---|---|---|---| | Read appointments | Enterprise only | Triggers on changes | Yes | | Book or move an appointment | Enterprise only | No | Yes, after your OK | | Approve pending requests | Enterprise only | No | Yes, after your OK | | Add a customer | Enterprise only | Yes | Yes | | Appointy plan needed | Enterprise | Any | Any | Checked 8 Nov 2026. Sources: [Appointy pricing](https://www.appointy.com/pricing/), [Zapier: Appointy integrations](https://zapier.com/apps/appointy/integrations), [Appointy home](https://www.appointy.com/) ## How does the Appointy MCP server work? 1. **Sign in to Appointy.** 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 Appointy password, and no booking, approval, move or cancellation goes through until you approve it. ## How to connect Appointy to your AI agent 1. **Sign in to Appointy in a Cloud Browser.** Create a Cotlet account, open Appointy in its Cloud Browser, sign in with your admin 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. Appointy shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned Appointy on after connecting? Refresh the connector and the 9 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, Tool: appointy_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: appointy_write ``` ## All 9 Appointy MCP tools ### Appointments Free slots come from your working hours and bookings. Booking, approving, moving and cancelling wait for your OK; your notification settings decide what the customer hears. - **List appointments** (`list_appointments`, read): Appointments for a day or range, by staff member or service. - **Find free slots** (`find_free_slots`, read): Open times for a service on a day. - **Book appointment** (`book_appointment`, write, asks first): Books a service for a customer with a staff member. - **Approve pending appointment** (`approve_appointment`, write, asks first): Confirms a booking request that waits for approval. - **Reschedule appointment** (`reschedule_appointment`, write, asks first): Moves an appointment to a new time or staff member. - **Cancel appointment** (`cancel_appointment`, write, asks first): Cancels an appointment. ### Customers Search matches name, email and phone, so a returning customer is found before a duplicate is made. - **List customers** (`list_customers`, read): Customers, searchable by name, email or phone. - **Get customer** (`get_customer`, read): One customer with past and upcoming appointments. - **Create customer** (`create_customer`, write): Adds a customer. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/appointy-api-mcp-server#tools ## Who can see my Appointy session, and how do I revoke it? - **What we store.** Your signed-in Appointy profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 9 Appointy tools, never the session cookie. - **What the session sees.** What your login sees: calendar, customers, services, staff. - **What no tool touches.** Payments and refunds, booking page design, plan, deletes. - **If Appointy 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 Appointy 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](https://cotlet.dev/security.md)). ## What happens when Appointy changes? - **12 h** between tests of the Appointy reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a Appointy tool paused for repair When Appointy moves a button on the calendar or renames an appointment status, we fix the tool and your agent calls it the same way. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads pending requests.** For the day you name. 2. **Checks each against the calendar.** Overlaps and staff hours. 3. **Lists clashes for you.** And proposes another time. 4. **Waits, then approves.** The batch shows up in your Cotlet console first. | Action | Undo | |---|---| | Book an appointment | Yes, cancel it | | Approve a request | Cancel it; the confirmation stays sent | | Move an appointment | Move it back; a message already sent stays sent | | Cancel an appointment | Book it again | | Add a customer | Yes, edit it in Appointy | 4 of 9 tools ask first: book_appointment, reschedule_appointment, cancel_appointment, approve_appointment. A new customer reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine. MCP call: ``` { "name": "book_appointment", "arguments": { "customer_id": "CU-31890", "service": "60 min massage", "staff": "Rachel", "start": "2026-11-13T10:00" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/appointy/customers/CU-31890/appointments \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"service":"60 min massage","staff":"Rachel","start":"2026-11-13T10:00"}' ``` Response: ``` { "appointment_id": "AP-662140", "customer": "Olivia Grant", "service": "60 min massage", "staff": "Rachel", "start": "2026-11-13T10:00", "status": "Confirmed" } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/appointy` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the Appointy MCP server cost? **About $35 a month** for a massage studio with 3 therapists, 6,100 credits. Your Appointy plan stays as it is. | Job | Calls | Credits | |---|---|---| | Booking from a message | 3 × 90 | 2,700 | | Pending requests approved | 4 × 26 | 1,040 | | Appointment moved | 3 × 20 | 600 | | Tomorrow's schedule checked | 1 × 26 | 260 | | Cloud Browser, 30 days | | 1,500 | | Total | | 6,100 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on any Appointy plan Appointy publishes no booking counts, so the month is our example. Dollars at the $29 pack rate. ## Appointy MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [Zapier: Appointy](https://zapier.com/apps/appointy/integrations) | Starts workflows on new, updated or cancelled appointments; creates customers. | Cannot book, move, approve or cancel. | | Appointy private API | Full access for your own developer. | Enterprise plan only; you build and host the code. | | By hand | Every screen of Appointy, one booking at a time. | Your front desk's time. | If you only need to copy new bookings into another app, the Zapier triggers do it. To book, approve and reschedule by asking in ChatGPT or Claude, Cotlet works in the Appointy account you already have. ### Appointy MCP setup on GitHub and PyPI Prefer code? Our public repo has a ready Appointy MCP config for Claude Code, ChatGPT and Cursor, an agent skill and a small command-line tool. Add your Cotlet API key and your agent works in your own Appointy account. - MCP config for Claude Code, Cursor and Codex - Agent skill and Cursor rules for Appointy - Clone it and run, Python standard library only - Elastic License 2.0, free in your own business - Code: https://github.com/cotlet-connect/appointy-mcp ## 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 Appointy tools go to contact@cotlet.dev. ## Appointy MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open Appointy under Integrations in the console and sign in to Appointy in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect Appointy to ChatGPT or Claude? Sign up at cotlet.dev, log in to Appointy 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 Appointy account through Cotlet, in their phone apps too. ### What can ChatGPT do in Appointy? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Appointy: book appointments from emails and messages; approve pending booking requests; reschedule when staff are out. 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 Appointy? No. Appointy has no ChatGPT or Claude connector of its own and Appointy has no official MCP server (checked 8 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 Appointy? Yes, with Cotlet. ChatGPT finds the customer, checks free slots for the service and books it with the staff member you name, after your OK. ### Can ChatGPT reschedule appointments in Appointy? Yes, with Cotlet. ChatGPT moves appointments to another time or staff member, for example when someone is out. Each move waits for your OK by default. ### Can ChatGPT approve booking requests in Appointy? Yes, with Cotlet. ChatGPT reads pending requests, checks them against the calendar and confirms the ones you OK. ### Do I need the Appointy Enterprise plan to use Cotlet? No. Cotlet works through your own Appointy sign-in, so it needs no private API, which Appointy lists only on Enterprise. It can do what your plan and login can do. ### Does it send reminders? Appointy sends its own confirmations and reminders by your settings. A booking the agent makes is a normal Appointy booking, so the same reminders go out. ### Is the MCP server different from the REST API? Only in how it is called. Both carry the same 9 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Appointy? No. Cotlet is independent and not affiliated with Appointy. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.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.