ClubReady API and MCP server Let your AI agent keep the studio follow-up moving.

ClubReady: ClubReady provides an official API and real-time data notifications. Request a key from ClubReady Support; third-party authorization is approved by the club owner. No vendor-published ClubReady MCP server or ChatGPT or Claude connector was found in the sources checked on 12 November 2026. Checked 12 November 2026. Cotlet provides 168 Cloud Browser capabilities for ChatGPT and Claude in your business account. A trial visit, an unanswered sales lead and an expiring agreement need different next steps. Give the agent the member or prospect and the ClubReady club before asking it to change a record.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with ClubReady
ClubReady logo ClubReady Cloud Browser

168 tools Read and write

Your business account

What can your AI agent do in ClubReady? A trial visit, an unanswered sales lead and an expiring agreement need different next steps. Give the agent the member or prospect and the ClubReady club before asking it to change a record.

  • Review prospects waiting for a follow-up

  • Read upcoming personal-training bookings

  • Check a member's session credits

  • Prepare a message for a selected prospect

  • Read the club's membership reports

  • Find the agreement attached to a member

API access requires approval

Does ClubReady have an MCP server or an API? Vendor connection options, checked 12 November 2026.

ClubReady provides an official API and real-time data notifications. Request a key from ClubReady Support; third-party authorization is approved by the club owner. No vendor-published ClubReady MCP server or ChatGPT or Claude connector was found in the sources checked on 12 November 2026.

  • ClubReady provides an official API and real-time data notifications. Request a key from ClubReady Support; third-party authorization is approved by the club owner.
  • No vendor-published ClubReady MCP server or ChatGPT or Claude connector was found in the sources checked on 12 November 2026.
  • ClubReady Connect supports customer messaging, segments and follow-up automation. Its configured workflows determine which messages run.
The ClubReady API, other options and Cotlet compared
What you need Official connectionBy handCotlet
Account work Documented scope Your staff time Your account screens
Connection setup Vendor access conditions Your own sign-in Sign in, then connect your AI

Among these options, only Cotlet lets your AI agent read and write on every ClubReady screen you can use yourself, from ChatGPT, Claude or any MCP client, without a ClubReady API key or a change to your current ClubReady plan. Sources checked 12 Nov 2026: Vendor connection documentation 1 · Vendor connection documentation 2 · Vendor connection documentation 3 · Vendor connection documentation 4 · Vendor connection documentation 5 · Vendor connection documentation 6 · Vendor connection documentation 7 · Vendor connection documentation 8 · Vendor connection documentation 9 · Vendor connection documentation 10 · Vendor connection documentation 11 · Vendor connection documentation 12

Set up once

How does the ClubReady MCP server work? The ClubReady MCP server by Cotlet: your agent works in your own ClubReady account.

  1. 1Sign in to ClubReady

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the busywork

    In ClubReady, search customer or prospect profiles for the record and period I select. Search customer or prospect profiles. Staff role with Prospect Management: Can Access Prospects Lookup; desktop web; authorized club only.

Cotlet never sees or stores your password. Who can see your session

Any MCP client

How to connect ClubReady to your AI agent

  1. 1

    Sign in to ClubReady in a Cloud Browser. Open ClubReady in your Cotlet Cloud Browser and sign in with your own business account at app.clubready.com/login.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

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

ClubReady shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned ClubReady on after connecting? Refresh the connector and the 168 tools appear.

ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
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"
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: clubready_read
57 read, 111 write

All 168 ClubReady MCP tools

Prospects & Members > Profile7

Documented prospects & members > profile work in ClubReady.

  • search_customer_profiles Search customer or prospect profiles. Staff role with Prospect Management: Can Access Prospects Lookup; desktop web; authorized club only. read

    Search customer or prospect profiles. Staff role with Prospect Management: Can Access Prospects Lookup; desktop web; authorized club only.

    MCP callclubready_read → search_customer_profiles

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-profiles/search

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Prospect Management: Can Access Prospects Lookup; desktop web; authorized club only"
    }
  • read_customer_profile View a customer profile. Staff role with client profile access; desktop web. read

    View a customer profile. Staff role with client profile access; desktop web.

    MCP callclubready_read → read_customer_profile

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-profiles/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client profile access; desktop web"
    }
  • update_customer_contact_details Update customer business-contact details. Staff role with Can Edit Client Profiles. Business-contact fields only (name, address, phone, contact email). Not portal username or password. write

    Update customer business-contact details. Staff role with Can Edit Client Profiles. Business-contact fields only (name, address, phone, contact email). Not portal username or password.

    MCP callclubready_write → update_customer_contact_details

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/customer-contact-details

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Can Edit Client Profiles. Business-contact fields only (name, address, phone, contact email). Not portal username or password"
    }
  • update_customer_emergency_contacts Update customer emergency contacts. Staff role with Can Edit Client Profiles; contact details only, no clinical content. write

    Update customer emergency contacts. Staff role with Can Edit Client Profiles; contact details only, no clinical content.

    MCP callclubready_write → update_customer_emergency_contacts

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/customer-emergency-contacts

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Can Edit Client Profiles; contact details only, no clinical content"
    }
  • update_customer_type Change a customer's membership type. Staff role with Can edit clients membership type. Confirm because it can change entitlements. writeAsks first

    Change a customer's membership type. Staff role with Can edit clients membership type. Confirm because it can change entitlements.

    MCP callclubready_write → update_customer_type

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/customer-type

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Can edit clients membership type. Confirm because it can change entitlements"
    }
  • update_customer_email_preferences Change customer email preferences. Staff role with Can Edit Client Profiles. Confirm because it changes communication consent or delivery. writeAsks first

    Change customer email preferences. Staff role with Can Edit Client Profiles. Confirm because it changes communication consent or delivery.

    MCP callclubready_write → update_customer_email_preferences

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/customer-email-preferences

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Can Edit Client Profiles. Confirm because it changes communication consent or delivery"
    }
  • assign_customer_custom_category Assign a customer custom-category option. Staff role with Can edit client profiles. write

    Assign a customer custom-category option. Staff role with Can edit client profiles.

    MCP callclubready_write → assign_customer_custom_category

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-custom-category/assign

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Can edit client profiles"
    }

Prospects & Members > Adding1

Documented prospects & members > adding work in ClubReady.

  • create_prospect Add a prospect. Staff role with Prospect Management: Can add new prospects. Do not set free-consultation credits or lead types that trigger automation or messages without asking. write

    Add a prospect. Staff role with Prospect Management: Can add new prospects. Do not set free-consultation credits or lead types that trigger automation or messages without asking.

    MCP callclubready_write → create_prospect

    REST endpointPOST https://cotlet.dev/api/v1/clubready/prospects

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Prospect Management: Can add new prospects. Do not set free-consultation credits or lead types that trigger automation or messages without asking"
    }

Setup > Leads1

Documented setup > leads work in ClubReady.

  • configure_prospect_form_fields Configure the Add Lead / prospect form fields. Staff role with Club Setup: Can access add lead form setup. Do not change free-consultation-credit assignment without asking. write

    Configure the Add Lead / prospect form fields. Staff role with Club Setup: Can access add lead form setup. Do not change free-consultation-credit assignment without asking.

    MCP callclubready_write → configure_prospect_form_fields

    REST endpointPOST https://cotlet.dev/api/v1/clubready/prospect-form-fields/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Club Setup: Can access add lead form setup. Do not change free-consultation-credit assignment without asking"
    }

Prospects & Members > Profile > Merging1

Documented prospects & members > profile > merging work in ClubReady.

  • merge_customer_profiles Merge duplicate customer profiles. Start from the profile to keep: All Detail > General > Merge. Agreements, bookings, payments and invoices move; payment profiles do not. Destructive. writeAsks first

    Merge duplicate customer profiles. Start from the profile to keep: All Detail > General > Merge. Agreements, bookings, payments and invoices move; payment profiles do not. Destructive.

    MCP callclubready_write → merge_customer_profiles

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-profiles/merge

    Parameters

    No parameters.

    Example response

    {
      "scope": "Start from the profile to keep: All Detail > General > Merge. Agreements, bookings, payments and invoices move; payment profiles do not. Destructive"
    }

Prospects & Members > Adding/Deleting1

Documented prospects & members > adding/deleting work in ClubReady.

  • delete_customer_profile Delete a prospect or member profile. Capability-level evidence only; Permanent removal; staff permission required. writeAsks first

    Delete a prospect or member profile. Capability-level evidence only; Permanent removal; staff permission required.

    MCP callclubready_write → delete_customer_profile

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/customer-profiles

    Parameters

    No parameters.

    Example response

    {
      "scope": "Capability-level evidence only; Permanent removal; staff permission required"
    }

Setup > Members2

Documented setup > members work in ClubReady.

  • create_custom_category Create a customer custom category. Staff role with setup permissions. write

    Create a customer custom category. Staff role with setup permissions.

    MCP callclubready_write → create_custom_category

    REST endpointPOST https://cotlet.dev/api/v1/clubready/custom-categories

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with setup permissions"
    }
  • create_custom_category_option Add a selectable option to a custom category. Staff role with setup permissions. write

    Add a selectable option to a custom category. Staff role with setup permissions.

    MCP callclubready_write → create_custom_category_option

    REST endpointPOST https://cotlet.dev/api/v1/clubready/custom-category-options

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with setup permissions"
    }

Prospects & Members > Notes, Alerts & Files > Files1

