Zen Planner MCP Server
Members, classes, attendance and billing in Zen Planner.
Размещённый MCP-сервер
npx add-mcp 'https://cotlet.dev/mcp/v1/zen-planner'Устанавливается в Claude Code, Codex, Cursor и другие
Документация
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Zen Planner API and MCP server: Let your AI agent run the front desk in Zen Planner.
Zen Planner has no MCP server, and its API is not open to studios (checked 24 Oct 2026). The API lives on the Daxko Partners portal, which says "Contact your Daxko sales representative to request access." Cotlet runs 14 Zen Planner tools hosted, over MCP for agents and REST for scripts.
Read Zen Planner members, class rosters and billing reports through MCP or REST. Connect an agent, an automation platform or your own reporting script.
- Free 7-day trial, no card
- Unofficial, not affiliated with Zen Planner or Daxko
- Page: https://cotlet.dev/integrations/zen-planner-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Zen Planner. Zen Planner is a trademark of its owner. If Zen Planner's own integrations cover what you need, use them first.
What can you automate in Zen Planner?
- Chase last week's failed payments
- Find members who stopped coming
- Add event leads as prospects
- Book and cancel class spots
- Check in a class roster
- Compare revenue by membership type
Does Zen Planner have an MCP server or an API?
- The partner API reaches classes, bookings, check-ins, people and memberships, and sends 13 webhooks. It has no payments, revenue or belt rank endpoints, and it can add prospects but not list them.
- Zen Planner's integrations page lists Zapier under Engage, but Zapier has no public Zen Planner app, and n8n has no Zen Planner node.
- The AI Agent in Zen Planner Engage answers calls and follows up leads inside Zen Planner. Your own agent cannot call it.
| What you need | Daxko partner API | Zen Planner Engage | Cotlet |
|---|---|---|---|
| Members, classes, bookings and check-ins | Yes, in code you build | No | Yes, writes after your OK |
| Failed payments and revenue reports | No | No | Yes, read only |
| Belt and rank promotions | No | No | Yes |
| Your own AI agent can use it | If you write a server | No, its own AI Agent | Yes |
| What you need first | A Daxko sales rep | Engage, from $249 a month | A staff login, any plan |
Checked 24 Oct 2026. Sources: Daxko Partners API documentation (Zen Planner API), Zen Planner integrations, Zen Planner pricing, Zen Planner AI Agent
How does Cotlet connect to Zen Planner?
- Sign in to Zen Planner. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Zen Planner password, and no booking, check-in or new membership is saved until you approve it.
Connect Zen Planner to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Log in to Zen Planner Studio. Create a Cotlet account, log in to Zen Planner Studio in its Cloud Browser with a staff login, then press Enable for agents.
- Add the address to your agent. Paste https://cotlet.dev/mcp/v1 where your agent takes MCP servers or connectors.
- Let the agent in. Chat apps send you to a Cotlet sign-in. Code editors, n8n and scripts take an API key made in the console.
This one address carries Zen Planner and every other app you enable. If you turned Zen Planner on after connecting, refresh the connector so its 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: zen_planner_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: zen_planner_write
How to use the Zen Planner REST API
Create your Cotlet API key
Create a Cotlet API key with access to Zen Planner and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Sign in to Zen Planner in its Cotlet Cloud Browser and enable the app for agents. Use a Studio staff role allowed to see the members, billing and reports you request.
Make your first Zen Planner API request
REST:
curl "https://cotlet.dev/api/v1/zen-planner/members?limit=2" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read members and continue the list
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "zen-planner",
"tool": "list_members",
"result": {
"members": [
{
"person_id": "p253ac9b9",
"name": "Sarah Lee",
"status": "member",
"email": "sarah.lee@example.com",
"phone": "+1 555 0142",
"memberships": [
"Unlimited Monthly"
]
}
],
"next_cursor": null
}
}
Read result.members and pass result.next_cursor unchanged as cursor until null. Keep status, query and modified-after filters fixed.
Member pages default to 50 records, with a maximum of 200. The default member selection excludes prospects and alumni.
Use person_id for member details and dated attendance reads. Compare membership and status changes as well as IDs; class reads require a starting date.
Zen Planner workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read members and member details into a directory report, preserving membership and status changes. |
| Make | HTTP > Make a request | Combine members and dated attendance into a lapsed-attendance review for staff. |
| Python or Node.js | REST API | Read classes and class rosters into a daily coaching briefing without changing attendance. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Zen Planner; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Zen Planner API endpoints and MCP tools
Members and prospects
Lists come in pages of up to 200 people. A new prospect can start the lead follow-up automations your studio has switched on.
- List members (
list_members, read): People in your studio with status, email, phone and memberships. - Get member (
get_member, read): Full profile: contact details, memberships and family members. - List prospects (
list_prospects, read): Leads with source, status and date added. - Create prospect (
create_prospect, write, asks first): Add a lead with contact details and source.
Classes, bookings and attendance
Attendance is one call per member, so a pass over the whole roster costs one call per person.
- List classes (
list_classes, read): Class schedule with time, instructor, capacity and open spots. - Get class roster (
get_class_roster, read): Who reserved and who checked in for one class. - List attendance (
list_attendance, read): A member's class check-ins in a date range, newest first. - Book class (
book_class, write, asks first): Reserve a spot in a class for a member. - Cancel reservation (
cancel_reservation, write, asks first): Cancel a member's class reservation. - Check in member (
check_in_member, write, asks first): Record that a member attended a class.
Billing and reports
Needs a staff role that can see billing and reports. Failed payments are read only: no tool reruns a charge or edits a stored card.
- List failed payments (
list_failed_payments, read): Payments that failed, with member, amount, date and reason. - Get revenue report (
get_revenue_report, read): Revenue for a period, grouped by membership type, class, instructor, location or retail. - Enroll in membership (
enroll_in_membership, write, asks first): Add a membership to a member. Billing follows the membership type.
Belt and skill ranks
Uses the rank structure you set up in Zen Planner's belt and skill tracking.
- Promote rank (
promote_rank, write, asks first): Move a student to their next belt or rank.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/zen-planner-api-mcp-server#tools
Who can see my Zen Planner session, and how do I revoke it?
- What we store. Your logged-in Zen Planner Studio profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. The 14 Zen Planner tools, not the session cookie.
- What the session sees. What your staff role sees: members, classes, billing, reports.
- What no tool touches. Charges, stored cards, refunds, staff, setup and deleting.
- A login of its own. A database owner can add a staff login with only the roles it needs.
- How to cut access. Disable for agents, reset the browser, or untick Login on that staff record.
Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Finds the member. list_members by name, so two Sarahs come back as a question.
- Finds the class. list_classes for tomorrow, with open spots.
- Waits for your OK. The booking shows up in your Cotlet console first.
- Reports the spot. Reservation ID, class, coach, spots left.
| Action | Undo |
|---|---|
| Book a class | cancel_reservation frees the spot |
| Cancel a reservation | Book again while a spot is open |
| Check in a member | Remove the check-in in Zen Planner |
| Create a prospect | Edit or remove the profile in Zen Planner |
| Enroll in a membership | End it in Zen Planner; a charge that already ran needs a refund |
| Promote a rank | Set the old rank back in Zen Planner |
Every one of the 6 write tools asks first, because each changes a member's record and enroll_in_membership starts billing. Reads run at once. Switch the wait off per tool for a scheduled run, such as roster check-ins.
A new prospect can trigger your Zen Planner automations, such as the New Prospect staff task. Check them before a large import.
MCP call:
{
"name": "book_class",
"arguments": {
"class_id": "c7e2a91f",
"person_id": "p253ac9b9"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/zen-planner/persons/p253ac9b9/class/c7e2a91f \
-H "Authorization: Bearer $COTLET_API_KEY"
Tool output:
{
"reservation_id": "r_5510",
"status": "reserved",
"class": {
"name": "CrossFit WOD",
"starts_at": "2026-10-12T06:00:00-04:00",
"instructor": "Coach Alex"
},
"open_spots_left": 3
}
Scripts and cron jobs call the same tools over REST at /api/v1/zen-planner, with the same key and price. A billing tool on a staff role without billing access fails, and a failed call costs nothing. The tools table lists the REST path of each tool.
How much does the Zen Planner MCP server cost?
About $34 a month for a box of about 120 active members, 5,780 credits. Daxko still bills your Zen Planner plan.
| Job | Calls | Credits |
|---|---|---|
| Failed payments call list, weekly | 13 × 4 | 520 |
| Members who stopped coming, weekly (40 regulars) | 47 × 4 | 1,880 |
| Open house leads into prospects | 38 × 1 | 380 |
| Book or cancel a class spot | 3 × 20 | 600 |
| Check in a kids class roster | 11 × 8 | 880 |
| Revenue by membership type, two months | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 5,780 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on Zen Planner Studio, no Engage needed
The month is our example. Two Brain Business puts a group-class gym at 122.5 members (2024), which on Zen Planner is the 101 to 150 tier, $229 a month for Studio. The weekly check covers 40 regulars, not all 120, because attendance is one call per member. Dollars at the $29 pack rate.
Zen Planner MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| blablanumerodeux/zenplannermcp | FastMCP server on one gym's member portal: schedule, book and cancel your own classes. | Member side, one member, no license, 0 stars, last commit 19 Sep 2026. |
| Daxko partner API | Classes, people, memberships, new prospects, 13 webhooks. | Sales rep and an access form first, then you build and host the code. No payments or revenue. |
| Zapier | Listed on Zen Planner's integrations page under Engage. | No public Zen Planner app on Zapier; n8n has no node either. |
| Goodcall | AI phone assistant that answers calls and books into Zen Planner. | Phone calls only, from $79 a month. |
The one Zen Planner MCP server on GitHub books classes for a single member, not for the desk. The partner API is the clean route when a developer and a Daxko agreement are in place, and it still leaves out failed payments and revenue. Cotlet covers the staff jobs from your own login.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Zen Planner tools go to contact@cotlet.dev.
Zen Planner API and MCP: questions
Can I use the Zen Planner API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Sign up free at https://cotlet.dev, open Zen Planner under Integrations in the console and log in to Zen Planner Studio in its Cloud Browser. The trial starts when you sign up and asks for no card.
How do I connect Zen Planner to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Zen Planner 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 Zen Planner account through Cotlet, in their phone apps too.
What can ChatGPT do in Zen Planner?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Zen Planner: follow up on failed payments; book members into classes; find members who stopped coming. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need Daxko API credentials?
No. Cotlet works in your own Zen Planner Studio staff account and does not use the Daxko partner API, whose credentials come only through a Daxko sales rep (checked 11 Oct 2026).
Does Zen Planner have webhooks?
Only for Daxko partners: the partner API sends 13 events, such as a new person, a reservation or a check-in. Cotlet sends no events, so run your agent on a schedule, for example a Monday list_failed_payments pass.
Does it work on the Studio plan?
Yes. Cotlet works in your staff login on any Zen Planner plan, Studio from $99 a month included. The staff role decides what the tools can read: billing and reports need a role that sees them.
Can the agent rerun a failed payment?
No. list_failed_payments only reads. Rerunning a charge or updating a card stays with your staff in Zen Planner.
Is the MCP server different from the REST API?
Only the way in differs. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Zen Planner?
No. Cotlet is independent and not affiliated with Zen Planner or Daxko, LLC.
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.