Pike13 API and MCP server Let your AI agent put each client in the right session.

Pike13: Pike13 documents Core, Reporting and Webhooks APIs. Developer and help documentation require Premium and app approval; its marketing page also names Advanced. Check the entitlement on your account before building an API connection. No official Pike13 MCP server or ChatGPT or Claude connector was found in the vendor sources checked on 12 November 2026. Checked 12 November 2026. Cotlet provides 133 Cloud Browser capabilities for ChatGPT and Claude in your business account. Pike13 separates the client, the event and the plan that pays for the visit. Name the location and session so a roster change stays tied to the booking the client expects.

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

133 tools Read and write

Your business account

What can your AI agent do in Pike13? Pike13 separates the client, the event and the plan that pays for the visit. Name the location and session so a roster change stays tied to the booking the client expects.

  • Read tomorrow's class rosters

  • Find clients with unused passes

  • Review waitlisted clients for a session

  • Check the staff member assigned to an event

  • Read a client's visit history

  • Prepare the requested enrollment change

API needs paid entitlement

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

Pike13 documents Core, Reporting and Webhooks APIs. Developer and help documentation require Premium and app approval; its marketing page also names Advanced. Check the entitlement on your account before building an API connection. No official Pike13 MCP server or ChatGPT or Claude connector was found in the vendor sources checked on 12 November 2026.

  • Pike13 documents Core, Reporting and Webhooks APIs. Developer and help documentation require Premium and app approval; its marketing page also names Advanced. Check the entitlement on your account before building an API connection.
  • No official Pike13 MCP server or ChatGPT or Claude connector was found in the vendor sources checked on 12 November 2026.
  • Pike13 provides class rosters, enrollment rules, plans and reporting in the studio account. These features follow your staff role and enabled plan.
The Pike13 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 Pike13 screen you can use yourself, from ChatGPT, Claude or any MCP client, without a Pike13 API key or a change to your current Pike13 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

Set up once

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

  1. 1Sign in to Pike13

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the busywork

    In Pike13, search customer records for the record and period I select. Search customer records. Per-tenant staff permissions.

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

Any MCP client

How to connect Pike13 to your AI agent

  1. 1

    Sign in to Pike13 in a Cloud Browser. Open Pike13 in your Cotlet Cloud Browser and sign in with your own business account at pike13.com/accounts/sign_in.

  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.

Pike13 shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Pike13 on after connecting? Refresh the connector and the 133 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: pike13_read
29 read, 104 write

All 133 Pike13 MCP tools

Staff → Client Management23

Documented staff → client management work in Pike13.

  • search_clients Search customer records. Per-tenant staff permissions. read

    Search customer records. Per-tenant staff permissions.

    MCP callpike13_read → search_clients

    REST endpointGET https://cotlet.dev/api/v1/pike13/clients/search

    Parameters

    No parameters.

    Example response

    {
      "scope": "Per-tenant staff permissions"
    }
  • filter_sort_clients Filter and sort customer list. Customer list filters and sort order. read

    Filter and sort customer list. Customer list filters and sort order.

    MCP callpike13_read → filter_sort_clients

    REST endpointGET https://cotlet.dev/api/v1/pike13/sort-clients/filter

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer list filters and sort order"
    }
  • view_client_dashboard View customer dashboard. Account credit is a separate menu item, not dashboard content. read

    View customer dashboard. Account credit is a separate menu item, not dashboard content.

    MCP callpike13_read → view_client_dashboard

    REST endpointGET https://cotlet.dev/api/v1/pike13/client-dashboards/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Account credit is a separate menu item, not dashboard content"
    }
  • update_client_business_profile Edit customer business profile. Customer record only; if an edit changes the customer's sign-in email, stop and hand off. writeAsks first

    Edit customer business profile. Customer record only; if an edit changes the customer's sign-in email, stop and hand off.

    MCP callpike13_write → update_client_business_profile

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/client-business-profile

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer record only; if an edit changes the customer's sign-in email, stop and hand off"
    }
  • create_client_record Create customer record. Only with welcome email and complimentary pass turned off; Limited Staff cannot use it; otherwise confirm first. write

    Create customer record. Only with welcome email and complimentary pass turned off; Limited Staff cannot use it; otherwise confirm first.

    MCP callpike13_write → create_client_record

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-records

    Parameters

    No parameters.

    Example response

    {
      "scope": "Only with welcome email and complimentary pass turned off; Limited Staff cannot use it; otherwise confirm first"
    }
  • create_dependent_record Create dependent customer. Creates a management relationship between people. writeAsks first

    Create dependent customer. Creates a management relationship between people.

    MCP callpike13_write → create_dependent_record

    REST endpointPOST https://cotlet.dev/api/v1/pike13/dependent-records

    Parameters

    No parameters.

    Example response

    {
      "scope": "Creates a management relationship between people"
    }
  • resend_client_welcome Resend customer welcome email. Sends customer email; , so check actual tenant permissions. writeAsks first

    Resend customer welcome email. Sends customer email; , so check actual tenant permissions.

    MCP callpike13_write → resend_client_welcome

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-welcome/resend

    Parameters

    No parameters.

    Example response

    {
      "scope": "Sends customer email; , so check actual tenant permissions"
    }
  • merge_client_profiles Merge duplicate customer profiles. Owner or Manager permission; conflicts resolved manually. writeAsks first

    Merge duplicate customer profiles. Owner or Manager permission; conflicts resolved manually.

    MCP callpike13_write → merge_client_profiles

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-profiles/merge

    Parameters

    No parameters.

    Example response

    {
      "scope": "Owner or Manager permission; conflicts resolved manually"
    }
  • set_client_non_client_status Change customer to non-client. For customers who only manage dependents. writeAsks first

    Change customer to non-client. For customers who only manage dependents.

    MCP callpike13_write → set_client_non_client_status

    REST endpointPUT https://cotlet.dev/api/v1/pike13/client-non-client-status

    Parameters

    No parameters.

    Example response

    {
      "scope": "For customers who only manage dependents"
    }
  • hide_client_record Hide customer from client list. Does not cancel plans, stop billing or cancel future bookings; reversible via Reactivate. writeAsks first

    Hide customer from client list. Does not cancel plans, stop billing or cancel future bookings; reversible via Reactivate.

    MCP callpike13_write → hide_client_record

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-record/hide

    Parameters

    No parameters.

    Example response

    {
      "scope": "Does not cancel plans, stop billing or cancel future bookings; reversible via Reactivate"
    }
  • reactivate_hidden_client Reactivate hidden customer. Primary Owner, Owner or Manager. writeAsks first

    Reactivate hidden customer. Primary Owner, Owner or Manager.

    MCP callpike13_write → reactivate_hidden_client

    REST endpointPOST https://cotlet.dev/api/v1/pike13/hidden-client/reactivate

    Parameters

    No parameters.

    Example response

    {
      "scope": "Primary Owner, Owner or Manager"
    }
  • delete_client_profile Delete customer profile. Removes access and erases personal details; history stays in reports and attendance lists. writeAsks first

    Delete customer profile. Removes access and erases personal details; history stays in reports and attendance lists.

    MCP callpike13_write → delete_client_profile

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/client-profiles

    Parameters

    No parameters.

    Example response

    {
      "scope": "Removes access and erases personal details; history stays in reports and attendance lists"
    }
  • convert_client_to_staff Create staff profile for customer. Grants staff access; Managers and Owners only. writeAsks first

    Create staff profile for customer. Grants staff access; Managers and Owners only.

    MCP callpike13_write → convert_client_to_staff

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-to-staff/convert

    Parameters

    No parameters.

    Example response

    {
      "scope": "Grants staff access; Managers and Owners only"
    }
  • grant_site_designer_access Grant customer site-designer access. Access grant covering website layout, colors and navigation. writeAsks first

    Grant customer site-designer access. Access grant covering website layout, colors and navigation.

    MCP callpike13_write → grant_site_designer_access

    REST endpointPOST https://cotlet.dev/api/v1/pike13/site-designer-access/grant

    Parameters

    No parameters.

    Example response

    {
      "scope": "Access grant covering website layout, colors and navigation"
    }
  • create_custom_client_field Create customer field. Settings → Advanced Settings → Client Signup → Custom Fields. writeAsks first

    Create customer field. Settings → Advanced Settings → Client Signup → Custom Fields.

    MCP callpike13_write → create_custom_client_field

    REST endpointPOST https://cotlet.dev/api/v1/pike13/custom-client-fields

    Parameters

    No parameters.

    Example response

    {
      "scope": "Settings → Advanced Settings → Client Signup → Custom Fields"
    }
  • update_custom_client_field Edit customer field. Customer record field. writeAsks first

    Edit customer field. Customer record field.

    MCP callpike13_write → update_custom_client_field

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/custom-client-field

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer record field"
    }
  • delete_custom_client_field Delete customer field. Irreversible: saved data in the field is permanently removed. writeAsks first

    Delete customer field. Irreversible: saved data in the field is permanently removed.

    MCP callpike13_write → delete_custom_client_field

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/custom-client-fields

    Parameters

    No parameters.

    Example response

    {
      "scope": "Irreversible: saved data in the field is permanently removed"
    }
  • configure_document_field_placeholder Use customer field as document placeholder. Changes what appears in documents and waivers. writeAsks first

    Use customer field as document placeholder. Changes what appears in documents and waivers.

    MCP callpike13_write → configure_document_field_placeholder

    REST endpointPOST https://cotlet.dev/api/v1/pike13/document-field-placeholder/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes what appears in documents and waivers"
    }
  • view_client_notifications View customer notification history. Alerts sent to the customer; New and Archived tabs. read

    View customer notification history. Alerts sent to the customer; New and Archived tabs.

    MCP callpike13_read → view_client_notifications

    REST endpointGET https://cotlet.dev/api/v1/pike13/client-notifications/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Alerts sent to the customer; New and Archived tabs"
    }
  • view_client_notification_settings View customer notification settings. Read-only Settings tab. read

    View customer notification settings. Read-only Settings tab.

    MCP callpike13_read → view_client_notification_settings

    REST endpointGET https://cotlet.dev/api/v1/pike13/client-notification-settings/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Read-only Settings tab"
    }
  • view_client_recurring_enrollments View recurring customer enrollments. Managers and Owners. read

    View recurring customer enrollments. Managers and Owners.

    MCP callpike13_read → view_client_recurring_enrollments

    REST endpointGET https://cotlet.dev/api/v1/pike13/client-recurring-enrollments/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Managers and Owners"
    }
  • remove_recurring_class_enrollments Remove customer from a recurring class series. Class series; removal of one instance is separate; check the notify option. writeAsks first

    Remove customer from a recurring class series. Class series; removal of one instance is separate; check the notify option.

    MCP callpike13_write → remove_recurring_class_enrollments

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/recurring-class-enrollments

    Parameters

    No parameters.

    Example response

    {
      "scope": "Class series; removal of one instance is separate; check the notify option"
    }