Documented prospects & members > notes, alerts & files > files work in ClubReady.

  • upload_customer_file Upload a file to a customer account. Uploaded files can be visible to the customer in the Wellness Portal. Existing files only: no camera capture, no clinical or medical documents. writeAsks first

    Upload a file to a customer account. Uploaded files can be visible to the customer in the Wellness Portal. Existing files only: no camera capture, no clinical or medical documents.

    MCP callclubready_write → upload_customer_file

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-files

    Parameters

    No parameters.

    Example response

    {
      "scope": "Uploaded files can be visible to the customer in the Wellness Portal. Existing files only: no camera capture, no clinical or medical documents"
    }

Prospects & Members > Check In > Amenities3

Documented prospects & members > check in > amenities work in ClubReady.

  • read_customer_amenities View customer amenities. Staff role with client access. read

    View customer amenities. Staff role with client access.

    MCP callclubready_read → read_customer_amenities

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-amenities/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client access"
    }
  • update_customer_amenities Enable or remove customer amenities. Changes an entitlement; All Detail > General > Amenities. writeAsks first

    Enable or remove customer amenities. Changes an entitlement; All Detail > General > Amenities.

    MCP callclubready_write → update_customer_amenities

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/customer-amenities

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes an entitlement; All Detail > General > Amenities"
    }
  • read_customer_amenity_history Read a customer's amenity history. Staff role with client access. read

    Read a customer's amenity history. Staff role with client access.

    MCP callclubready_read → read_customer_amenity_history

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-amenity-histories/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client access"
    }

Members Lookup2

Documented members lookup work in ClubReady.

  • filter_customers_by_amenity Filter customers by amenity. Staff role with Members Lookup. read

    Filter customers by amenity. Staff role with Members Lookup.

    MCP callclubready_read → filter_customers_by_amenity

    REST endpointGET https://cotlet.dev/api/v1/clubready/customers-by-amenities/filter

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Members Lookup"
    }
  • export_customers_by_amenity Export the amenity-filtered customer list. Retrieval to Excel only; no external transmission. read

    Export the amenity-filtered customer list. Retrieval to Excel only; no external transmission.

    MCP callclubready_read → export_customers_by_amenity

    REST endpointGET https://cotlet.dev/api/v1/clubready/customers-by-amenities/export

    Parameters

    No parameters.

    Example response

    {
      "scope": "Retrieval to Excel only; no external transmission"
    }

Prospects & Members > Check In > Guest Pass2

Documented prospects & members > check in > guest pass work in ClubReady.

  • assign_prospect_guest_pass Issue a guest-pass type to a prospect. The guest-pass feature must be enabled for the club. Changes an entitlement. writeAsks first

    Issue a guest-pass type to a prospect. The guest-pass feature must be enabled for the club. Changes an entitlement.

    MCP callclubready_write → assign_prospect_guest_pass

    REST endpointPOST https://cotlet.dev/api/v1/clubready/prospect-guest-pass/assign

    Parameters

    No parameters.

    Example response

    {
      "scope": "The guest-pass feature must be enabled for the club. Changes an entitlement"
    }
  • activate_prospect_guest_pass Activate an issued guest pass. Changes access; some pass types activate automatically. writeAsks first

    Activate an issued guest pass. Changes access; some pass types activate automatically.

    MCP callclubready_write → activate_prospect_guest_pass

    REST endpointPOST https://cotlet.dev/api/v1/clubready/prospect-guest-pass/activate

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes access; some pass types activate automatically"
    }

Prospects Lookup1

Documented prospects lookup work in ClubReady.

  • filter_prospects_by_guest_pass_status Filter prospects by guest-pass status. Staff role with Prospects Lookup. read

    Filter prospects by guest-pass status. Staff role with Prospects Lookup.

    MCP callclubready_read → filter_prospects_by_guest_pass_status

    REST endpointGET https://cotlet.dev/api/v1/clubready/prospects-by-guest-pass-status/filter

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Prospects Lookup"
    }

Prospects & Members > Notes6

Documented prospects & members > notes work in ClubReady.

  • read_customer_notes View customer notes. Staff role with client note access; notes are internal. read

    View customer notes. Staff role with client note access; notes are internal.

    MCP callclubready_read → read_customer_notes

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-notes/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client note access; notes are internal"
    }
  • filter_customer_notes Filter customer notes by category and date. Staff role with client note access. read

    Filter customer notes by category and date. Staff role with client note access.

    MCP callclubready_read → filter_customer_notes

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-notes/filter

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client note access"
    }
  • create_customer_note Add an internal customer note. Staff role with Can add client note. Notes are not customer-visible. No clinical content. write

    Add an internal customer note. Staff role with Can add client note. Notes are not customer-visible. No clinical content.

    MCP callclubready_write → create_customer_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Can add client note. Notes are not customer-visible. No clinical content"
    }
  • update_customer_note Edit a customer note. Staff role with client note access. write

    Edit a customer note. Staff role with client note access.

    MCP callclubready_write → update_customer_note

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/customer-note

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client note access"
    }
  • create_cross_club_customer_note Add a cross-club-visible (Fitness Related) note. Fitness Related notes may be visible to other clubs. Changes visibility. writeAsks first

    Add a cross-club-visible (Fitness Related) note. Fitness Related notes may be visible to other clubs. Changes visibility.

    MCP callclubready_write → create_cross_club_customer_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/cross-club-customer-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Fitness Related notes may be visible to other clubs. Changes visibility"
    }
  • create_customer_key_note Add a key note to a customer account. Staff role with the dedicated key-note permission. write

    Add a key note to a customer account. Staff role with the dedicated key-note permission.

    MCP callclubready_write → create_customer_key_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-key-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with the dedicated key-note permission"
    }

Members > Search All Notes1

Documented members > search all notes work in ClubReady.

  • search_member_notes Search member notes by keyword. Staff role with notes search access. read

    Search member notes by keyword. Staff role with notes search access.

    MCP callclubready_read → search_member_notes

    REST endpointGET https://cotlet.dev/api/v1/clubready/member-notes/search

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with notes search access"
    }

Prospects & Members > Notes, Alerts & Files > Alerts1

Documented prospects & members > notes, alerts & files > alerts work in ClubReady.

  • create_internal_customer_alert Add an internal customer alert. Leave Notify Customer At Self Check-In off. No clinical content. write

    Add an internal customer alert. Leave Notify Customer At Self Check-In off. No clinical content.

    MCP callclubready_write → create_internal_customer_alert

    REST endpointPOST https://cotlet.dev/api/v1/clubready/internal-customer-alerts

    Parameters

    No parameters.

    Example response

    {
      "scope": "Leave Notify Customer At Self Check-In off. No clinical content"
    }

Prospects & Members > Alerts2

Documented prospects & members > alerts work in ClubReady.

  • configure_customer_checkin_alert_message Set a customer-facing self-check-in alert message. The message is shown to the customer at self check-in. Configuration only, not kiosk use. writeAsks first

    Set a customer-facing self-check-in alert message. The message is shown to the customer at self check-in. Configuration only, not kiosk use.

    MCP callclubready_write → configure_customer_checkin_alert_message

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-checkin-alert-message/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "The message is shown to the customer at self check-in. Configuration only, not kiosk use"
    }
  • remove_customer_alert Remove a customer alert. Requires the delete-alert permission. writeAsks first

    Remove a customer alert. Requires the delete-alert permission.

    MCP callclubready_write → remove_customer_alert

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/customer-alerts

    Parameters

    No parameters.

    Example response

    {
      "scope": "Requires the delete-alert permission"
    }

Prospects & Members > Agreements > Files2

Documented prospects & members > agreements > files work in ClubReady.

  • upload_agreement_file Attach an existing file to an agreement. Check who can see agreement files before attaching a private document. writeAsks first

    Attach an existing file to an agreement. Check who can see agreement files before attaching a private document.

    MCP callclubready_write → upload_agreement_file

    REST endpointPOST https://cotlet.dev/api/v1/clubready/agreement-files

    Parameters

    No parameters.

    Example response

    {
      "scope": "Check who can see agreement files before attaching a private document"
    }
  • delete_agreement_file Delete an agreement attachment. Requires the dedicated delete-file permission. writeAsks first

    Delete an agreement attachment. Requires the dedicated delete-file permission.

    MCP callclubready_write → delete_agreement_file

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/agreement-files

    Parameters

    No parameters.

    Example response

    {
      "scope": "Requires the dedicated delete-file permission"
    }

Prospects & Members > Tasks2

Documented prospects & members > tasks work in ClubReady.

  • read_customer_tasks View customer tasks. Staff role with Member Management: Can access member options. read

    View customer tasks. Staff role with Member Management: Can access member options.

    MCP callclubready_read → read_customer_tasks

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-tasks/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Member Management: Can access member options"
    }
  • create_customer_task Create an assigned customer task (also the to-do item). Fields: task name, due date, assigned staff, optional colour. Purpose and priority are reported by pass 3 only. A Call option only puts the phone number in the task and does not place a call. Customer to-do is an alias of this function. write

    Create an assigned customer task (also the to-do item). Fields: task name, due date, assigned staff, optional colour. Purpose and priority are reported by pass 3 only. A Call option only puts the phone number in the task and does not place a call. Customer to-do is an alias of this function.

    MCP callclubready_write → create_customer_task

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-tasks

    Parameters

    No parameters.

    Example response

    {
      "scope": "Fields: task name, due date, assigned staff, optional colour. Purpose and priority are reported by pass 3 only. A Call option only puts the phone number in the task and does not place a call. Customer to-do is an alias of this function"
    }

Prospects & Members > Work It1

