Momence MCP Server
Classes, bookings and members for your Momence studio.
Máy chủ MCP được lưu trữ
npx add-mcp 'https://cotlet.dev/mcp/v1/momence'Cài vào Claude Code, Codex, Cursor và nhiều công cụ khác
Tài liệu
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Momence API and MCP server: Let your AI agent handle the studio desk in Momence.
Momence has no MCP server (checked 27 Oct 2026). Its Developer API is self-serve: any studio adds an API client under Apps & Integrations and works as one staff user. It reads members, classes and rosters, books for free, checks in, cancels bookings and freezes memberships. Classes, refunds, renewals and messages are not in it. Cotlet runs 14 Momence tools hosted, over MCP for agents and REST for scripts.
Classes, bookings and members for your Momence studio. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Momence or Xplor
- Page: https://cotlet.dev/integrations/momence-api-mcp-server
What can you automate in Momence?
- Cancel a class and tell everyone booked
- Load a new term as draft series
- Freeze a member who travels
- Refund drop-ins to card or credits
- Check in tonight's roster
- Text students when a spot opens
Does Momence have an MCP server or an API?
- Class sessions, membership products and appointment reservations are read-only in the API. Of our 14 tools it covers 7 in full and 2 in part.
- API tokens expire a few hours after they are issued, even in use. Webhooks exist but are experimental and switched on by Momence support.
- The Zapier app is invite-only, with 5 triggers and no actions. Momence's AI Inbox answers your customers; your own agent cannot call it.
| What you need | Momence API | Zapier | Cotlet |
|---|---|---|---|
| Read classes, rosters and members | Yes | Triggers only | Yes |
| Book, check in, cancel a booking | Free bookings only | No | Yes, bookings after your OK |
| Create or cancel a class | No, read-only | No | Yes |
| Refund a payment | No | No | Card or credits, after your OK |
| Freeze or stop a renewal | Freeze only | No | Both, after your OK |
| Email, SMS or in-app message | No | No | Yes, after your OK |
Checked 27 Oct 2026. Sources: Momence API docs index, Momence API: getting started, Momence API: authentication, Momence API: webhooks basics, Momence Help: Support Agent overview, Carly: Momence API, Zapier triggers
How does Cotlet connect to Momence?
- Sign in to Momence. 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 Momence password, and no cancellation, booking, freeze, refund or message goes out before you approve it.
Connect Momence 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.
- Sign in to Momence in a Cloud Browser. Make a Cotlet account, open Momence in the Cloud Browser we host for you, log in with your own staff account and turn on Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the link. Chat apps show a Cotlet sign-in page. Code editors, n8n and cron jobs send an API key you create in the console.
https://cotlet.dev/mcp/v1 serves every Cotlet app you enable, Momence included. Turn Momence on after the agent is connected and its tools show up once you refresh the connector.
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: momence_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: momence_write
How to use the Momence REST API
Create your Cotlet API key
Create a Cotlet API key with access to Momence and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Momence in Cotlet and enable it for agents. Account access: Your Momence staff account (permissions for classes, freezes, refunds and the Inbox decide what works).
Make your first Momence API request
REST:
curl "https://cotlet.dev/api/v1/momence/classes?from=2026-10-15&to=2026-10-15" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read classes and apply the operation limits
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": "momence",
"tool": "list_classes",
"result": {
"classes": [
{
"class_id": "9182736",
"name": "Vinyasa Flow 60",
"starts_at": "2026-10-15T19:00:00-07:00",
"teacher": "Maya Lee",
"location": "Studio A",
"booked": 14,
"capacity": 18,
"status": "scheduled"
}
]
}
}
Returns classes between two dates in start order, with teacher, location, booked count and whether the class is cancelled. Cancelled classes are hidden unless include_cancelled is true.
Use class_id from each item in get_class_roster and the write tools.
from: First day. Default: today.
to: Last day. Default: 7 days from today.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Momence workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Customers booked into a class and on its waitlist, with check-in status. Use get_class_roster in your configured business report. |
| Make | HTTP > Make a request | Profile, tags, notes, active subscriptions and packs, and upcoming bookings. Use get_customer in your configured business report. |
| Python or Node.js | REST API | Payments from the customer profile (Activity > Payments), newest first. Use list_customer_payments in your configured business report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Momence; 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.
Momence API endpoints and MCP tools
Classes and rosters
A cancelled class stays on the customer schedule marked as cancelled. Drafts made by create_class stay hidden until you publish them on the Schedule page.
- List classes (
list_classes, read): Scheduled classes in a date range, with teacher, location, bookings and status. - Get class roster (
get_class_roster, read): Customers booked into a class and on its waitlist, with check-in status. - Create class (
create_class, write): One-off class or recurring series from a class template, like Classes > Schedule > New Class. - Cancel class (
cancel_class, write, asks first): Cancel one class. It stays on the customer schedule marked as cancelled.
Bookings and check-ins
Late-cancel fees follow your Cancellation Policy setting. A check-in reaches nobody and flips back in one call.
- Book customer (
book_customer, write, asks first): Book a customer into a class, or add them to its waitlist. - Cancel booking (
cancel_booking, write, asks first): Cancel a customer's booking in a class, with credit and notification choices. - Check in customer (
check_in_customer, write): Mark a booking as checked in, or undo the check-in.
Customers and memberships
A freeze cancels the member's future bookings made with that subscription, so the agent lists them before you approve.
- Search customers (
search_customers, read): Find customers by name, email or phone, optionally by tag. - Get customer (
get_customer, read): Profile, tags, notes, active subscriptions and packs, and upcoming bookings. - Freeze membership (
freeze_membership, write, asks first): Freeze a customer's subscription now or on a date, with an optional unfreeze date. - Cancel membership renewal (
cancel_membership_renewal, write, asks first): Cancel Renewal on a subscription now or at a scheduled date, so it expires instead of charging again.
Payments and messages
Refunds and Inbox messages need a staff role allowed to do them. Group messages skip customers who unsubscribed.
- List customer payments (
list_customer_payments, read): Payments from the customer profile (Activity > Payments), newest first. - Refund payment (
refund_payment, write, asks first): Refund a payment as money or as Momence credits; the original purchase stays on record. - Send message (
send_message, write, asks first): Message customers from the Momence Inbox by email, SMS or in-app message.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/momence-api-mcp-server#tools
Who can see my Momence session, and how do I revoke it?
- What we store. Your signed-in Momence profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. 14 Momence tools, no cookie, no login.
- What the session sees. Only what your staff role sees: freezes, refunds and the Inbox follow its permissions.
- What no tool touches. Checkout, prices, payouts, staff, studio settings and deleting classes.
- If Momence signs you out. You get an email with a sign-in link and log in yourself. We never do.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.
Use a staff account rather than the owner login when you can: Momence applies the same permissions in the dashboard and in every tool. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); we have no SOC 2 report or third-party pentest yet.
Is it against Momence's terms? Account safety
with any robot, spider, crawler, scraper, or other manual or automated means or interface to access the Services, retrieve, index, scrape, "data mine" or otherwise gather content or extract user's information; to use or develop any third-party applications that interacts with the Services or users' content or information without Xplor's written consent
Xplor Acceptable Use Policy, section 4, Feb 2022 (read 27 Oct 2026)
Momence has been part of Xplor since 30 Mar 2026, and that policy covers the services of Xplor and its affiliates; a breach counts as "a material breach of the master agreement". Momence's own subscription terms are not public, so we cannot say whether yours point to it. The Momence API Terms (July 2026) also forbid "automated means to access endpoints or data not expressly made available through the Momence APIs". An agent in the dashboard is automated access, so Momence could object. We found no public case of a studio closed for automation (checked 27 Oct 2026).
How we keep your account looking like you:
- Your own staff login, typed in by you
- One Cloud Browser with a steady IP and cookies, like the desk computer
- Cancellations, bookings, freezes, refunds and messages wait for your OK
- No tool exports the whole customer list
- If Momence objects, we pause the Momence tools for everyone within 24 h
Momence emails its cancellation template to everyone booked the moment a class is cancelled. Approve the cancel and the follow-up text together, so a student does not get two different stories.
What happens when Momence changes?
- 12 h between tests of the Momence class, roster and customer reads
- 24 h between tests of cancellations, refunds and messages students would see
- $0 for a call to a Momence tool paused for a fix
Momence changes often: the AI Inbox arrived with the Xplor merger on 30 Mar 2026, the webhook docs were rewritten on 6 Mar 2026 and new API Terms came in July 2026. When a dashboard screen moves, we repair the tool and keep its name. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Saves the roster. Booked names and the waitlist, because un-cancelling a class does not bring sign-ups back.
- Cancels with your note. cancel_class waits in your Cotlet console with the number of students Momence will email.
- Sorts by payment. Pack and subscription holders got their credit back; card drop-ins wait for your refund OK.
- Offers the next class. Checks the open spots, then one text to booked and waitlisted students after your OK.
| Action | Undo |
|---|---|
| Create a class or series | cancel_class; drafts were never seen |
| Cancel a class | Un-cancel in Momence; sign-ups and the sent email stay lost |
| Book a customer | cancel_booking; the booking notice already went out |
| Check in | check_in_customer with checked_in false |
| Freeze a membership | Unfreeze in the dashboard; cancelled bookings do not return |
| Refund or send a message | Cannot be undone |
7 of the 9 write tools ask first. create_class and check_in_customer run at once: a class reaches nobody until someone books it, and a check-in is one call to reverse. Reads never wait. For a scheduled run you can turn the wait off tool by tool.
cancel_class cancels one class, not its series. To end a whole weekly series, the agent cancels each date in your range, or you use Group Recurring in Momence.
MCP call:
{
"name": "create_class",
"arguments": {
"template": "Vinyasa Flow 60",
"teacher": "Maya Lee",
"location": "Studio A",
"starts_at": "2026-10-15T19:00:00-07:00",
"duration_minutes": 60,
"repeat_every_days": 7,
"end_date": "2026-12-31"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/momence/class \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"template":"Vinyasa Flow 60","teacher":"Maya Lee","location":"Studio A","starts_at":"2026-10-15T19:00:00-07:00","duration_minutes":60,"repeat_every_days":7,"end_date":"2026-12-31"}'
Response:
{
"series_id": "ser_48213",
"classes_created": 12,
"first_class_id": "9182736",
"status": "published",
"next_classes": [
"2026-10-15T19:00:00-07:00",
"2026-10-22T19:00:00-07:00"
]
}
A nightly script or a timetable importer can call the same tools over REST at /api/v1/momence, with one key and one price. A call your staff role may not make returns an error and costs nothing. Each tool row above shows its REST path.
How much does the Momence MCP server cost?
About $25 a month for one studio with about 25 classes a week, 4,370 credits. No Momence API client or add-on needed.
| Job | Calls | Credits |
|---|---|---|
| Tomorrow's rosters, every evening | 5 × 30 | 1,500 |
| Book requests from the Inbox | 3 × 20 | 600 |
| Freeze a membership for travel | 3 × 6 | 180 |
| Stop a renewal on request | 3 × 4 | 120 |
| Sick teacher: cancel, 3 refunds, one text | 21 × 2 | 420 |
| Next month's workshops as drafts | 5 × 1 | 50 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 4,370 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on the Momence plan you already pay for
The month is our example: 3 teachers, about 25 classes a week, 20 booking requests, 6 freezes, 4 stopped renewals, two sick days and one batch of workshops. Momence serves over 4,500 businesses and publishes no typical studio size; its pricing page quotes per studio. Dollars at the $29 pack rate.
Momence MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| usefulapi Momence MCP | Hosted MCP on the official API: 16 read and 7 write tools for members, rosters, free bookings, waitlists, check-ins and tags. Free for 50 calls a month, then $9. MIT, pushed 27 Oct 2026. | Needs your API client secret plus a staff email and password. No classes, refunds, freezes, renewals or messages. |
| willdaly/momence-mcp | A repo named for a Momence MCP server. 0 stars, last push 3 Mar 2026. | The README is only a title; no license, no tools listed. |
| salinesolution/momence-api | Unofficial Python client that books classes as a customer. 1 star, last push 1 Apr 2026. | Customer side only; no studio dashboard work. |
| Momence AI Inbox | Momence's own Support Agent answers customers in the Inbox and handles their bookings, freezes and refund requests. | A paid add-on that serves your customers; your own agent cannot give it work. |
If you write your own code and only need members, rosters and check-ins, the free Developer API or the usefulapi server is enough. If customers should get answers in the Inbox, the AI Inbox is Momence's own route. If your agent should cancel classes, load a term, refund, stop renewals and message students, Cotlet does that hosted.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Momence tools go to contact@cotlet.dev.
Momence API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, pick Momence under Integrations in the console and log in to Momence in its Cloud Browser. The trial starts when you sign up and asks for no card.
How do I connect Momence to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Momence 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 Momence account through Cotlet, in their phone apps too.
What can ChatGPT do in Momence?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Momence: check in everyone who showed up; cancel a class and notify students; create recurring classes for a new term. You ask in plain words, and anything that reaches other people waits for your OK first.
Can the agent cancel a class and tell everyone who booked?
Yes. cancel_class cancels the class, and Momence emails every registered customer its cancellation template with your optional note (Momence Help, checked 11 Oct 2026). send_message adds a personal text or in-app message on top.
What staff permissions does it need?
It acts as the staff account you sign in with, so it can only do what that account may do. Freezing needs a staff account with permission to freeze (Momence Help, checked 11 Oct 2026).
Does Momence have webhooks?
Yes, as an experimental feature that Momence support switches on for you: session booked, cancelled, checked in and no-show, membership frozen and renewal failed, among others. Cotlet does not use them. To react to changes, run your agent on a schedule and read the classes or the customer.
Can I keep using the Momence API next to Cotlet?
Yes. Your API clients and Zapier key are separate from the Cloud Browser session, and nothing in Cotlet changes them.
Is the MCP server different from the REST API?
Only in how you call it. Both expose the same 14 tools, inputs and answers, with one API key and one price. Agents call MCP; scripts call REST.
Is Cotlet affiliated with Momence?
No. Cotlet is independent and not affiliated with Momence or Xplor Technologies.
Can I use the Momence 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.
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.