Staff → Notes & Staff Notifications10

Documented staff → notes & staff notifications work in Pike13.

  • view_client_notes Read customer notes. Per role note permissions. read

    Read customer notes. Per role note permissions.

    MCP callpike13_read → view_client_notes

    REST endpointGET https://cotlet.dev/api/v1/pike13/client-notes/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Per role note permissions"
    }
  • view_event_notes Read event notes. Class, course or appointment Notes tab. read

    Read event notes. Class, course or appointment Notes tab.

    MCP callpike13_read → view_event_notes

    REST endpointGET https://cotlet.dev/api/v1/pike13/event-notes/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Class, course or appointment Notes tab"
    }
  • create_private_client_note Add internal customer note. Private (staff-only) visibility only. write

    Add internal customer note. Private (staff-only) visibility only.

    MCP callpike13_write → create_private_client_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/private-client-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Private (staff-only) visibility only"
    }
  • create_private_event_note Add internal event note. Private visibility only. write

    Add internal event note. Private visibility only.

    MCP callpike13_write → create_private_event_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/private-event-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Private visibility only"
    }
  • star_client_note Star customer note. Internal organization only. write

    Star customer note. Internal organization only.

    MCP callpike13_write → star_client_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-note/star

    Parameters

    No parameters.

    Example response

    {
      "scope": "Internal organization only"
    }
  • send_client_note Send public note to a customer. Public notes notify the customer. writeAsks first

    Send public note to a customer. Public notes notify the customer.

    MCP callpike13_write → send_client_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Public notes notify the customer"
    }
  • send_roster_note Send public note to enrolled customers. Goes to everyone currently enrolled. writeAsks first

    Send public note to enrolled customers. Goes to everyone currently enrolled.

    MCP callpike13_write → send_roster_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/roster-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Goes to everyone currently enrolled"
    }
  • publish_event_website_note Publish event website note. Public on the client website; the current help article says enrolled customers are also emailed (an older blog says otherwise). writeAsks first

    Publish event website note. Public on the client website; the current help article says enrolled customers are also emailed (an older blog says otherwise).

    MCP callpike13_write → publish_event_website_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/event-website-note/publish

    Parameters

    No parameters.

    Example response

    {
      "scope": "Public on the client website; the current help article says enrolled customers are also emailed (an older blog says otherwise)"
    }
  • delete_note Delete customer-profile note. Client-profile notes only; limited to the roles the permissions guide checks. writeAsks first

    Delete customer-profile note. Client-profile notes only; limited to the roles the permissions guide checks.

    MCP callpike13_write → delete_note

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Client-profile notes only; limited to the roles the permissions guide checks"
    }
  • view_operational_notifications Review business notifications. Reading and archiving the feed only; changing personal notification preferences is excluded. read

    Review business notifications. Reading and archiving the feed only; changing personal notification preferences is excluded.

    MCP callpike13_read → view_operational_notifications

    REST endpointGET https://cotlet.dev/api/v1/pike13/operational-notifications/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Reading and archiving the feed only; changing personal notification preferences is excluded"
    }

Pike13 Skill Tracking2

Documented pike13 skill tracking work in Pike13.

  • add_private_skill_note Add internal skill note. Private only; Skill Tracking is Premium (included or add-on); excluded in any medical deployment. write

    Add internal skill note. Private only; Skill Tracking is Premium (included or add-on); excluded in any medical deployment.

    MCP callpike13_write → add_private_skill_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/private-skill-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Private only; Skill Tracking is Premium (included or add-on); excluded in any medical deployment"
    }
  • add_public_skill_note Share skill note with customer. Customer-visible; same Skill Tracking caveats. writeAsks first

    Share skill note with customer. Customer-visible; same Skill Tracking caveats.

    MCP callpike13_write → add_public_skill_note

    REST endpointPOST https://cotlet.dev/api/v1/pike13/public-skill-notes

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer-visible; same Skill Tracking caveats"
    }

Staff → Staff Dashboard (Today tab)2