Documented prospects & members > work it work in ClubReady.

  • work_customer_task Work a customer task in Work It. Completing a task with no outreach is internal. Any SMS or Fast Book inside Work It needs approval. writeAsks first

    Work a customer task in Work It. Completing a task with no outreach is internal. Any SMS or Fast Book inside Work It needs approval.

    MCP callclubready_write → work_customer_task

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-task/work

    Parameters

    No parameters.

    Example response

    {
      "scope": "Completing a task with no outreach is internal. Any SMS or Fast Book inside Work It needs approval"
    }

Prospects & Members > All Detail / Work It1

Documented prospects & members > all detail / work it work in ClubReady.

  • send_customer_sms Send a text message to a customer. Needs SMS enabled. Basic Work It SMS is disabled when Connect is enabled. External send. writeAsks first

    Send a text message to a customer. Needs SMS enabled. Basic Work It SMS is disabled when Connect is enabled. External send.

    MCP callclubready_write → send_customer_sms

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-sms

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs SMS enabled. Basic Work It SMS is disabled when Connect is enabled. External send"
    }

Bookings - New UI7

Documented bookings - new ui work in ClubReady.

  • create_prospect_from_schedule Add a prospect from the Bookings screen. Optional Key Note field; do not trigger automation or messages. write

    Add a prospect from the Bookings screen. Optional Key Note field; do not trigger automation or messages.

    MCP callclubready_write → create_prospect_from_schedule

    REST endpointPOST https://cotlet.dev/api/v1/clubready/prospect-from-schedules

    Parameters

    No parameters.

    Example response

    {
      "scope": "Optional Key Note field; do not trigger automation or messages"
    }
  • create_service_booking Schedule a one-to-one service booking. Staff booking permission. Booking commitment. writeAsks first

    Schedule a one-to-one service booking. Staff booking permission. Booking commitment.

    MCP callclubready_write → create_service_booking

    REST endpointPOST https://cotlet.dev/api/v1/clubready/service-bookings

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff booking permission. Booking commitment"
    }
  • create_service_booking_unavailable_time Book a service in an unavailable time. Requires an additional staff permission. writeAsks first

    Book a service in an unavailable time. Requires an additional staff permission.

    MCP callclubready_write → create_service_booking_unavailable_time

    REST endpointPOST https://cotlet.dev/api/v1/clubready/service-booking-unavailable-times

    Parameters

    No parameters.

    Example response

    {
      "scope": "Requires an additional staff permission"
    }
  • create_service_booking_internal_note Add a service-booking internal note. Staff-only note; the client cannot view it. write

    Add a service-booking internal note. Staff-only note; the client cannot view it.

    MCP callclubready_write → create_service_booking_internal_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/service-booking-internal-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff-only note; the client cannot view it"
    }
  • create_class_event Schedule a class event. Instructor, class type and time; physical or virtual. Booking commitment. writeAsks first

    Schedule a class event. Instructor, class type and time; physical or virtual. Booking commitment.

    MCP callclubready_write → create_class_event

    REST endpointPOST https://cotlet.dev/api/v1/clubready/class-events

    Parameters

    No parameters.

    Example response

    {
      "scope": "Instructor, class type and time; physical or virtual. Booking commitment"
    }
  • create_recurring_class_events Schedule recurring classes. Recurrence and series-ending controls. Booking commitment. writeAsks first

    Schedule recurring classes. Recurrence and series-ending controls. Booking commitment.

    MCP callclubready_write → create_recurring_class_events

    REST endpointPOST https://cotlet.dev/api/v1/clubready/recurring-class-events

    Parameters

    No parameters.

    Example response

    {
      "scope": "Recurrence and series-ending controls. Booking commitment"
    }
  • create_virtual_class_event Schedule a virtual class. Requires a join link. writeAsks first

    Schedule a virtual class. Requires a join link.

    MCP callclubready_write → create_virtual_class_event

    REST endpointPOST https://cotlet.dev/api/v1/clubready/virtual-class-events

    Parameters

    No parameters.

    Example response

    {
      "scope": "Requires a join link"
    }

Bookings - New UI > Email Notifications3

Documented bookings - new ui > email notifications work in ClubReady.

  • send_service_booking_confirmation Send a service-booking confirmation message. Optional checkboxes on the booking form. External send. writeAsks first

    Send a service-booking confirmation message. Optional checkboxes on the booking form. External send.

    MCP callclubready_write → send_service_booking_confirmation

    REST endpointPOST https://cotlet.dev/api/v1/clubready/service-booking-confirmations

    Parameters

    No parameters.

    Example response

    {
      "scope": "Optional checkboxes on the booking form. External send"
    }
  • send_class_roster_email Email selected class attendees. Sent to selected roster members only. External send. writeAsks first

    Email selected class attendees. Sent to selected roster members only. External send.

    MCP callclubready_write → send_class_roster_email

    REST endpointPOST https://cotlet.dev/api/v1/clubready/class-roster-emails

    Parameters

    No parameters.

    Example response

    {
      "scope": "Sent to selected roster members only. External send"
    }
  • send_booking_cancellation_notification Send a booking-cancellation notification. External send. The cancellation itself also needs approval. writeAsks first

    Send a booking-cancellation notification. External send. The cancellation itself also needs approval.

    MCP callclubready_write → send_booking_cancellation_notification

    REST endpointPOST https://cotlet.dev/api/v1/clubready/booking-cancellation-notifications

    Parameters

    No parameters.

    Example response

    {
      "scope": "External send. The cancellation itself also needs approval"
    }

Bookings - New UI > Notes4

Documented bookings - new ui > notes work in ClubReady.

  • read_booking_notes View booking notes. Separate from customer-account notes; staff only. read

    View booking notes. Separate from customer-account notes; staff only.

    MCP callclubready_read → read_booking_notes

    REST endpointGET https://cotlet.dev/api/v1/clubready/booking-notes/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Separate from customer-account notes; staff only"
    }
  • create_booking_note Add a booking note. Needs note type, subject and text. write

    Add a booking note. Needs note type, subject and text.

    MCP callclubready_write → create_booking_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/booking-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs note type, subject and text"
    }
  • update_booking_note Edit a booking note. Three-dot menu > Edit > Save. write

    Edit a booking note. Three-dot menu > Edit > Save.

    MCP callclubready_write → update_booking_note

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/booking-note

    Parameters

    No parameters.

    Example response

    {
      "scope": "Three-dot menu > Edit > Save"
    }
  • delete_booking_note Delete a booking note. Permanent. writeAsks first

    Delete a booking note. Permanent.

    MCP callclubready_write → delete_booking_note

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/booking-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Permanent"
    }

Bookings - New UI > Cross-Club Bookings2

Documented bookings - new ui > cross-club bookings work in ClubReady.

  • create_cross_club_class_booking Book another club's member into a class. Class and location must be enabled for cross-club participation. writeAsks first

    Book another club's member into a class. Class and location must be enabled for cross-club participation.

    MCP callclubready_write → create_cross_club_class_booking

    REST endpointPOST https://cotlet.dev/api/v1/clubready/cross-club-class-bookings

    Parameters

    No parameters.

    Example response

    {
      "scope": "Class and location must be enabled for cross-club participation"
    }
  • create_cross_club_service_booking Book another club's member into a service. Location and service must be enabled for cross-club booking. writeAsks first

    Book another club's member into a service. Location and service must be enabled for cross-club booking.

    MCP callclubready_write → create_cross_club_service_booking

    REST endpointPOST https://cotlet.dev/api/v1/clubready/cross-club-service-bookings

    Parameters

    No parameters.

    Example response

    {
      "scope": "Location and service must be enabled for cross-club booking"
    }

Bookings - New UI > Text Notifications1

Documented bookings - new ui > text notifications work in ClubReady.

  • send_class_roster_text Text selected class attendees. Needs SMS enabled. External send. writeAsks first

    Text selected class attendees. Needs SMS enabled. External send.

    MCP callclubready_write → send_class_roster_text

    REST endpointPOST https://cotlet.dev/api/v1/clubready/class-roster-texts

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs SMS enabled. External send"
    }

Bookings > Schedule Sharing1

Documented bookings > schedule sharing work in ClubReady.

  • change_schedule_sharing_visibility Share a customer's booking schedule with another client. Changes who can view the schedule. writeAsks first

    Share a customer's booking schedule with another client. Changes who can view the schedule.

    MCP callclubready_write → change_schedule_sharing_visibility

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/schedule-sharing-visibility

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes who can view the schedule"
    }

Setup > Scheduling > Services1

Documented setup > scheduling > services work in ClubReady.

  • create_service_type Create a bookable service type. Setup permission. Controls what customers can book. writeAsks first

    Create a bookable service type. Setup permission. Controls what customers can book.

    MCP callclubready_write → create_service_type

    REST endpointPOST https://cotlet.dev/api/v1/clubready/service-types

    Parameters

    No parameters.

    Example response

    {
      "scope": "Setup permission. Controls what customers can book"
    }

Bookings & Session Credits11