Documented staff → staff dashboard (today tab) work in Pike13.

  • view_today_unpaid_invoices_queue View unpaid-invoice queue (Today tab). Viewing only; contacting customers needs its own confirmation. read

    View unpaid-invoice queue (Today tab). Viewing only; contacting customers needs its own confirmation.

    MCP callpike13_read → view_today_unpaid_invoices_queue

    REST endpointGET https://cotlet.dev/api/v1/pike13/today-unpaid-invoices-queues/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Viewing only; contacting customers needs its own confirmation"
    }
  • view_unpaid_invoices_upcoming_visits View unpaid invoices with upcoming visits. Viewing only. read

    View unpaid invoices with upcoming visits. Viewing only.

    MCP callpike13_read → view_unpaid_invoices_upcoming_visits

    REST endpointGET https://cotlet.dev/api/v1/pike13/unpaid-invoices-upcoming-visits/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Viewing only"
    }

Services12

Documented services work in Pike13.

  • view_service_catalog View service offerings. Settings → Services. read

    View service offerings. Settings → Services.

    MCP callpike13_read → view_service_catalog

    REST endpointGET https://cotlet.dev/api/v1/pike13/service-catalogs/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Settings → Services"
    }
  • create_appointment_service Create appointment service. Pay rates and Payroll settings are Advanced and Premium only. writeAsks first

    Create appointment service. Pay rates and Payroll settings are Advanced and Premium only.

    MCP callpike13_write → create_appointment_service

    REST endpointPOST https://cotlet.dev/api/v1/pike13/appointment-services

    Parameters

    No parameters.

    Example response

    {
      "scope": "Pay rates and Payroll settings are Advanced and Premium only"
    }
  • duplicate_appointment_service Duplicate appointment service. May create another visible offering. writeAsks first

    Duplicate appointment service. May create another visible offering.

    MCP callpike13_write → duplicate_appointment_service

    REST endpointPOST https://cotlet.dev/api/v1/pike13/appointment-service/duplicate

    Parameters

    No parameters.

    Example response

    {
      "scope": "May create another visible offering"
    }
  • create_class_service Create class service. Customer-facing offering. writeAsks first

    Create class service. Customer-facing offering.

    MCP callpike13_write → create_class_service

    REST endpointPOST https://cotlet.dev/api/v1/pike13/class-services

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer-facing offering"
    }
  • update_class_service Edit class service. Capacity and waitlist limits only. writeAsks first

    Edit class service. Capacity and waitlist limits only.

    MCP callpike13_write → update_class_service

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/class-service

    Parameters

    No parameters.

    Example response

    {
      "scope": "Capacity and waitlist limits only"
    }
  • duplicate_class_service Duplicate class service. Generic duplicate option, not class-specific. writeAsks first

    Duplicate class service. Generic duplicate option, not class-specific.

    MCP callpike13_write → duplicate_class_service

    REST endpointPOST https://cotlet.dev/api/v1/pike13/class-service/duplicate

    Parameters

    No parameters.

    Example response

    {
      "scope": "Generic duplicate option, not class-specific"
    }
  • manage_service_categories Create or edit service categories. Changes customer-facing classification. writeAsks first

    Create or edit service categories. Changes customer-facing classification.

    MCP callpike13_write → manage_service_categories

    REST endpointPOST https://cotlet.dev/api/v1/pike13/service-categories/manage

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes customer-facing classification"
    }
  • configure_service_registration Set online enrollment eligibility and window. Classes and appointments only. writeAsks first

    Set online enrollment eligibility and window. Classes and appointments only.

    MCP callpike13_write → configure_service_registration

    REST endpointPOST https://cotlet.dev/api/v1/pike13/service-registration/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Classes and appointments only"
    }
  • configure_service_recurrence_permissions Set recurring or bulk enrollment permissions per service. Pike13 Support must first enable class Bulk Enrollment for the business; per-service staff and client controls are self-serve afterwards. writeAsks first

    Set recurring or bulk enrollment permissions per service. Pike13 Support must first enable class Bulk Enrollment for the business; per-service staff and client controls are self-serve afterwards.

    MCP callpike13_write → configure_service_recurrence_permissions

    REST endpointPOST https://cotlet.dev/api/v1/pike13/service-recurrence-permissions/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Pike13 Support must first enable class Bulk Enrollment for the business; per-service staff and client controls are self-serve afterwards"
    }
  • configure_service_instructions_reminders Set service instructions and reminders. Changes future customer emails. writeAsks first

    Set service instructions and reminders. Changes future customer emails.

    MCP callpike13_write → configure_service_instructions_reminders

    REST endpointPOST https://cotlet.dev/api/v1/pike13/service-instructions-reminders/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes future customer emails"
    }
  • configure_class_waitlist Configure class waitlist. Changes booking rules and notifications. writeAsks first

    Configure class waitlist. Changes booking rules and notifications.

    MCP callpike13_write → configure_class_waitlist

    REST endpointPOST https://cotlet.dev/api/v1/pike13/class-waitlist/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes booking rules and notifications"
    }
  • set_event_session_capacity Change capacity of one class or course session. Existing enrollments stay even above a reduced capacity; not available for appointments. writeAsks first

    Change capacity of one class or course session. Existing enrollments stay even above a reduced capacity; not available for appointments.

    MCP callpike13_write → set_event_session_capacity

    REST endpointPUT https://cotlet.dev/api/v1/pike13/event-session-capacity

    Parameters

    No parameters.

    Example response

    {
      "scope": "Existing enrollments stay even above a reduced capacity; not available for appointments"
    }

Events → Schedule10

Documented events → schedule work in Pike13.

  • update_scheduled_class Modify scheduled class time. Instance or future-instance scope; customer notification choice. writeAsks first

    Modify scheduled class time. Instance or future-instance scope; customer notification choice.

    MCP callpike13_write → update_scheduled_class

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/scheduled-class

    Parameters

    No parameters.

    Example response

    {
      "scope": "Instance or future-instance scope; customer notification choice"
    }
  • update_scheduled_course Modify scheduled course time. Changing an occurrence time is supported; moving a student's one missed visit to another offering is not. writeAsks first

    Modify scheduled course time. Changing an occurrence time is supported; moving a student's one missed visit to another offering is not.

    MCP callpike13_write → update_scheduled_course

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/scheduled-course

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changing an occurrence time is supported; moving a student's one missed visit to another offering is not"
    }
  • book_appointment Book appointment. Limited Staff excluded; review step has a Notify affected clients choice. writeAsks first

    Book appointment. Limited Staff excluded; review step has a Notify affected clients choice.

    MCP callpike13_write → book_appointment

    REST endpointPOST https://cotlet.dev/api/v1/pike13/appointments

    Parameters

    No parameters.

    Example response

    {
      "scope": "Limited Staff excluded; review step has a Notify affected clients choice"
    }
  • schedule_class_times Schedule class time. Publishes a bookable event; Add Another Time appears only if bulk enrollment is enabled. writeAsks first

    Schedule class time. Publishes a bookable event; Add Another Time appears only if bulk enrollment is enabled.

    MCP callpike13_write → schedule_class_times

    REST endpointPOST https://cotlet.dev/api/v1/pike13/class-times/schedule

    Parameters

    No parameters.

    Example response

    {
      "scope": "Publishes a bookable event; Add Another Time appears only if bulk enrollment is enabled"
    }
  • enroll_client_in_class Enroll customer in class. Limited Staff allowed; enrolling under 30 minutes before start or after start needs manual attendance confirmation. writeAsks first

    Enroll customer in class. Limited Staff allowed; enrolling under 30 minutes before start or after start needs manual attendance confirmation.

    MCP callpike13_write → enroll_client_in_class

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-in-class/enroll

    Parameters

    No parameters.

    Example response

    {
      "scope": "Limited Staff allowed; enrolling under 30 minutes before start or after start needs manual attendance confirmation"
    }
  • bulk_enroll_client_in_classes Enroll customer in recurring class instances. Requires Pike13 Support to enable Bulk Enrollment; multi-client mode skips per-client conflict checks. writeAsks first

    Enroll customer in recurring class instances. Requires Pike13 Support to enable Bulk Enrollment; multi-client mode skips per-client conflict checks.

    MCP callpike13_write → bulk_enroll_client_in_classes

    REST endpointPOST https://cotlet.dev/api/v1/pike13/enroll-client-in-classes/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Requires Pike13 Support to enable Bulk Enrollment; multi-client mode skips per-client conflict checks"
    }
  • bulk_enroll_multiple_clients Bulk-enroll multiple customers in a class series. Same Support-enablement requirement; optional customer notification. writeAsks first

    Bulk-enroll multiple customers in a class series. Same Support-enablement requirement; optional customer notification.

    MCP callpike13_write → bulk_enroll_multiple_clients

    REST endpointPOST https://cotlet.dev/api/v1/pike13/enroll-multiple-clients/bulk

    Parameters

    No parameters.

    Example response

    {
      "scope": "Same Support-enablement requirement; optional customer notification"
    }
  • cancel_client_class_enrollment Remove customer from a class. Staff-side removal; this instance or this and future instances. writeAsks first

    Remove customer from a class. Staff-side removal; this instance or this and future instances.

    MCP callpike13_write → cancel_client_class_enrollment

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-class-enrollment/cancel

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff-side removal; this instance or this and future instances"
    }
  • view_class_waitlist Review class waitlist. Needs permission to view waitlist entries. read

    Review class waitlist. Needs permission to view waitlist entries.

    MCP callpike13_read → view_class_waitlist

    REST endpointGET https://cotlet.dev/api/v1/pike13/class-waitlists/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs permission to view waitlist entries"
    }
  • view_course_waitlist Review course waitlist. Needs permission to view waitlist entries. read

    Review course waitlist. Needs permission to view waitlist entries.

    MCP callpike13_read → view_course_waitlist

    REST endpointGET https://cotlet.dev/api/v1/pike13/course-waitlists/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Needs permission to view waitlist entries"
    }

Events → Roster & Attendance2

Documented events → roster & attendance work in Pike13.

  • view_event_roster View event roster. Attendee list for the selected event. read

    View event roster. Attendee list for the selected event.

    MCP callpike13_read → view_event_roster

    REST endpointGET https://cotlet.dev/api/v1/pike13/event-rosters/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Attendee list for the selected event"
    }
  • confirm_client_attendance Confirm customer attendance. Records attendance only, not physical presence. writeAsks first

    Confirm customer attendance. Records attendance only, not physical presence.

    MCP callpike13_write → confirm_client_attendance

    REST endpointPOST https://cotlet.dev/api/v1/pike13/client-attendance/confirm

    Parameters

    No parameters.

    Example response

    {
      "scope": "Records attendance only, not physical presence"
    }

Services → Rooms10

Documented services → rooms work in Pike13.

  • view_rooms_availability View rooms and availability. Rooms are Advanced and Premium and off by default. read

    View rooms and availability. Rooms are Advanced and Premium and off by default.

    MCP callpike13_read → view_rooms_availability

    REST endpointGET https://cotlet.dev/api/v1/pike13/rooms-availabilities/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Rooms are Advanced and Premium and off by default"
    }
  • enable_rooms_feature Enable Rooms. Advanced and Premium only; Essential must contact sales. writeAsks first

    Enable Rooms. Advanced and Premium only; Essential must contact sales.

    MCP callpike13_write → enable_rooms_feature

    REST endpointPOST https://cotlet.dev/api/v1/pike13/rooms-feature/enable

    Parameters

    No parameters.

    Example response

    {
      "scope": "Advanced and Premium only; Essential must contact sales"
    }
  • create_room Create room. Creates a bookable resource. writeAsks first

    Create room. Creates a bookable resource.

    MCP callpike13_write → create_room

    REST endpointPOST https://cotlet.dev/api/v1/pike13/rooms

    Parameters

    No parameters.

    Example response

    {
      "scope": "Creates a bookable resource"
    }
  • update_room Edit room. May affect existing bookings. writeAsks first

    Edit room. May affect existing bookings.

    MCP callpike13_write → update_room

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/room

    Parameters

    No parameters.

    Example response

    {
      "scope": "May affect existing bookings"
    }
  • delete_room Delete room. Destructive. writeAsks first

    Delete room. Destructive.

    MCP callpike13_write → delete_room

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/rooms

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive"
    }
  • assign_room_to_service Assign room to service. Changes resource booking rules. writeAsks first

    Assign room to service. Changes resource booking rules.

    MCP callpike13_write → assign_room_to_service

    REST endpointPOST https://cotlet.dev/api/v1/pike13/room-to-service/assign

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes resource booking rules"
    }
  • set_room_availability Set room availability. Changes bookable times. writeAsks first

    Set room availability. Changes bookable times.

    MCP callpike13_write → set_room_availability

    REST endpointPUT https://cotlet.dev/api/v1/pike13/room-availability

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes bookable times"
    }
  • configure_room_overbooking Set room overbooking behavior. Changes capacity safeguards. writeAsks first

    Set room overbooking behavior. Changes capacity safeguards.

    MCP callpike13_write → configure_room_overbooking

    REST endpointPOST https://cotlet.dev/api/v1/pike13/room-overbooking/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes capacity safeguards"
    }
  • configure_room_sharing Configure concurrent room sharing. Concurrent appointments up to room capacity; when off, the first appointment reserves the whole room. writeAsks first

    Configure concurrent room sharing. Concurrent appointments up to room capacity; when off, the first appointment reserves the whole room.

    MCP callpike13_write → configure_room_sharing

    REST endpointPOST https://cotlet.dev/api/v1/pike13/room-sharing/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Concurrent appointments up to room capacity; when off, the first appointment reserves the whole room"
    }
  • configure_room_self_booking Configure customer room self-booking. Grants customer booking access; direct booking also needs a service without staff availability. writeAsks first

    Configure customer room self-booking. Grants customer booking access; direct booking also needs a service without staff availability.

    MCP callpike13_write → configure_room_self_booking

    REST endpointPOST https://cotlet.dev/api/v1/pike13/room-self-booking/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Grants customer booking access; direct booking also needs a service without staff availability"
    }

Staff → Staff Availability4

Documented staff → staff availability work in Pike13.

  • view_staff_availability View staff appointment availability. Per staff permissions. read

    View staff appointment availability. Per staff permissions.

    MCP callpike13_read → view_staff_availability

    REST endpointGET https://cotlet.dev/api/v1/pike13/staff-availabilities/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Per staff permissions"
    }
  • set_staff_available_hours Set staff appointment hours. Changes bookable availability. writeAsks first

    Set staff appointment hours. Changes bookable availability.

    MCP callpike13_write → set_staff_available_hours

    REST endpointPUT https://cotlet.dev/api/v1/pike13/staff-available-hours

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes bookable availability"
    }
  • view_staff_availability_history View staff availability history. Date-filterable. read

    View staff availability history. Date-filterable.

    MCP callpike13_read → view_staff_availability_history

    REST endpointGET https://cotlet.dev/api/v1/pike13/staff-availability-histories/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Date-filterable"
    }
  • export_staff_availability_history Export staff availability history. Local download only; sending it elsewhere needs confirmation. read

    Export staff availability history. Local download only; sending it elsewhere needs confirmation.

    MCP callpike13_read → export_staff_availability_history

    REST endpointGET https://cotlet.dev/api/v1/pike13/staff-availability-histories/export

    Parameters

    No parameters.

    Example response

    {
      "scope": "Local download only; sending it elsewhere needs confirmation"
    }