Documented bookings & session credits work in ClubReady.

  • read_customer_session_credit_status View customer session credits and booking-credit status. Staff role with client booking access. read

    View customer session credits and booking-credit status. Staff role with client booking access.

    MCP callclubready_read → read_customer_session_credit_status

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-session-credit-status/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client booking access"
    }
  • add_customer_session_credits Manually add session credits. Free credits can create an invoice and affect trainer payroll. writeAsks first

    Manually add session credits. Free credits can create an invoice and affect trainer payroll.

    MCP callclubready_write → add_customer_session_credits

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-session-credits

    Parameters

    No parameters.

    Example response

    {
      "scope": "Free credits can create an invoice and affect trainer payroll"
    }
  • reassign_completed_booking_credit Reassign the credit used by a completed booking. Affects booking and financial attribution. writeAsks first

    Reassign the credit used by a completed booking. Affects booking and financial attribution.

    MCP callclubready_write → reassign_completed_booking_credit

    REST endpointPOST https://cotlet.dev/api/v1/clubready/completed-booking-credit/reassign

    Parameters

    No parameters.

    Example response

    {
      "scope": "Affects booking and financial attribution"
    }
  • delete_customer_session_credit Delete a session credit. Destructive; removes an entitlement. writeAsks first

    Delete a session credit. Destructive; removes an entitlement.

    MCP callclubready_write → delete_customer_session_credit

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/customer-session-credits

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive; removes an entitlement"
    }
  • bulk_delete_customer_session_credits Delete selected session credits in bulk. Destructive; removes entitlements. writeAsks first

    Delete selected session credits in bulk. Destructive; removes entitlements.

    MCP callclubready_write → bulk_delete_customer_session_credits

    REST endpointPOST https://cotlet.dev/api/v1/clubready/delete-customer-session-credits/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive; removes entitlements"
    }
  • change_session_credit_expiration Change a session-credit expiry date. Restoring a lost credit can duplicate trainer pay. writeAsks first

    Change a session-credit expiry date. Restoring a lost credit can duplicate trainer pay.

    MCP callclubready_write → change_session_credit_expiration

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/session-credit-expiration

    Parameters

    No parameters.

    Example response

    {
      "scope": "Restoring a lost credit can duplicate trainer pay"
    }
  • change_session_credit_type Change a session credit's type. Changes an entitlement. writeAsks first

    Change a session credit's type. Changes an entitlement.

    MCP callclubready_write → change_session_credit_type

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/session-credit-type

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes an entitlement"
    }
  • bulk_change_session_credit_type Change multiple credit types at once. Changes entitlements. writeAsks first

    Change multiple credit types at once. Changes entitlements.

    MCP callclubready_write → bulk_change_session_credit_type

    REST endpointPOST https://cotlet.dev/api/v1/clubready/change-session-credit-type/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes entitlements"
    }
  • hold_customer_session_credits Place session credits on hold. Held credits cannot be used for booking. writeAsks first

    Place session credits on hold. Held credits cannot be used for booking.

    MCP callclubready_write → hold_customer_session_credits

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-session-credits/hold

    Parameters

    No parameters.

    Example response

    {
      "scope": "Held credits cannot be used for booking"
    }
  • release_customer_session_credit_hold Release held session credits. Restores credit use. writeAsks first

    Release held session credits. Restores credit use.

    MCP callclubready_write → release_customer_session_credit_hold

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-session-credit-hold/release

    Parameters

    No parameters.

    Example response

    {
      "scope": "Restores credit use"
    }
  • tie_credit_to_unpaid_booking Assign available credit to an unpaid booking. Booking and financial effect. writeAsks first

    Assign available credit to an unpaid booking. Booking and financial effect.

    MCP callclubready_write → tie_credit_to_unpaid_booking

    REST endpointPOST https://cotlet.dev/api/v1/clubready/credit-to-unpaid-booking/tie

    Parameters

    No parameters.

    Example response

    {
      "scope": "Booking and financial effect"
    }

Setup > Scheduling1

Documented setup > scheduling work in ClubReady.

  • configure_session_credit_cleanup Configure automatic credit-to-booking cleanup. Setup permission. Daily automation. writeAsks first

    Configure automatic credit-to-booking cleanup. Setup permission. Daily automation.

    MCP callclubready_write → configure_session_credit_cleanup

    REST endpointPOST https://cotlet.dev/api/v1/clubready/session-credit-cleanup/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Setup permission. Daily automation"
    }

Bookings & Session Credits > Sharing2

Documented bookings & session credits > sharing work in ClubReady.

  • read_session_credit_sharing View customer session-credit sharing. Staff role with client booking access. read

    View customer session-credit sharing. Staff role with client booking access.

    MCP callclubready_read → read_session_credit_sharing

    REST endpointGET https://cotlet.dev/api/v1/clubready/session-credit-sharings/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with client booking access"
    }
  • configure_session_credit_sharing Share one customer's credits with another. All Detail > Bookings > Session Credit Sharing; not every unlimited membership qualifies. Entitlement change. writeAsks first

    Share one customer's credits with another. All Detail > Bookings > Session Credit Sharing; not every unlimited membership qualifies. Entitlement change.

    MCP callclubready_write → configure_session_credit_sharing

    REST endpointPOST https://cotlet.dev/api/v1/clubready/session-credit-sharing/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "All Detail > Bookings > Session Credit Sharing; not every unlimited membership qualifies. Entitlement change"
    }

Prospects & Members > Billing6

Documented prospects & members > billing work in ClubReady.

  • read_customer_invoices_payments View customer invoices. Needs Can view client billing information. Invoice list verified; the Payments view was not read. read

    View customer invoices. Needs Can view client billing information. Invoice list verified; the Payments view was not read.

    MCP callclubready_read → read_customer_invoices_payments

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-invoices-payments/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs Can view client billing information. Invoice list verified; the Payments view was not read"
    }
  • create_customer_invoice Create a manual customer invoice. Financial obligation. Package invoices can change membership expiry or credits. writeAsks first

    Create a manual customer invoice. Financial obligation. Package invoices can change membership expiry or credits.

    MCP callclubready_write → create_customer_invoice

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-invoices

    Parameters

    No parameters.

    Example response

    {
      "scope": "Financial obligation. Package invoices can change membership expiry or credits"
    }
  • change_invoice_due_date Change an unpaid invoice's due date. Unpaid invoices only. Financial change. writeAsks first

    Change an unpaid invoice's due date. Unpaid invoices only. Financial change.

    MCP callclubready_write → change_invoice_due_date

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/invoice-due-date

    Parameters

    No parameters.

    Example response

    {
      "scope": "Unpaid invoices only. Financial change"
    }
  • adjust_customer_invoice Adjust an unpaid invoice amount. Unpaid invoices only. Financial change. writeAsks first

    Adjust an unpaid invoice amount. Unpaid invoices only. Financial change.

    MCP callclubready_write → adjust_customer_invoice

    REST endpointPOST https://cotlet.dev/api/v1/clubready/customer-invoice/adjust

    Parameters

    No parameters.

    Example response

    {
      "scope": "Unpaid invoices only. Financial change"
    }
  • add_invoice_note Add an invoice note. Internal note. write

    Add an invoice note. Internal note.

    MCP callclubready_write → add_invoice_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/invoice-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Internal note"
    }

Prospects & Members > Refunds & Credits1

Documented prospects & members > refunds & credits work in ClubReady.

  • refund_membership_invoice Refund a membership invoice. Money movement. Cash or written-check fulfilment is a physical club step and not delegated. writeAsks first

    Refund a membership invoice. Money movement. Cash or written-check fulfilment is a physical club step and not delegated.

    MCP callclubready_write → refund_membership_invoice

    REST endpointPOST https://cotlet.dev/api/v1/clubready/membership-invoice/refund

    Parameters

    No parameters.

    Example response

    {
      "scope": "Money movement. Cash or written-check fulfilment is a physical club step and not delegated"
    }

Setup > Products1

Documented setup > products work in ClubReady.

  • configure_retail_product Set up a retail product. Setup permission. write

    Set up a retail product. Setup permission.

    MCP callclubready_write → configure_retail_product

    REST endpointPOST https://cotlet.dev/api/v1/clubready/retail-product/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Setup permission"
    }

Setup > Products > Current Inventory1

Documented setup > products > current inventory work in ClubReady.

  • read_current_inventory View current inventory. Staff role with inventory access. read

    View current inventory. Staff role with inventory access.

    MCP callclubready_read → read_current_inventory

    REST endpointGET https://cotlet.dev/api/v1/clubready/current-inventories/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with inventory access"
    }

Setup > Automation / Work It1

Documented setup > automation / work it work in ClubReady.

  • read_customer_automation_history View a customer's automation history and upcoming actions. Staff role with Work It access. read

    View a customer's automation history and upcoming actions. Staff role with Work It access.

    MCP callclubready_read → read_customer_automation_history

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-automation-histories/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Work It access"
    }

Setup > Automation3

Documented setup > automation work in ClubReady.

  • create_disabled_automation_rule Create an inactive automation rule. Save with the rule OFF. Rules can assign tasks, send messages or change status. write

    Create an inactive automation rule. Save with the rule OFF. Rules can assign tasks, send messages or change status.

    MCP callclubready_write → create_disabled_automation_rule

    REST endpointPOST https://cotlet.dev/api/v1/clubready/disabled-automation-rules

    Parameters

    No parameters.

    Example response

    {
      "scope": "Save with the rule OFF. Rules can assign tasks, send messages or change status"
    }
  • enable_business_automation_rule Enable an automation rule. Starts rule execution that may message customers or change records. writeAsks first

    Enable an automation rule. Starts rule execution that may message customers or change records.

    MCP callclubready_write → enable_business_automation_rule

    REST endpointPOST https://cotlet.dev/api/v1/clubready/business-automation-rule/enable

    Parameters

    No parameters.

    Example response

    {
      "scope": "Starts rule execution that may message customers or change records"
    }
  • disable_business_automation_rule Disable an automation rule. Changes future automated behaviour. writeAsks first

    Disable an automation rule. Changes future automated behaviour.

    MCP callclubready_write → disable_business_automation_rule

    REST endpointPOST https://cotlet.dev/api/v1/clubready/business-automation-rule/disable

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes future automated behaviour"
    }