Staff → Staff Payroll11

Documented staff → staff payroll work in Pike13.

  • configure_staff_pay_rates Set staff pay rates. Advanced and Premium. writeAsks first

    Set staff pay rates. Advanced and Premium.

    MCP callpike13_write → configure_staff_pay_rates

    REST endpointPOST https://cotlet.dev/api/v1/pike13/staff-pay-rates/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Advanced and Premium"
    }
  • review_pending_payroll Review pending payroll items. Advanced and Premium; Owner or Primary Owner. read

    Review pending payroll items. Advanced and Premium; Owner or Primary Owner.

    MCP callpike13_read → review_pending_payroll

    REST endpointGET https://cotlet.dev/api/v1/pike13/pending-payrolls/review

    Parameters

    No parameters.

    Example response

    {
      "scope": "Advanced and Premium; Owner or Primary Owner"
    }
  • approve_payroll_item Approve payroll item. Calculation records only; Pike13 does not move payroll funds. writeAsks first

    Approve payroll item. Calculation records only; Pike13 does not move payroll funds.

    MCP callpike13_write → approve_payroll_item

    REST endpointPOST https://cotlet.dev/api/v1/pike13/payroll-item/approve

    Parameters

    No parameters.

    Example response

    {
      "scope": "Calculation records only; Pike13 does not move payroll funds"
    }
  • reject_payroll_item Reject payroll item. Discards pending pay. writeAsks first

    Reject payroll item. Discards pending pay.

    MCP callpike13_write → reject_payroll_item

    REST endpointPOST https://cotlet.dev/api/v1/pike13/payroll-item/reject

    Parameters

    No parameters.

    Example response

    {
      "scope": "Discards pending pay"
    }
  • reassign_payroll_item Reassign payroll item. Changes employee allocation before approval. writeAsks first

    Reassign payroll item. Changes employee allocation before approval.

    MCP callpike13_write → reassign_payroll_item

    REST endpointPOST https://cotlet.dev/api/v1/pike13/payroll-item/reassign

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes employee allocation before approval"
    }
  • generate_payroll_report Calculate or view payroll report. Transient calculation or viewing existing results only; creating, closing, deleting or recalculating stored periods are the separate write functions. read

    Calculate or view payroll report. Transient calculation or viewing existing results only; creating, closing, deleting or recalculating stored periods are the separate write functions.

    MCP callpike13_read → generate_payroll_report

    REST endpointGET https://cotlet.dev/api/v1/pike13/payroll-reports/generate

    Parameters

    No parameters.

    Example response

    {
      "scope": "Transient calculation or viewing existing results only; creating, closing, deleting or recalculating stored periods are the separate write functions"
    }
  • recalculate_pending_pay Recalculate stored pending pay. Updates stored compensation records. writeAsks first

    Recalculate stored pending pay. Updates stored compensation records.

    MCP callpike13_write → recalculate_pending_pay

    REST endpointPOST https://cotlet.dev/api/v1/pike13/pending-pay/recalculate

    Parameters

    No parameters.

    Example response

    {
      "scope": "Updates stored compensation records"
    }
  • create_payroll_period Create payroll period. Creates a stored period. writeAsks first

    Create payroll period. Creates a stored period.

    MCP callpike13_write → create_payroll_period

    REST endpointPOST https://cotlet.dev/api/v1/pike13/payroll-periods

    Parameters

    No parameters.

    Example response

    {
      "scope": "Creates a stored period"
    }
  • close_payroll_period Close payroll period. Marks the period Closed. writeAsks first

    Close payroll period. Marks the period Closed.

    MCP callpike13_write → close_payroll_period

    REST endpointPOST https://cotlet.dev/api/v1/pike13/payroll-period/close

    Parameters

    No parameters.

    Example response

    {
      "scope": "Marks the period Closed"
    }
  • delete_payroll_period Delete generated payroll period. Destructive; the period can be recreated. writeAsks first

    Delete generated payroll period. Destructive; the period can be recreated.

    MCP callpike13_write → delete_payroll_period

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/payroll-periods

    Parameters

    No parameters.

    Example response

    {
      "scope": "Destructive; the period can be recreated"
    }
  • export_payroll_period_csv Download payroll-period CSV. Local download only; sending it elsewhere needs confirmation. read

    Download payroll-period CSV. Local download only; sending it elsewhere needs confirmation.

    MCP callpike13_read → export_payroll_period_csv

    REST endpointGET https://cotlet.dev/api/v1/pike13/payroll-period-csvs/export

    Parameters

    No parameters.

    Example response

    {
      "scope": "Local download only; sending it elsewhere needs confirmation"
    }

Products & Merchandise13