Setup > Misc > Add Lead API / widget3

Documented setup > misc > add lead api / widget work in ClubReady.

  • read_lead_widget_code Retrieve generated lead-widget HTML. Retrieval only. Publishing the widget on a website is a separate publication needing approval. read

    Retrieve generated lead-widget HTML. Retrieval only. Publishing the widget on a website is a separate publication needing approval.

    MCP callclubready_read → read_lead_widget_code

    REST endpointGET https://cotlet.dev/api/v1/clubready/lead-widget-codes/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Retrieval only. Publishing the widget on a website is a separate publication needing approval"
    }
  • configure_lead_widget_fields Configure lead-widget fields. Referral list, phone destination and return page. write

    Configure lead-widget fields. Referral list, phone destination and return page.

    MCP callclubready_write → configure_lead_widget_fields

    REST endpointPOST https://cotlet.dev/api/v1/clubready/lead-widget-fields/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Referral list, phone destination and return page"
    }
  • require_lead_referral_source Require referral-source capture on lead intake. Set the referral question and Mandatory to Yes. write

    Require referral-source capture on lead intake. Set the referral question and Mandatory to Yes.

    MCP callclubready_write → require_lead_referral_source

    REST endpointPOST https://cotlet.dev/api/v1/clubready/lead-referral-source/require

    Parameters

    No parameters.

    Example response

    {
      "scope": "Set the referral question and Mandatory to Yes"
    }

Setup > Misc > Add Lead API3

Documented setup > misc > add lead api work in ClubReady.

  • configure_lead_welcome_message Configure a lead welcome message. Causes outbound messages to new leads. writeAsks first

    Configure a lead welcome message. Causes outbound messages to new leads.

    MCP callclubready_write → configure_lead_welcome_message

    REST endpointPOST https://cotlet.dev/api/v1/clubready/lead-welcome-message/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Causes outbound messages to new leads"
    }
  • configure_lead_free_package Configure a free package for new leads. Grants an entitlement to every new lead. writeAsks first

    Configure a free package for new leads. Grants an entitlement to every new lead.

    MCP callclubready_write → configure_lead_free_package

    REST endpointPOST https://cotlet.dev/api/v1/clubready/lead-free-package/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Grants an entitlement to every new lead"
    }
  • enable_external_lead_api Enable external lead intake (Add Lead API). Opens an external intake path; an access change. writeAsks first

    Enable external lead intake (Add Lead API). Opens an external intake path; an access change.

    MCP callclubready_write → enable_external_lead_api

    REST endpointPOST https://cotlet.dev/api/v1/clubready/external-lead-api/enable

    Parameters

    No parameters.

    Example response

    {
      "scope": "Opens an external intake path; an access change"
    }

Main > Widgets1

Documented main > widgets work in ClubReady.

  • add_referral_prospect_via_widget Add a referred prospect with the Referrals widget. Required fields: Referred By, name, gender, cell phone. Welcome or free-credit effects are not ruled out. writeAsks first

    Add a referred prospect with the Referrals widget. Required fields: Referred By, name, gender, cell phone. Welcome or free-credit effects are not ruled out.

    MCP callclubready_write → add_referral_prospect_via_widget

    REST endpointPOST https://cotlet.dev/api/v1/clubready/referral-prospect-via-widgets

    Parameters

    No parameters.

    Example response

    {
      "scope": "Required fields: Referred By, name, gender, cell phone. Welcome or free-credit effects are not ruled out"
    }

Main > Club News5

Documented main > club news work in ClubReady.

  • read_club_news View current or past club news. Staff role with Club News access. read

    View current or past club news. Staff role with Club News access.

    MCP callclubready_read → read_club_news

    REST endpointGET https://cotlet.dev/api/v1/clubready/club-news/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with Club News access"
    }
  • publish_club_news Publish club news. Can be visible to members in the Wellness Portal. Publication. writeAsks first

    Publish club news. Can be visible to members in the Wellness Portal. Publication.

    MCP callclubready_write → publish_club_news

    REST endpointPOST https://cotlet.dev/api/v1/clubready/club-news/publish

    Parameters

    No parameters.

    Example response

    {
      "scope": "Can be visible to members in the Wellness Portal. Publication"
    }
  • update_published_club_news Edit existing club news. Changes published content. writeAsks first

    Edit existing club news. Changes published content.

    MCP callclubready_write → update_published_club_news

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/published-club-news

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes published content"
    }
  • delete_club_news Delete club news. Destructive; past news only. writeAsks first

    Delete club news. Destructive; past news only.

    MCP callclubready_write → delete_club_news

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/club-news

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive; past news only"
    }
  • change_club_news_audience Change a news item's audience. Changes member visibility via For Employees Only. writeAsks first

    Change a news item's audience. Changes member visibility via For Employees Only.

    MCP callclubready_write → change_club_news_audience

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/club-news-audience

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes member visibility via For Employees Only"
    }

Main > Check-In Monitor3

Documented main > check-in monitor work in ClubReady.

  • read_checkin_monitor View the Check-In Monitor. Staff role with monitor access. read

    View the Check-In Monitor. Staff role with monitor access.

    MCP callclubready_read → read_checkin_monitor

    REST endpointGET https://cotlet.dev/api/v1/clubready/checkin-monitors/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with monitor access"
    }
  • manual_check_in Record a present customer's manual check-in. Typed name, phone, ID or barcode lookup only. Requires a stated actual presence. No physical scan and no entry of customer PINs. writeAsks first

    Record a present customer's manual check-in. Typed name, phone, ID or barcode lookup only. Requires a stated actual presence. No physical scan and no entry of customer PINs.

    MCP callclubready_write → manual_check_in

    REST endpointPOST https://cotlet.dev/api/v1/clubready/check-in/manual

    Parameters

    No parameters.

    Example response

    {
      "scope": "Typed name, phone, ID or barcode lookup only. Requires a stated actual presence. No physical scan and no entry of customer PINs"
    }
  • add_checkin_monitor_staff_note Post a Staff Note to Check-In Monitor staff. Message shown to staff watching the monitor; it is not a private record. writeAsks first

    Post a Staff Note to Check-In Monitor staff. Message shown to staff watching the monitor; it is not a private record.

    MCP callclubready_write → add_checkin_monitor_staff_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/checkin-monitor-staff-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Message shown to staff watching the monitor; it is not a private record"
    }

Reports > Sales1

Documented reports > sales work in ClubReady.

  • read_past_due_report Read the Past Due report. Staff role with report access. Columns and filters not read. read

    Read the Past Due report. Staff role with report access. Columns and filters not read.

    MCP callclubready_read → read_past_due_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/past-due-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access. Columns and filters not read"
    }

Reports > Intelligence2

Documented reports > intelligence work in ClubReady.

  • read_referrals_report Read the Referrals report. Staff role with report access. read

    Read the Referrals report. Staff role with report access.

    MCP callclubready_read → read_referrals_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/referrals-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • export_referrals_report Export the Referrals report. CSV, PDF or Excel export for this report only; not generalized to other reports. read

    Export the Referrals report. CSV, PDF or Excel export for this report only; not generalized to other reports.

    MCP callclubready_read → export_referrals_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/referrals-reports/export

    Parameters

    No parameters.

    Example response

    {
      "scope": "CSV, PDF or Excel export for this report only; not generalized to other reports"
    }

Reports > Products3

Documented reports > products work in ClubReady.

  • read_inventory_report Read the Inventory report. Staff role with report access. read

    Read the Inventory report. Staff role with report access.

    MCP callclubready_read → read_inventory_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/inventory-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_inventory_change_log_report Read or export the Inventory Change Log. Excel report. read

    Read or export the Inventory Change Log. Excel report.

    MCP callclubready_read → read_inventory_change_log_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/inventory-change-log-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Excel report"
    }
  • read_manual_inventory_count_report Read or export the Manual Inventory Count report. Report retrieval, not a physical stock count. read

    Read or export the Manual Inventory Count report. Report retrieval, not a physical stock count.

    MCP callclubready_read → read_manual_inventory_count_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/manual-inventory-count-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Report retrieval, not a physical stock count"
    }

Reports > Scheduling2

Documented reports > scheduling work in ClubReady.

  • read_business_plan_report Read the Business Plan report. Staff role with report access. read

    Read the Business Plan report. Staff role with report access.

    MCP callclubready_read → read_business_plan_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/business-plan-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • export_business_plan_report Export the Business Plan report. CSV, PDF or Excel; no external transmission. read

    Export the Business Plan report. CSV, PDF or Excel; no external transmission.

    MCP callclubready_read → export_business_plan_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/business-plan-reports/export

    Parameters

    No parameters.

    Example response

    {
      "scope": "CSV, PDF or Excel; no external transmission"
    }

Reports > Staff14

Documented reports > staff work in ClubReady.

  • read_commission_payroll_report Read or export Commission and Payroll reporting. Staff role with payroll report access. Reporting only, not payroll execution. read

    Read or export Commission and Payroll reporting. Staff role with payroll report access. Reporting only, not payroll execution.

    MCP callclubready_read → read_commission_payroll_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/commission-payroll-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with payroll report access. Reporting only, not payroll execution"
    }
  • read_commissions_report Read the Commissions report. Staff role with report access. read

    Read the Commissions report. Staff role with report access.

    MCP callclubready_read → read_commissions_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/commissions-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_contact_log_report Read the Contact Log report. No outreach authorized. read

    Read the Contact Log report. No outreach authorized.

    MCP callclubready_read → read_contact_log_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/contact-log-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "No outreach authorized"
    }
  • read_disciplinary_actions_report Read the Disciplinary Actions report. Sensitive personnel data; permission-bound. read

    Read the Disciplinary Actions report. Sensitive personnel data; permission-bound.

    MCP callclubready_read → read_disciplinary_actions_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/disciplinary-actions-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Sensitive personnel data; permission-bound"
    }
  • read_draft_commission_report Read the Draft Commission report. No commission edits. read

    Read the Draft Commission report. No commission edits.

    MCP callclubready_read → read_draft_commission_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/draft-commission-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "No commission edits"
    }
  • read_manual_credits_by_staff_report Read the Manual Credits By Staff report. Staff role with report access. read

    Read the Manual Credits By Staff report. Staff role with report access.

    MCP callclubready_read → read_manual_credits_by_staff_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/manual-credits-by-staff-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_packages_sold_report Read the Packages Sold report. Staff role with report access. read

    Read the Packages Sold report. Staff role with report access.

    MCP callclubready_read → read_packages_sold_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/packages-sold-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_session_payroll_report Read the Session Payroll report. Reporting only. read

    Read the Session Payroll report. Reporting only.

    MCP callclubready_read → read_session_payroll_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/session-payroll-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Reporting only"
    }
  • read_staff_gross_sales_report Read the Staff Gross Sales report. Staff role with report access. read

    Read the Staff Gross Sales report. Staff role with report access.

    MCP callclubready_read → read_staff_gross_sales_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-gross-sales-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_staff_list_report Read the Staff List report. Staff role with report access. read

    Read the Staff List report. Staff role with report access.

    MCP callclubready_read → read_staff_list_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-list-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_staff_profitability_report Read the Staff Profitability report. Staff role with report access. read

    Read the Staff Profitability report. Staff role with report access.

    MCP callclubready_read → read_staff_profitability_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-profitability-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_staff_utilization_report Read the Staff Utilization report. Staff role with report access. read

    Read the Staff Utilization report. Staff role with report access.

    MCP callclubready_read → read_staff_utilization_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-utilization-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff role with report access"
    }
  • read_stretchlab_staff_utilization_report Read the Staff Utilization report (brand-specific). Available only to the Stretchlab brand per the article title. read

    Read the Staff Utilization report (brand-specific). Available only to the Stretchlab brand per the article title.

    MCP callclubready_read → read_stretchlab_staff_utilization_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/stretchlab-staff-utilization-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Available only to the Stretchlab brand per the article title"
    }
  • read_time_clock_payroll_report Read the Time Clock Payroll report. Report retrieval only; physical clock-in/out is excluded. read

    Read the Time Clock Payroll report. Report retrieval only; physical clock-in/out is excluded.

    MCP callclubready_read → read_time_clock_payroll_report

    REST endpointGET https://cotlet.dev/api/v1/clubready/time-clock-payroll-reports/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Report retrieval only; physical clock-in/out is excluded"
    }

Staff > Staff Profile5

Documented staff > staff profile work in ClubReady.

  • search_staff_records Look up a staff member. Staff Management permissions. read

    Look up a staff member. Staff Management permissions.

    MCP callclubready_read → search_staff_records

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-records/search

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff Management permissions"
    }
  • update_staff_business_details Edit employee business and personnel details. Name, address, phone, email, hire date, emergency contacts, payroll reference fields. Excludes Login Type, username, password and the owner's own profile. write

    Edit employee business and personnel details. Name, address, phone, email, hire date, emergency contacts, payroll reference fields. Excludes Login Type, username, password and the owner's own profile.

    MCP callclubready_write → update_staff_business_details

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/staff-business-details

    Parameters

    No parameters.

    Example response

    {
      "scope": "Name, address, phone, email, hire date, emergency contacts, payroll reference fields. Excludes Login Type, username, password and the owner's own profile"
    }
  • read_staff_internal_notes View employee internal notes. Permission-bound personnel data. read

    View employee internal notes. Permission-bound personnel data.

    MCP callclubready_read → read_staff_internal_notes

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-internal-notes/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Permission-bound personnel data"
    }
  • create_staff_internal_note Add an internal employee note. Internal only; no message delivery. write

    Add an internal employee note. Internal only; no message delivery.

    MCP callclubready_write → create_staff_internal_note

    REST endpointPOST https://cotlet.dev/api/v1/clubready/staff-internal-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Internal only; no message delivery"
    }
  • change_staff_type Change a staff member's staff type (permission role). Needs Can change a club staff members staff type. Access change; the staff member must log in again. writeAsks first

    Change a staff member's staff type (permission role). Needs Can change a club staff members staff type. Access change; the staff member must log in again.

    MCP callclubready_write → change_staff_type

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/staff-type

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs Can change a club staff members staff type. Access change; the staff member must log in again"
    }

Staff > Staff Profile / Main > My To Do Lists1

Documented staff > staff profile / main > my to do lists work in ClubReady.

  • create_staff_todo Add an employee to-do item. Title, colour, reminder date and optional note. write

    Add an employee to-do item. Title, colour, reminder date and optional note.

    MCP callclubready_write → create_staff_todo

    REST endpointPOST https://cotlet.dev/api/v1/clubready/staff-todos

    Parameters

    No parameters.

    Example response

    {
      "scope": "Title, colour, reminder date and optional note"
    }

Main > My To Do Lists4

Documented main > my to do lists work in ClubReady.

  • read_staff_todos View authorized employee to-dos. Own list and Daily Tasks widget; do not assume access to other employees' lists. read

    View authorized employee to-dos. Own list and Daily Tasks widget; do not assume access to other employees' lists.

    MCP callclubready_read → read_staff_todos

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-todos/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Own list and Daily Tasks widget; do not assume access to other employees' lists"
    }
  • update_staff_todo Edit an authorized employee to-do. Role-scoped. write

    Edit an authorized employee to-do. Role-scoped.

    MCP callclubready_write → update_staff_todo

    REST endpointPATCH https://cotlet.dev/api/v1/clubready/staff-todo

    Parameters

    No parameters.

    Example response

    {
      "scope": "Role-scoped"
    }
  • delete_staff_todo Delete an employee to-do. Destructive; role-scoped. writeAsks first

    Delete an employee to-do. Destructive; role-scoped.

    MCP callclubready_write → delete_staff_todo

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/staff-todos

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive; role-scoped"
    }
  • delete_completed_staff_todos Delete all completed employee to-dos. Destructive; role-scoped. writeAsks first

    Delete all completed employee to-dos. Destructive; role-scoped.

    MCP callclubready_write → delete_completed_staff_todos

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/completed-staff-todos

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive; role-scoped"
    }

Staff > Disciplinary Records2

Documented staff > disciplinary records work in ClubReady.

  • create_staff_disciplinary_record Record a staff disciplinary incident. Record supplied facts only. No sanction decisions and no notifications. write

    Record a staff disciplinary incident. Record supplied facts only. No sanction decisions and no notifications.

    MCP callclubready_write → create_staff_disciplinary_record

    REST endpointPOST https://cotlet.dev/api/v1/clubready/staff-disciplinary-records

    Parameters

    No parameters.

    Example response

    {
      "scope": "Record supplied facts only. No sanction decisions and no notifications"
    }
  • read_staff_disciplinary_records Review staff disciplinary history. Sensitive personnel data; permission-bound. read

    Review staff disciplinary history. Sensitive personnel data; permission-bound.

    MCP callclubready_read → read_staff_disciplinary_records

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-disciplinary-records/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Sensitive personnel data; permission-bound"
    }

Staff1

Documented staff work in ClubReady.

  • add_staff_member Add a new staff member. Needs Can add a new admin or provider. Creates a login, so it is an access change. Master-admin creation is not delegated and no passwords are entered. Optional SSN field is not to be entered. writeAsks first

    Add a new staff member. Needs Can add a new admin or provider. Creates a login, so it is an access change. Master-admin creation is not delegated and no passwords are entered. Optional SSN field is not to be entered.

    MCP callclubready_write → add_staff_member

    REST endpointPOST https://cotlet.dev/api/v1/clubready/staff-members

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs Can add a new admin or provider. Creates a login, so it is an access change. Master-admin creation is not delegated and no passwords are entered. Optional SSN field is not to be entered"
    }

Corporate Portal > Staff Management1

Documented corporate portal > staff management work in ClubReady.

  • add_staff_location_access Add another location to a staff member's access. Corporate access. Access change. writeAsks first

    Add another location to a staff member's access. Corporate access. Access change.

    MCP callclubready_write → add_staff_location_access

    REST endpointPOST https://cotlet.dev/api/v1/clubready/staff-location-access

    Parameters

    No parameters.

    Example response

    {
      "scope": "Corporate access. Access change"
    }

Corporate Portal > Member Management1

Documented corporate portal > member management work in ClubReady.

  • transfer_member_to_location Move a member to a different location. Needs Corporate access plus the client move tool and client options permissions. The target location needs the same sales package and credits. writeAsks first

    Move a member to a different location. Needs Corporate access plus the client move tool and client options permissions. The target location needs the same sales package and credits.

    MCP callclubready_write → transfer_member_to_location

    REST endpointPOST https://cotlet.dev/api/v1/clubready/member-to-location/transfer

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs Corporate access plus the client move tool and client options permissions. The target location needs the same sales package and credits"
    }

Tools > Credits Tools5