Documented products & merchandise work in Pike13.

  • view_client_passes_plans View customer passes and plans. Active, Upcoming and Inactive lists. read

    View customer passes and plans. Active, Upcoming and Inactive lists.

    MCP callpike13_read → view_client_passes_plans

    REST endpointGET https://cotlet.dev/api/v1/pike13/client-passes-plans/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Active, Upcoming and Inactive lists"
    }
  • update_pass_product Edit pass product. Term changes generally apply to future sales; applicable-service changes affect existing holders. writeAsks first

    Edit pass product. Term changes generally apply to future sales; applicable-service changes affect existing holders.

    MCP callpike13_write → update_pass_product

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/pass-product

    Parameters

    No parameters.

    Example response

    {
      "scope": "Term changes generally apply to future sales; applicable-service changes affect existing holders"
    }
  • delete_pass_product Delete pass product. Only never-sold passes can be deleted; otherwise stop selling. writeAsks first

    Delete pass product. Only never-sold passes can be deleted; otherwise stop selling.

    MCP callpike13_write → delete_pass_product

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/pass-products

    Parameters

    No parameters.

    Example response

    {
      "scope": "Only never-sold passes can be deleted; otherwise stop selling"
    }
  • delete_merchandise_item Delete merchandise item. Only never-sold items; the article's entitlement table excludes Essential. writeAsks first

    Delete merchandise item. Only never-sold items; the article's entitlement table excludes Essential.

    MCP callpike13_write → delete_merchandise_item

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/merchandise-items

    Parameters

    No parameters.

    Example response

    {
      "scope": "Only never-sold items; the article's entitlement table excludes Essential"
    }
  • create_recurring_plan Create recurring plan product. Customer service plan, not the owner's Pike13 subscription. writeAsks first

    Create recurring plan product. Customer service plan, not the owner's Pike13 subscription.

    MCP callpike13_write → create_recurring_plan

    REST endpointPOST https://cotlet.dev/api/v1/pike13/recurring-plans

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer service plan, not the owner's Pike13 subscription"
    }
  • update_plan_product Edit plan product. Settings → Plans; group rates and plan policies are not included. writeAsks first

    Edit plan product. Settings → Plans; group rates and plan policies are not included.

    MCP callpike13_write → update_plan_product

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/plan-product

    Parameters

    No parameters.

    Example response

    {
      "scope": "Settings → Plans; group rates and plan policies are not included"
    }
  • configure_plan_service_eligibility Set services covered by plan. Changes affect existing holders. writeAsks first

    Set services covered by plan. Changes affect existing holders.

    MCP callpike13_write → configure_plan_service_eligibility

    REST endpointPOST https://cotlet.dev/api/v1/pike13/plan-service-eligibility/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes affect existing holders"
    }
  • configure_plan_renewal_commitment Set required payments and renewal terms. Includes custom-term renewal into a different commitment duration (2026 release). writeAsks first

    Set required payments and renewal terms. Includes custom-term renewal into a different commitment duration (2026 release).

    MCP callpike13_write → configure_plan_renewal_commitment

    REST endpointPOST https://cotlet.dev/api/v1/pike13/plan-renewal-commitment/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Includes custom-term renewal into a different commitment duration (2026 release)"
    }
  • stop_selling_plan Stop selling plan. Hides the plan from the store; current holders stay active. writeAsks first

    Stop selling plan. Hides the plan from the store; current holders stay active.

    MCP callpike13_write → stop_selling_plan

    REST endpointPOST https://cotlet.dev/api/v1/pike13/selling-plan/stop

    Parameters

    No parameters.

    Example response

    {
      "scope": "Hides the plan from the store; current holders stay active"
    }
  • resume_selling_plan Resume selling plan. Restores a suspended plan to sale. writeAsks first

    Resume selling plan. Restores a suspended plan to sale.

    MCP callpike13_write → resume_selling_plan

    REST endpointPOST https://cotlet.dev/api/v1/pike13/selling-plan/resume

    Parameters

    No parameters.

    Example response

    {
      "scope": "Restores a suspended plan to sale"
    }
  • delete_plan_product Delete plan product. Only plans that have never been sold; otherwise stop selling. writeAsks first

    Delete plan product. Only plans that have never been sold; otherwise stop selling.

    MCP callpike13_write → delete_plan_product

    REST endpointDELETE https://cotlet.dev/api/v1/pike13/plan-products

    Parameters

    No parameters.

    Example response

    {
      "scope": "Only plans that have never been sold; otherwise stop selling"
    }
  • update_recurring_plan_prices Change recurring-plan prices for active plans. Changes future customer charges. writeAsks first

    Change recurring-plan prices for active plans. Changes future customer charges.

    MCP callpike13_write → update_recurring_plan_prices

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/recurring-plan-prices

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes future customer charges"
    }
  • import_existing_client_plan_pass Import customer's existing plan or pass. Managers and Owners; no initial bill is created. writeAsks first

    Import customer's existing plan or pass. Managers and Owners; no initial bill is created.

    MCP callpike13_write → import_existing_client_plan_pass

    REST endpointPOST https://cotlet.dev/api/v1/pike13/existing-client-plan-pass

    Parameters

    No parameters.

    Example response

    {
      "scope": "Managers and Owners; no initial bill is created"
    }

Transactions14

Documented transactions work in Pike13.

  • view_customer_invoices View customer invoices and upcoming bills. Upcoming bills confirmed on the dashboard; full invoice view from the invoices article. read

    View customer invoices and upcoming bills. Upcoming bills confirmed on the dashboard; full invoice view from the invoices article.

    MCP callpike13_read → view_customer_invoices

    REST endpointGET https://cotlet.dev/api/v1/pike13/customer-invoices/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Upcoming bills confirmed on the dashboard; full invoice view from the invoices article"
    }
  • view_purchase_requests View purchase requests. Dashboard listing confirmed; tracking workflow in the purchase-requests article. read

    View purchase requests. Dashboard listing confirmed; tracking workflow in the purchase-requests article.

    MCP callpike13_read → view_purchase_requests

    REST endpointGET https://cotlet.dev/api/v1/pike13/purchase-requests/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Dashboard listing confirmed; tracking workflow in the purchase-requests article"
    }
  • pay_invoice_in_full Apply full invoice payment with a saved method. Customer charge; entering a new card or bank number is excluded; confirm payer, amount, method, receipt recipient. writeAsks first

    Apply full invoice payment with a saved method. Customer charge; entering a new card or bank number is excluded; confirm payer, amount, method, receipt recipient.

    MCP callpike13_write → pay_invoice_in_full

    REST endpointPOST https://cotlet.dev/api/v1/pike13/invoice-in-full/pay

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer charge; entering a new card or bank number is excluded; confirm payer, amount, method, receipt recipient"
    }
  • split_invoice_payment Pay invoice using multiple methods. For recurring plans, split applies to the first transaction only. writeAsks first

    Pay invoice using multiple methods. For recurring plans, split applies to the first transaction only.

    MCP callpike13_write → split_invoice_payment

    REST endpointPOST https://cotlet.dev/api/v1/pike13/invoice-payment/split

    Parameters

    No parameters.

    Example response

    {
      "scope": "For recurring plans, split applies to the first transaction only"
    }
  • apply_partial_invoice_payment Apply partial invoice payment. Passes and plans are usable only after full payment. writeAsks first

    Apply partial invoice payment. Passes and plans are usable only after full payment.

    MCP callpike13_write → apply_partial_invoice_payment

    REST endpointPOST https://cotlet.dev/api/v1/pike13/partial-invoice-payment/apply

    Parameters

    No parameters.

    Example response

    {
      "scope": "Passes and plans are usable only after full payment"
    }
  • complete_partial_invoice_payment Pay remaining invoice balance. Customer charge. writeAsks first

    Pay remaining invoice balance. Customer charge.

    MCP callpike13_write → complete_partial_invoice_payment

    REST endpointPOST https://cotlet.dev/api/v1/pike13/partial-invoice-payment/complete

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer charge"
    }
  • refund_customer_payment Refund customer payment. Returns funds; the refund can cancel associated products and sends a receipt by default. writeAsks first

    Refund customer payment. Returns funds; the refund can cancel associated products and sends a receipt by default.

    MCP callpike13_write → refund_customer_payment

    REST endpointPOST https://cotlet.dev/api/v1/pike13/customer-payment/refund

    Parameters

    No parameters.

    Example response

    {
      "scope": "Returns funds; the refund can cancel associated products and sends a receipt by default"
    }
  • view_account_credit View customer account credit. Balance and associated transactions. read

    View customer account credit. Balance and associated transactions.

    MCP callpike13_read → view_account_credit

    REST endpointGET https://cotlet.dev/api/v1/pike13/account-credits/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Balance and associated transactions"
    }
  • grant_account_credit Add customer account credit. Grants financial value; actual tenant permissions govern who may do this. writeAsks first

    Add customer account credit. Grants financial value; actual tenant permissions govern who may do this.

    MCP callpike13_write → grant_account_credit

    REST endpointPOST https://cotlet.dev/api/v1/pike13/account-credit/grant

    Parameters

    No parameters.

    Example response

    {
      "scope": "Grants financial value; actual tenant permissions govern who may do this"
    }
  • withdraw_account_credit Remove customer account credit. Removes stored credit only; any reimbursement happens outside Pike13. writeAsks first

    Remove customer account credit. Removes stored credit only; any reimbursement happens outside Pike13.

    MCP callpike13_write → withdraw_account_credit

    REST endpointPOST https://cotlet.dev/api/v1/pike13/account-credit/withdraw

    Parameters

    No parameters.

    Example response

    {
      "scope": "Removes stored credit only; any reimbursement happens outside Pike13"
    }
  • refund_to_account_credit Refund purchase as account credit. Refund operation. writeAsks first

    Refund purchase as account credit. Refund operation.

    MCP callpike13_write → refund_to_account_credit

    REST endpointPOST https://cotlet.dev/api/v1/pike13/account-credit/refund

    Parameters

    No parameters.

    Example response

    {
      "scope": "Refund operation"
    }
  • apply_account_credit Apply customer credit to purchase. Consumes credit. writeAsks first

    Apply customer credit to purchase. Consumes credit.

    MCP callpike13_write → apply_account_credit

    REST endpointPOST https://cotlet.dev/api/v1/pike13/account-credit/apply

    Parameters

    No parameters.

    Example response

    {
      "scope": "Consumes credit"
    }
  • configure_account_credit Enable or restrict account credit. Owner-level setting; changes customer financial policy. writeAsks first

    Enable or restrict account credit. Owner-level setting; changes customer financial policy.

    MCP callpike13_write → configure_account_credit

    REST endpointPOST https://cotlet.dev/api/v1/pike13/account-credit/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Owner-level setting; changes customer financial policy"
    }
  • view_saved_payment_methods View saved payment-method summaries. Summary only; no secret extraction. read

    View saved payment-method summaries. Summary only; no secret extraction.

    MCP callpike13_read → view_saved_payment_methods

    REST endpointGET https://cotlet.dev/api/v1/pike13/saved-payment-methods/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "Summary only; no secret extraction"
    }