Documented tools > credits tools work in ClubReady.

  • read_expiring_session_credits_tool Retrieve session credits by expiry range. Tools permission. read

    Retrieve session credits by expiry range. Tools permission.

    MCP callclubready_read → read_expiring_session_credits_tool

    REST endpointGET https://cotlet.dev/api/v1/clubready/expiring-session-credits-tools/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Tools permission"
    }
  • bulk_change_session_credit_expiration Change expiry for selected credits in bulk. Entitlement change. writeAsks first

    Change expiry for selected credits in bulk. Entitlement change.

    MCP callclubready_write → bulk_change_session_credit_expiration

    REST endpointPOST https://cotlet.dev/api/v1/clubready/change-session-credit-expiration/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Entitlement change"
    }
  • read_credit_expiration_tool_history View credit-expiry adjustment history. Tools permission. read

    View credit-expiry adjustment history. Tools permission.

    MCP callclubready_read → read_credit_expiration_tool_history

    REST endpointGET https://cotlet.dev/api/v1/clubready/credit-expiration-tool-histories/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Tools permission"
    }
  • restore_credit_expiration_tool_changes Restore previous credit-expiry dates. Reversal of an entitlement change. writeAsks first

    Restore previous credit-expiry dates. Reversal of an entitlement change.

    MCP callclubready_write → restore_credit_expiration_tool_changes

    REST endpointPOST https://cotlet.dev/api/v1/clubready/credit-expiration-tool-changes/restore

    Parameters

    No parameters.

    Example response

    {
      "scope": "Reversal of an entitlement change"
    }
  • bulk_import_session_credits Import customer session credits from a CSV. The template can wipe existing credits and carries payroll values. writeAsks first

    Import customer session credits from a CSV. The template can wipe existing credits and carries payroll values.

    MCP callclubready_write → bulk_import_session_credits

    REST endpointPOST https://cotlet.dev/api/v1/clubready/import-session-credits/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "The template can wipe existing credits and carries payroll values"
    }

Prospects/Members Lookup1

Documented prospects/members lookup work in ClubReady.

  • export_filtered_customer_lookup Export a filtered customer lookup to Excel. Retrieval only. read

    Export a filtered customer lookup to Excel. Retrieval only.

    MCP callclubready_read → export_filtered_customer_lookup

    REST endpointGET https://cotlet.dev/api/v1/clubready/filtered-customer-lookups/export

    Parameters

    No parameters.

    Example response

    {
      "scope": "Retrieval only"
    }

Tools > Customers Tools11

Documented tools > customers tools work in ClubReady.

  • bulk_update_customer_lead_types Bulk-update customer lead types and dates. Lead-type changes may trigger automation. writeAsks first

    Bulk-update customer lead types and dates. Lead-type changes may trigger automation.

    MCP callclubready_write → bulk_update_customer_lead_types

    REST endpointPOST https://cotlet.dev/api/v1/clubready/update-customer-lead-types/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Lead-type changes may trigger automation"
    }
  • read_membership_expiration_tool_users Retrieve members by membership expiry range. Tools permission. read

    Retrieve members by membership expiry range. Tools permission.

    MCP callclubready_read → read_membership_expiration_tool_users

    REST endpointGET https://cotlet.dev/api/v1/clubready/membership-expiration-tool-users/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Tools permission"
    }
  • bulk_change_membership_expiration Change membership expiries in bulk. Access and entitlement change. writeAsks first

    Change membership expiries in bulk. Access and entitlement change.

    MCP callclubready_write → bulk_change_membership_expiration

    REST endpointPOST https://cotlet.dev/api/v1/clubready/change-membership-expiration/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Access and entitlement change"
    }
  • read_membership_expiration_tool_history View membership-expiry adjustment history. Tools permission. read

    View membership-expiry adjustment history. Tools permission.

    MCP callclubready_read → read_membership_expiration_tool_history

    REST endpointGET https://cotlet.dev/api/v1/clubready/membership-expiration-tool-histories/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Tools permission"
    }
  • restore_membership_expiration_tool_changes Restore previous membership expiry dates. Access reversal. writeAsks first

    Restore previous membership expiry dates. Access reversal.

    MCP callclubready_write → restore_membership_expiration_tool_changes

    REST endpointPOST https://cotlet.dev/api/v1/clubready/membership-expiration-tool-changes/restore

    Parameters

    No parameters.

    Example response

    {
      "scope": "Access reversal"
    }
  • read_staff_prospect_assignments Read prospect assignments by staff. Tools permission. read

    Read prospect assignments by staff. Tools permission.

    MCP callclubready_read → read_staff_prospect_assignments

    REST endpointGET https://cotlet.dev/api/v1/clubready/staff-prospect-assignments/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Tools permission"
    }
  • bulk_reassign_prospects Assign or reassign prospects in bulk. Conservative: assignment may change who sees the prospects. writeAsks first

    Assign or reassign prospects in bulk. Conservative: assignment may change who sees the prospects.

    MCP callclubready_write → bulk_reassign_prospects

    REST endpointPOST https://cotlet.dev/api/v1/clubready/reassign-prospects/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Conservative: assignment may change who sees the prospects"
    }
  • read_customer_file_catalog List, sort and open customer files. Tools permission. read

    List, sort and open customer files. Tools permission.

    MCP callclubready_read → read_customer_file_catalog

    REST endpointGET https://cotlet.dev/api/v1/clubready/customer-file-catalogs/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Tools permission"
    }
  • delete_customer_file Delete a customer file. Destructive. writeAsks first

    Delete a customer file. Destructive.

    MCP callclubready_write → delete_customer_file

    REST endpointDELETE https://cotlet.dev/api/v1/clubready/customer-files

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive"
    }
  • bulk_update_customer_classifications Bulk-update documented customer classifications. Documented fields only: lead type/date, membership type, referral type, Assigned To. writeAsks first

    Bulk-update documented customer classifications. Documented fields only: lead type/date, membership type, referral type, Assigned To.

    MCP callclubready_write → bulk_update_customer_classifications

    REST endpointPOST https://cotlet.dev/api/v1/clubready/update-customer-classifications/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Documented fields only: lead type/date, membership type, referral type, Assigned To"
    }
  • bulk_import_customers Import customers or prospects from the vendor CSV template. Cannot be undone. Options include status, login duration, welcome letter and free credits. writeAsks first

    Import customers or prospects from the vendor CSV template. Cannot be undone. Options include status, login duration, welcome letter and free credits.

    MCP callclubready_write → bulk_import_customers

    REST endpointPOST https://cotlet.dev/api/v1/clubready/import-customers/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Cannot be undone. Options include status, login duration, welcome letter and free credits"
    }

Tools > Products Tools2

Documented tools > products tools work in ClubReady.

  • bulk_import_products Import retail products from the vendor template. Internal records; no ordering or publishing. write

    Import retail products from the vendor template. Internal records; no ordering or publishing.

    MCP callclubready_write → bulk_import_products

    REST endpointPOST https://cotlet.dev/api/v1/clubready/import-products/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Internal records; no ordering or publishing"
    }
  • bulk_adjust_inventory Apply bulk inventory quantity adjustments. CSV set/increase/decrease; changes are logged. write

    Apply bulk inventory quantity adjustments. CSV set/increase/decrease; changes are logged.

    MCP callclubready_write → bulk_adjust_inventory

    REST endpointPOST https://cotlet.dev/api/v1/clubready/adjust-inventory/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "CSV set/increase/decrease; changes are logged"
    }

Tools > Sales Tools1

Documented tools > sales tools work in ClubReady.

  • bulk_import_customer_invoices Import customer invoices from the vendor template. Creates financial obligations. The article has navigation inconsistencies, so check the tenant UI. writeAsks first

    Import customer invoices from the vendor template. Creates financial obligations. The article has navigation inconsistencies, so check the tenant UI.

    MCP callclubready_write → bulk_import_customer_invoices

    REST endpointPOST https://cotlet.dev/api/v1/clubready/import-customer-invoices/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Creates financial obligations. The article has navigation inconsistencies, so check the tenant UI"
    }

Tools > Tasks Tools2

Documented tools > tasks tools work in ClubReady.

  • bulk_delete_customer_tasks Delete filtered customer tasks in bulk. Destructive; filters define scope. writeAsks first

    Delete filtered customer tasks in bulk. Destructive; filters define scope.

    MCP callclubready_write → bulk_delete_customer_tasks

    REST endpointPOST https://cotlet.dev/api/v1/clubready/delete-customer-tasks/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive; filters define scope"
    }
  • bulk_reassign_customer_tasks Reassign tasks between staff in bulk. Internal assignment; ask first if it changes record visibility. write

    Reassign tasks between staff in bulk. Internal assignment; ask first if it changes record visibility.

    MCP callclubready_write → bulk_reassign_customer_tasks

    REST endpointPOST https://cotlet.dev/api/v1/clubready/reassign-customer-tasks/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Internal assignment; ask first if it changes record visibility"
    }

ClubReady Connect10

Documented clubready connect work in ClubReady.

  • read_connect_shared_inbox Read the Connect shared inbox. Separate product with its own Connect login and a monthly subscription; opened from the Connect tab in ClubReady. read

    Read the Connect shared inbox. Separate product with its own Connect login and a monthly subscription; opened from the Connect tab in ClubReady.

    MCP callclubready_read → read_connect_shared_inbox

    REST endpointGET https://cotlet.dev/api/v1/clubready/connect-shared-inbox/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Separate product with its own Connect login and a monthly subscription; opened from the Connect tab in ClubReady"
    }
  • read_connect_customer_message_history Read customer message history in Connect. Connect entitlement required. read

    Read customer message history in Connect. Connect entitlement required.

    MCP callclubready_read → read_connect_customer_message_history

    REST endpointGET https://cotlet.dev/api/v1/clubready/connect-customer-message-histories/read

    Parameters

    No parameters.

    Example response

    {
      "scope": "Connect entitlement required"
    }
  • filter_connect_contacts_by_lead_type Filter Connect contacts by custom lead type. Connect entitlement required. read

    Filter Connect contacts by custom lead type. Connect entitlement required.

    MCP callclubready_read → filter_connect_contacts_by_lead_type

    REST endpointGET https://cotlet.dev/api/v1/clubready/connect-contacts-by-lead-types/filter

    Parameters

    No parameters.

    Example response

    {
      "scope": "Connect entitlement required"
    }
  • segment_connect_message_audience Group customers into message segments. Selection only; sending is separate. read

    Group customers into message segments. Selection only; sending is separate.

    MCP callclubready_read → segment_connect_message_audience

    REST endpointGET https://cotlet.dev/api/v1/clubready/connect-message-audiences/segment

    Parameters

    No parameters.

    Example response

    {
      "scope": "Selection only; sending is separate"
    }
  • send_connect_customer_message Send an individual SMS or MMS from Connect. External send. Needs Connect entitlement. writeAsks first

    Send an individual SMS or MMS from Connect. External send. Needs Connect entitlement.

    MCP callclubready_write → send_connect_customer_message

    REST endpointPOST https://cotlet.dev/api/v1/clubready/connect-customer-messages

    Parameters

    No parameters.

    Example response

    {
      "scope": "External send. Needs Connect entitlement"
    }
  • send_connect_campaign Send a segmented campaign from Connect. External send to a group. writeAsks first

    Send a segmented campaign from Connect. External send to a group.

    MCP callclubready_write → send_connect_campaign

    REST endpointPOST https://cotlet.dev/api/v1/clubready/connect-campaigns

    Parameters

    No parameters.

    Example response

    {
      "scope": "External send to a group"
    }
  • send_connect_class_roster_message Message an entire class from Connect. External send. writeAsks first

    Message an entire class from Connect. External send.

    MCP callclubready_write → send_connect_class_roster_message

    REST endpointPOST https://cotlet.dev/api/v1/clubready/connect-class-roster-messages

    Parameters

    No parameters.

    Example response

    {
      "scope": "External send"
    }
  • schedule_connect_reminders Schedule messages and appointment reminders in Connect. External send, scheduled. writeAsks first

    Schedule messages and appointment reminders in Connect. External send, scheduled.

    MCP callclubready_write → schedule_connect_reminders

    REST endpointPOST https://cotlet.dev/api/v1/clubready/connect-reminders/schedule

    Parameters

    No parameters.

    Example response

    {
      "scope": "External send, scheduled"
    }
  • configure_connect_followups Configure automated follow-ups and messaging workflows in Connect. Automation that messages customers. writeAsks first

    Configure automated follow-ups and messaging workflows in Connect. Automation that messages customers.

    MCP callclubready_write → configure_connect_followups

    REST endpointPOST https://cotlet.dev/api/v1/clubready/connect-followups/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Automation that messages customers"
    }
  • configure_connect_waitlist_notifications Configure automated waitlist notifications in Connect. Automation that messages customers. writeAsks first

    Configure automated waitlist notifications in Connect. Automation that messages customers.

    MCP callclubready_write → configure_connect_waitlist_notifications

    REST endpointPOST https://cotlet.dev/api/v1/clubready/connect-waitlist-notifications/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Automation that messages customers"
    }
Encrypted, revocable

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

  • What we store

    Your signed-in ClubReady profile, AES-256-GCM encrypted, in Finland. No password.

  • What your agent gets

    The 168 ClubReady tools, never the session cookie.

  • What the session sees

    The records and screens available to your signed-in role in ClubReady.

  • What no tool touches

    Owner password, sign-in email, MFA, subscription billing and bank credentials. Ordinary customer records remain in scope.

  • If ClubReady 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 ClubReady 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).

Your account

What happens when ClubReady changes? The tools work in your own signed-in ClubReady account.

Cotlet watches ClubReady and updates the server when its screens change.

New ClubReady features become available to the agent within your account permissions.

Your ClubReady account and role determine which records and screens the agent can use.

If ClubReady signs you out, open your Cloud Browser with one click from the Cotlet console and sign in again.

82 tools ask first

Approvals, undo and mistakes Customers get nothing until you say so.

  1. 01 Identify the account record A trial visit, an unanswered sales lead and an expiring agreement need different next steps. Give the agent the member or prospect and the ClubReady club before asking it to change a record.
  2. 02 Search customer or prospect profiles Search customer or prospect profiles. Staff role with Prospect Management: Can Access Prospects Lookup; desktop web; authorized club only.
  3. 03 Review the proposed change Update customer business-contact details. Staff role with Can Edit Client Profiles. Business-contact fields only (name, address, phone, contact email). Not portal username or password.
  4. 04 Read the resulting record Check the record you selected before handing over the next task.
Which ClubReady actions can be undone
ActionUndo
Update customer business-contact detailsReview the operation and its current record before choosing a corrective action.

By default you confirm each call; you can switch that off for this tool. Tools marked Asks first wait for your approval. Unmarked tools run at once.

MCP call
{
  "name": "search_customer_profiles",
  "arguments": {}
}
REST
curl https://cotlet.dev/api/v1/clubready/customer-profiles/search \
  -H "Authorization: Bearer $COTLET_API_KEY"
Response
{
  "scope": "Staff role with Prospect Management: Can Access Prospects Lookup; desktop web; authorized club only"
}

A cron job or n8n flow can call the same tools over REST at /api/v1/clubready with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.

Pay per call

How much does the ClubReady MCP server cost?

About $18 a monthfor a membership studio with 100 active members and 12 trial visits a month, 3,180 credits. Your ClubReady plan stays as it is.

Illustrative four-week ClubReady account workload, in credits
JobCallsCredits
Search customer or prospect profiles1 × 48480
View a customer profile1 × 40400
View customer tasks1 × 36360
Add an internal customer note1 × 24240
Send a text message to a customer1 × 20200
Cloud Browser, 30 days1,500
Total3,180

The $29 pack covers a typical month for most owners.

  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Use the features included in your existing ClubReady plan.

Assumed successful calls for this owner workload. Dollars use the $29 pack rate.

Cotlet credit packs: price, credits and calls at 10 credits each
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.

Other options

ClubReady MCP server: connection options Choose by the work and entitlement each connection actually covers.

Other ways to connect ClubReady, checked 12 Nov 2026
OptionWhat it doesWhere it stops
Official API or connectorClubReady provides an official API and real-time data notifications. Request a key from ClubReady Support; third-party authorization is approved by the club owner.No vendor-published ClubReady MCP server or ChatGPT or Claude connector was found in the sources checked on 12 November 2026.
Native app featuresClubReady Connect supports customer messaging, segments and follow-up automation. Its configured workflows determine which messages run.Your enabled vendor features determine the scope.
By handOpen the business records and perform the work yourself.Each review and update takes your time.

ClubReady provides an official API and real-time data notifications. Request a key from ClubReady Support; third-party authorization is approved by the club owner. No vendor-published ClubReady MCP server or ChatGPT or Claude connector was found in the sources checked on 12 November 2026. Among these options, Cotlet lets your AI agent read and write on the ClubReady screens your own account can use, from ChatGPT, Claude or any MCP client, without a vendor API key or a vendor plan change.

Among these options, only Cotlet lets your AI agent read and write on every ClubReady screen you can use yourself, from ChatGPT, Claude or any MCP client, without a ClubReady API key or a change to your current ClubReady plan.

EU company, since 2019

Who runs Cotlet A company you can look up.

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 ClubReady tools go to contact@cotlet.dev.

ClubReady MCP server: questions

How do I get access?

Create a Cotlet account, open ClubReady and sign in at app.clubready.com/login. Enable it for agents, then add Cotlet to your chosen AI assistant.

How do I connect ClubReady to ChatGPT or Claude?

Sign up at cotlet.dev, log in to ClubReady 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 ClubReady account through Cotlet, in their phone apps too.

What can ChatGPT do in ClubReady?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in ClubReady: search customer or prospect profiles; view a customer profile; view customer amenities. You ask in plain words.

Is there an official ChatGPT or Claude app for ClubReady?

No vendor-published ClubReady MCP server or ChatGPT or Claude connector was found in the sources checked on 12 November 2026. Cotlet is independent and is not affiliated with ClubReady.

Can ChatGPT search customer or prospect profiles in ClubReady?

Search customer or prospect profiles: Search customer or prospect profiles. Staff role with Prospect Management: Can Access Prospects Lookup; desktop web; authorized club only.

Can ChatGPT view a customer profile in ClubReady?

View a customer profile: View a customer profile. Staff role with client profile access; desktop web.

Can ChatGPT update customer business-contact details in ClubReady?

Update customer business-contact details: Update customer business-contact details. Staff role with Can Edit Client Profiles. Business-contact fields only (name, address, phone, contact email). Not portal username or password.

Can ChatGPT update customer emergency contacts in ClubReady?

Update customer emergency contacts: Update customer emergency contacts. Staff role with Can Edit Client Profiles; contact details only, no clinical content.

Can ChatGPT change a customer's membership type in ClubReady?

Change a customer's membership type: Change a customer's membership type. Staff role with Can edit clients membership type. Confirm because it can change entitlements.

Does ClubReady have an API?

ClubReady provides an official API and real-time data notifications. Request a key from ClubReady Support; third-party authorization is approved by the club owner.

Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 168 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with ClubReady?

No. Cotlet is independent and not affiliated with ClubReady.

Finish the follow-up before the next trial arrives.

Free 7-day trial with 2,000 credits, no card needed.