Staff → Documents & Signatures7

Documented staff → documents & signatures work in Pike13.

  • create_miscellaneous_document Create customer document template. Settings → Documents; not required before enrolling or buying (unlike waivers). writeAsks first

    Create customer document template. Settings → Documents; not required before enrolling or buying (unlike waivers).

    MCP callpike13_write → create_miscellaneous_document

    REST endpointPOST https://cotlet.dev/api/v1/pike13/miscellaneous-documents

    Parameters

    No parameters.

    Example response

    {
      "scope": "Settings → Documents; not required before enrolling or buying (unlike waivers)"
    }
  • update_miscellaneous_document Edit customer document template. Customer document template. writeAsks first

    Edit customer document template. Customer document template.

    MCP callpike13_write → update_miscellaneous_document

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/miscellaneous-document

    Parameters

    No parameters.

    Example response

    {
      "scope": "Customer document template"
    }
  • insert_document_placeholder Add document placeholder. Changes disclosed agreement content. writeAsks first

    Add document placeholder. Changes disclosed agreement content.

    MCP callpike13_write → insert_document_placeholder

    REST endpointPOST https://cotlet.dev/api/v1/pike13/document-placeholder/insert

    Parameters

    No parameters.

    Example response

    {
      "scope": "Changes disclosed agreement content"
    }
  • request_customer_signature Send customer signature request. Sends the request only; does not sign for anyone. writeAsks first

    Send customer signature request. Sends the request only; does not sign for anyone.

    MCP callpike13_write → request_customer_signature

    REST endpointPOST https://cotlet.dev/api/v1/pike13/customer-signature/request

    Parameters

    No parameters.

    Example response

    {
      "scope": "Sends the request only; does not sign for anyone"
    }
  • send_bulk_signature_requests Send signature requests to selected customers or staff. Mass sends have narrower role scope than single requests; the earlier claim that documents cannot be bulk-sent is superseded. writeAsks first

    Send signature requests to selected customers or staff. Mass sends have narrower role scope than single requests; the earlier claim that documents cannot be bulk-sent is superseded.

    MCP callpike13_write → send_bulk_signature_requests

    REST endpointPOST https://cotlet.dev/api/v1/pike13/bulk-signature-requests

    Parameters

    No parameters.

    Example response

    {
      "scope": "Mass sends have narrower role scope than single requests; the earlier claim that documents cannot be bulk-sent is superseded"
    }
  • request_multiple_document_signatures Request several document signatures in one request. Sends one request covering several documents. writeAsks first

    Request several document signatures in one request. Sends one request covering several documents.

    MCP callpike13_write → request_multiple_document_signatures

    REST endpointPOST https://cotlet.dev/api/v1/pike13/multiple-document-signatures/request

    Parameters

    No parameters.

    Example response

    {
      "scope": "Sends one request covering several documents"
    }
  • request_staff_signature Request staff signature. Sends the request only. writeAsks first

    Request staff signature. Sends the request only.

    MCP callpike13_write → request_staff_signature

    REST endpointPOST https://cotlet.dev/api/v1/pike13/staff-signature/request

    Parameters

    No parameters.

    Example response

    {
      "scope": "Sends the request only"
    }

Business Setup6

Documented business setup work in Pike13.

  • view_business_details View business details. General Details. read

    View business details. General Details.

    MCP callpike13_read → view_business_details

    REST endpointGET https://cotlet.dev/api/v1/pike13/business-details/view

    Parameters

    No parameters.

    Example response

    {
      "scope": "General Details"
    }
  • update_business_contact_details Update business contact information. Published contact info, including the footer website URL. writeAsks first

    Update business contact information. Published contact info, including the footer website URL.

    MCP callpike13_write → update_business_contact_details

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/business-contact-details

    Parameters

    No parameters.

    Example response

    {
      "scope": "Published contact info, including the footer website URL"
    }
  • update_business_identity_locale Update business name, address or language. Currency and subdomain are support-only and excluded. writeAsks first

    Update business name, address or language. Currency and subdomain are support-only and excluded.

    MCP callpike13_write → update_business_identity_locale

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/business-identity-locale

    Parameters

    No parameters.

    Example response

    {
      "scope": "Currency and subdomain are support-only and excluded"
    }
  • set_business_clock_format Set business clock format. Existing notifications keep their old format. writeAsks first

    Set business clock format. Existing notifications keep their old format.

    MCP callpike13_write → set_business_clock_format

    REST endpointPUT https://cotlet.dev/api/v1/pike13/business-clock-format

    Parameters

    No parameters.

    Example response

    {
      "scope": "Existing notifications keep their old format"
    }
  • set_business_timezone Set business time zone. Service times adjust when the time zone changes. writeAsks first

    Set business time zone. Service times adjust when the time zone changes.

    MCP callpike13_write → set_business_timezone

    REST endpointPUT https://cotlet.dev/api/v1/pike13/business-timezone

    Parameters

    No parameters.

    Example response

    {
      "scope": "Service times adjust when the time zone changes"
    }
  • set_business_age_of_majority Set age-of-majority rule. Affected customers may be prompted for different waivers. writeAsks first

    Set age-of-majority rule. Affected customers may be prompted for different waivers.

    MCP callpike13_write → set_business_age_of_majority

    REST endpointPUT https://cotlet.dev/api/v1/pike13/business-age-of-majority

    Parameters

    No parameters.

    Example response

    {
      "scope": "Affected customers may be prompted for different waivers"
    }

Apps & Add-ons5

Documented apps & add-ons work in Pike13.

  • configure_appointment_widget Configure embedded appointment widget. Staff member's Show on your Pike13 website must be Yes; publishes a booking interface. writeAsks first

    Configure embedded appointment widget. Staff member's Show on your Pike13 website must be Yes; publishes a booking interface.

    MCP callpike13_write → configure_appointment_widget

    REST endpointPOST https://cotlet.dev/api/v1/pike13/appointment-widget/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Staff member's Show on your Pike13 website must be Yes; publishes a booking interface"
    }
  • configure_business_automation Configure external automation (Zapier). Premium and Advanced only (Essential no); Primary Owner or Owner only; downstream effects depend on the external workflow. writeAsks first

    Configure external automation (Zapier). Premium and Advanced only (Essential no); Primary Owner or Owner only; downstream effects depend on the external workflow.

    MCP callpike13_write → configure_business_automation

    REST endpointPOST https://cotlet.dev/api/v1/pike13/business-automation/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Premium and Advanced only (Essential no); Primary Owner or Owner only; downstream effects depend on the external workflow"
    }
  • configure_audience_sync_secondary Configure email-marketing audience synchronization (Emma). Advanced and Premium only; Primary Owner, Owner or Manager; needs a separate Emma subscription; shares customer data externally. writeAsks first

    Configure email-marketing audience synchronization (Emma). Advanced and Premium only; Primary Owner, Owner or Manager; needs a separate Emma subscription; shares customer data externally.

    MCP callpike13_write → configure_audience_sync_secondary

    REST endpointPOST https://cotlet.dev/api/v1/pike13/audience-sync-secondary/configure

    Parameters

    No parameters.

    Example response

    {
      "scope": "Advanced and Premium only; Primary Owner, Owner or Manager; needs a separate Emma subscription; shares customer data externally"
    }
  • submit_branded_app_assets Submit branded-app assets and listing information. Pike13's team submits to the app stores, so there is no immediate publication; developer-account credentials stay owner-only. writeAsks first

    Submit branded-app assets and listing information. Pike13's team submits to the app stores, so there is no immediate publication; developer-account credentials stay owner-only.

    MCP callpike13_write → submit_branded_app_assets

    REST endpointPOST https://cotlet.dev/api/v1/pike13/branded-app-assets/submit

    Parameters

    No parameters.

    Example response

    {
      "scope": "Pike13's team submits to the app stores, so there is no immediate publication; developer-account credentials stay owner-only"
    }
  • update_branded_app_theme Apply branded-app theme or colors. Premium and Owner/Manager restrictions documented; separate branded-app fees may apply. writeAsks first

    Apply branded-app theme or colors. Premium and Owner/Manager restrictions documented; separate branded-app fees may apply.

    MCP callpike13_write → update_branded_app_theme

    REST endpointPATCH https://cotlet.dev/api/v1/pike13/branded-app-theme

    Parameters

    No parameters.

    Example response

    {
      "scope": "Premium and Owner/Manager restrictions documented; separate branded-app fees may apply"
    }

Reporting1

Documented reporting work in Pike13.

  • run_clients_report Run Clients report. Analytics & Reporting → Clients & Staff; filterable by Client Status; exports to external recipients need confirmation. read

    Run Clients report. Analytics & Reporting → Clients & Staff; filterable by Client Status; exports to external recipients need confirmation.

    MCP callpike13_read → run_clients_report

    REST endpointGET https://cotlet.dev/api/v1/pike13/clients-reports/run

    Parameters

    No parameters.

    Example response

    {
      "scope": "Analytics & Reporting → Clients & Staff; filterable by Client Status; exports to external recipients need confirmation"
    }

Premium Reporting1

Documented premium reporting work in Pike13.

  • send_premium_report Send premium report by email. Premium only; staff reporting permissions; sends data to external recipients immediately. writeAsks first

    Send premium report by email. Premium only; staff reporting permissions; sends data to external recipients immediately.

    MCP callpike13_write → send_premium_report

    REST endpointPOST https://cotlet.dev/api/v1/pike13/premium-reports

    Parameters

    No parameters.

    Example response

    {
      "scope": "Premium only; staff reporting permissions; sends data to external recipients immediately"
    }
Encrypted, revocable

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

  • What we store

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

  • What your agent gets

    The 133 Pike13 tools, never the session cookie.

  • What the session sees

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

  • What no tool touches

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

  • If Pike13 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 Pike13 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 Pike13 changes? The tools work in your own signed-in Pike13 account.

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

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

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

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

99 tools ask first

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

  1. 01 Identify the account record Pike13 separates the client, the event and the plan that pays for the visit. Name the location and session so a roster change stays tied to the booking the client expects.
  2. 02 Search customer records Search customer records. Per-tenant staff permissions.
  3. 03 Review the proposed change Edit customer business profile. Customer record only; if an edit changes the customer's sign-in email, stop and hand off.
  4. 04 Read the resulting record Check the record you selected before handing over the next task.
Which Pike13 actions can be undone
ActionUndo
Edit customer business profileReview 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_clients",
  "arguments": {}
}
REST
curl https://cotlet.dev/api/v1/pike13/clients/search \
  -H "Authorization: Bearer $COTLET_API_KEY"
Response
{
  "scope": "Per-tenant staff permissions"
}

A cron job or n8n flow can call the same tools over REST at /api/v1/pike13 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 Pike13 MCP server cost?

About $19 a monthfor a class studio serving 80 clients with four group sessions on each weekday, 3,300 credits. Your Pike13 plan stays as it is.

Illustrative four-week Pike13 account workload, in credits
JobCallsCredits
Search customer records1 × 60600
Filter and sort customer list1 × 40400
View customer dashboard1 × 32320
Edit customer business profile1 × 28280
Enroll customer in class1 × 20200
Cloud Browser, 30 days1,500
Total3,300

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 Pike13 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

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

Other ways to connect Pike13, checked 12 Nov 2026
OptionWhat it doesWhere it stops
Official API or connectorPike13 documents Core, Reporting and Webhooks APIs. Developer and help documentation require Premium and app approval; its marketing page also names Advanced. Check the entitlement on your account before building an API connection.No official Pike13 MCP server or ChatGPT or Claude connector was found in the vendor sources checked on 12 November 2026.
Native app featuresPike13 provides class rosters, enrollment rules, plans and reporting in the studio account. These features follow your staff role and enabled plan.Your enabled vendor features determine the scope.
By handOpen the business records and perform the work yourself.Each review and update takes your time.

Pike13 documents Core, Reporting and Webhooks APIs. Developer and help documentation require Premium and app approval; its marketing page also names Advanced. Check the entitlement on your account before building an API connection. No official Pike13 MCP server or ChatGPT or Claude connector was found in the vendor sources checked on 12 November 2026. Among these options, Cotlet lets your AI agent read and write on the Pike13 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 Pike13 screen you can use yourself, from ChatGPT, Claude or any MCP client, without a Pike13 API key or a change to your current Pike13 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 Pike13 tools go to contact@cotlet.dev.

Pike13 MCP server: questions

How do I get access?

Create a Cotlet account, open Pike13 and sign in at pike13.com/accounts/sign_in. Enable it for agents, then add Cotlet to your chosen AI assistant.

How do I connect Pike13 to ChatGPT or Claude?

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

What can ChatGPT do in Pike13?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Pike13: search customer records; filter and sort customer list; view customer dashboard. You ask in plain words.

Is there an official ChatGPT or Claude app for Pike13?

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

Can ChatGPT search customer records in Pike13?

Search customer records: Search customer records. Per-tenant staff permissions.

Can ChatGPT filter and sort customer list in Pike13?

Filter and sort customer list: Filter and sort customer list. Customer list filters and sort order.

Can ChatGPT edit customer business profile in Pike13?

Edit customer business profile: Edit customer business profile. Customer record only; if an edit changes the customer's sign-in email, stop and hand off.

Can ChatGPT create customer record in Pike13?

Create customer record: Create customer record. Only with welcome email and complimentary pass turned off; Limited Staff cannot use it; otherwise confirm first.

Can ChatGPT create dependent customer in Pike13?

Create dependent customer: Create dependent customer. Creates a management relationship between people.

Does Pike13 have an API?

Pike13 documents Core, Reporting and Webhooks APIs. Developer and help documentation require Premium and app approval; its marketing page also names Advanced. Check the entitlement on your account before building an API connection.

Is the MCP server different from the REST API?

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

Is Cotlet affiliated with Pike13?

No. Cotlet is independent and not affiliated with Pike13.

Give the next roster review to your agent.

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