[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Pike13 API and MCP server: Let your AI agent put each client in the right session. > 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: 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 - Page: https://cotlet.dev/integrations/pike13-api-mcp-server ## What can your AI agent do in Pike13? - 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 ## Does Pike13 have an MCP server or 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. - 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. | What you need | Official connection | By hand | Cotlet | |---|---|---|---| | 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](https://developer.pike13.com/docs/get_started), [Vendor connection documentation 2](https://developer.pike13.com/docs/api/v2), [Vendor connection documentation 3](https://developer.pike13.com/docs/reporting/v3), [Vendor connection documentation 4](https://developer.pike13.com/docs/webhooks/v3), [Vendor connection documentation 5](https://help.pike13.com/hc/en-us/articles/360029643492-Pike13-API), [Vendor connection documentation 6](https://www.pike13.com/api-developer-center), [Vendor connection documentation 7](https://www.pike13.com/franchise-solutions), [Vendor connection documentation 8](https://www.pike13.com/connections-and-integrations), [Vendor connection documentation 9](https://help.pike13.com/knowledge/apps-add-ons), [Vendor connection documentation 10](https://www.usecarly.com/blog/claude-pike13-integration/), [Vendor connection documentation 11](https://www.pike13.com/get-started-with-pike13) ## How does the Pike13 MCP server work? 1. **Sign in to Pike13.** Once, in a browser we host for you. 2. **Connect your AI agent.** One address in its settings. 3. **Hand 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. ## How to connect Pike13 to your AI agent 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. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent. 3. **Let the agent in.** Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console. 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, Tool: pike13_read ``` ## All 133 Pike13 MCP tools ### Staff → Client Management Documented staff → client management work in Pike13. - **Search customer records** (`search_clients`, read): Search customer records. Per-tenant staff permissions. - **Filter and sort customer list** (`filter_sort_clients`, read): Filter and sort customer list. Customer list filters and sort order. - **View customer dashboard** (`view_client_dashboard`, read): View customer dashboard. Account credit is a separate menu item, not dashboard content. - **Edit customer business profile** (`update_client_business_profile`, write, asks first): Edit customer business profile. Customer record only; if an edit changes the customer's sign-in email, stop and hand off. - **Create customer record** (`create_client_record`, write): Create customer record. Only with welcome email and complimentary pass turned off; Limited Staff cannot use it; otherwise confirm first. - **Create dependent customer** (`create_dependent_record`, write, asks first): Create dependent customer. Creates a management relationship between people. - **Link existing customer to an account manager** (`link_existing_managed_client`, write, asks first): Link existing customer to an account manager. Changes who can manage schedules and payments. - **Resend customer welcome email** (`resend_client_welcome`, write, asks first): Resend customer welcome email. Sends customer email; , so check actual tenant permissions. - **Merge duplicate customer profiles** (`merge_client_profiles`, write, asks first): Merge duplicate customer profiles. Owner or Manager permission; conflicts resolved manually. - **Change customer to non-client** (`set_client_non_client_status`, write, asks first): Change customer to non-client. For customers who only manage dependents. - **Hide customer from client list** (`hide_client_record`, write, asks first): Hide customer from client list. Does not cancel plans, stop billing or cancel future bookings; reversible via Reactivate. - **Reactivate hidden customer** (`reactivate_hidden_client`, write, asks first): Reactivate hidden customer. Primary Owner, Owner or Manager. - **Delete customer profile** (`delete_client_profile`, write, asks first): Delete customer profile. Removes access and erases personal details; history stays in reports and attendance lists. - **Create staff profile for customer** (`convert_client_to_staff`, write, asks first): Create staff profile for customer. Grants staff access; Managers and Owners only. - **Grant customer site-designer access** (`grant_site_designer_access`, write, asks first): Grant customer site-designer access. Access grant covering website layout, colors and navigation. - **Create customer field** (`create_custom_client_field`, write, asks first): Create customer field. Settings → Advanced Settings → Client Signup → Custom Fields. - **Edit customer field** (`update_custom_client_field`, write, asks first): Edit customer field. Customer record field. - **Delete customer field** (`delete_custom_client_field`, write, asks first): Delete customer field. Irreversible: saved data in the field is permanently removed. - **Use customer field as document placeholder** (`configure_document_field_placeholder`, write, asks first): Use customer field as document placeholder. Changes what appears in documents and waivers. - **View customer notification history** (`view_client_notifications`, read): View customer notification history. Alerts sent to the customer; New and Archived tabs. - **View customer notification settings** (`view_client_notification_settings`, read): View customer notification settings. Read-only Settings tab. - **View recurring customer enrollments** (`view_client_recurring_enrollments`, read): View recurring customer enrollments. Managers and Owners. - **Remove customer from a recurring class series** (`remove_recurring_class_enrollments`, write, asks first): Remove customer from a recurring class series. Class series; removal of one instance is separate; check the notify option. ### Staff → Notes & Staff Notifications Documented staff → notes & staff notifications work in Pike13. - **Read customer notes** (`view_client_notes`, read): Read customer notes. Per role note permissions. - **Read event notes** (`view_event_notes`, read): Read event notes. Class, course or appointment Notes tab. - **Add internal customer note** (`create_private_client_note`, write): Add internal customer note. Private (staff-only) visibility only. - **Add internal event note** (`create_private_event_note`, write): Add internal event note. Private visibility only. - **Star customer note** (`star_client_note`, write): Star customer note. Internal organization only. - **Send public note to a customer** (`send_client_note`, write, asks first): Send public note to a customer. Public notes notify the customer. - **Send public note to enrolled customers** (`send_roster_note`, write, asks first): Send public note to enrolled customers. Goes to everyone currently enrolled. - **Publish event website note** (`publish_event_website_note`, write, asks 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). - **Delete customer-profile note** (`delete_note`, write, asks first): Delete customer-profile note. Client-profile notes only; limited to the roles the permissions guide checks. - **Review business notifications** (`view_operational_notifications`, read): Review business notifications. Reading and archiving the feed only; changing personal notification preferences is excluded. ### Pike13 Skill Tracking Documented pike13 skill tracking work in Pike13. - **Add internal skill note** (`add_private_skill_note`, write): Add internal skill note. Private only; Skill Tracking is Premium (included or add-on); excluded in any medical deployment. - **Share skill note with customer** (`add_public_skill_note`, write, asks first): Share skill note with customer. Customer-visible; same Skill Tracking caveats. ### Staff → Staff Dashboard (Today tab) Documented staff → staff dashboard (today tab) work in Pike13. - **View unpaid-invoice queue (Today tab)** (`view_today_unpaid_invoices_queue`, read): View unpaid-invoice queue (Today tab). Viewing only; contacting customers needs its own confirmation. - **View unpaid invoices with upcoming visits** (`view_unpaid_invoices_upcoming_visits`, read): View unpaid invoices with upcoming visits. Viewing only. ### Services Documented services work in Pike13. - **View service offerings** (`view_service_catalog`, read): View service offerings. Settings → Services. - **Create appointment service** (`create_appointment_service`, write, asks first): Create appointment service. Pay rates and Payroll settings are Advanced and Premium only. - **Duplicate appointment service** (`duplicate_appointment_service`, write, asks first): Duplicate appointment service. May create another visible offering. - **Create class service** (`create_class_service`, write, asks first): Create class service. Customer-facing offering. - **Edit class service** (`update_class_service`, write, asks first): Edit class service. Capacity and waitlist limits only. - **Duplicate class service** (`duplicate_class_service`, write, asks first): Duplicate class service. Generic duplicate option, not class-specific. - **Create or edit service categories** (`manage_service_categories`, write, asks first): Create or edit service categories. Changes customer-facing classification. - **Set online enrollment eligibility and window** (`configure_service_registration`, write, asks first): Set online enrollment eligibility and window. Classes and appointments only. - **Set recurring or bulk enrollment permissions per service** (`configure_service_recurrence_permissions`, write, asks 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. - **Set service instructions and reminders** (`configure_service_instructions_reminders`, write, asks first): Set service instructions and reminders. Changes future customer emails. - **Configure class waitlist** (`configure_class_waitlist`, write, asks first): Configure class waitlist. Changes booking rules and notifications. - **Change capacity of one class or course session** (`set_event_session_capacity`, write, asks first): Change capacity of one class or course session. Existing enrollments stay even above a reduced capacity; not available for appointments. ### Events → Schedule Documented events → schedule work in Pike13. - **Modify scheduled class time** (`update_scheduled_class`, write, asks first): Modify scheduled class time. Instance or future-instance scope; customer notification choice. - **Modify scheduled course time** (`update_scheduled_course`, write, asks first): Modify scheduled course time. Changing an occurrence time is supported; moving a student's one missed visit to another offering is not. - **Book appointment** (`book_appointment`, write, asks first): Book appointment. Limited Staff excluded; review step has a Notify affected clients choice. - **Schedule class time** (`schedule_class_times`, write, asks first): Schedule class time. Publishes a bookable event; Add Another Time appears only if bulk enrollment is enabled. - **Enroll customer in class** (`enroll_client_in_class`, write, asks first): Enroll customer in class. Limited Staff allowed; enrolling under 30 minutes before start or after start needs manual attendance confirmation. - **Enroll customer in recurring class instances** (`bulk_enroll_client_in_classes`, write, asks first): Enroll customer in recurring class instances. Requires Pike13 Support to enable Bulk Enrollment; multi-client mode skips per-client conflict checks. - **Bulk-enroll multiple customers in a class series** (`bulk_enroll_multiple_clients`, write, asks first): Bulk-enroll multiple customers in a class series. Same Support-enablement requirement; optional customer notification. - **Remove customer from a class** (`cancel_client_class_enrollment`, write, asks first): Remove customer from a class. Staff-side removal; this instance or this and future instances. - **Review class waitlist** (`view_class_waitlist`, read): Review class waitlist. Needs permission to view waitlist entries. - **Review course waitlist** (`view_course_waitlist`, read): Review course waitlist. Needs permission to view waitlist entries. ### Events → Roster & Attendance Documented events → roster & attendance work in Pike13. - **View event roster** (`view_event_roster`, read): View event roster. Attendee list for the selected event. - **Confirm customer attendance** (`confirm_client_attendance`, write, asks first): Confirm customer attendance. Records attendance only, not physical presence. ### Services → Rooms Documented services → rooms work in Pike13. - **View rooms and availability** (`view_rooms_availability`, read): View rooms and availability. Rooms are Advanced and Premium and off by default. - **Enable Rooms** (`enable_rooms_feature`, write, asks first): Enable Rooms. Advanced and Premium only; Essential must contact sales. - **Create room** (`create_room`, write, asks first): Create room. Creates a bookable resource. - **Edit room** (`update_room`, write, asks first): Edit room. May affect existing bookings. - **Delete room** (`delete_room`, write, asks first): Delete room. Destructive. - **Assign room to service** (`assign_room_to_service`, write, asks first): Assign room to service. Changes resource booking rules. - **Set room availability** (`set_room_availability`, write, asks first): Set room availability. Changes bookable times. - **Set room overbooking behavior** (`configure_room_overbooking`, write, asks first): Set room overbooking behavior. Changes capacity safeguards. - **Configure concurrent room sharing** (`configure_room_sharing`, write, asks first): Configure concurrent room sharing. Concurrent appointments up to room capacity; when off, the first appointment reserves the whole room. - **Configure customer room self-booking** (`configure_room_self_booking`, write, asks first): Configure customer room self-booking. Grants customer booking access; direct booking also needs a service without staff availability. ### Staff → Staff Availability Documented staff → staff availability work in Pike13. - **View staff appointment availability** (`view_staff_availability`, read): View staff appointment availability. Per staff permissions. - **Set staff appointment hours** (`set_staff_available_hours`, write, asks first): Set staff appointment hours. Changes bookable availability. - **View staff availability history** (`view_staff_availability_history`, read): View staff availability history. Date-filterable. - **Export staff availability history** (`export_staff_availability_history`, read): Export staff availability history. Local download only; sending it elsewhere needs confirmation. ### Staff → Staff Payroll Documented staff → staff payroll work in Pike13. - **Set staff pay rates** (`configure_staff_pay_rates`, write, asks first): Set staff pay rates. Advanced and Premium. - **Review pending payroll items** (`review_pending_payroll`, read): Review pending payroll items. Advanced and Premium; Owner or Primary Owner. - **Approve payroll item** (`approve_payroll_item`, write, asks first): Approve payroll item. Calculation records only; Pike13 does not move payroll funds. - **Reject payroll item** (`reject_payroll_item`, write, asks first): Reject payroll item. Discards pending pay. - **Reassign payroll item** (`reassign_payroll_item`, write, asks first): Reassign payroll item. Changes employee allocation before approval. - **Calculate or view payroll report** (`generate_payroll_report`, 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. - **Recalculate stored pending pay** (`recalculate_pending_pay`, write, asks first): Recalculate stored pending pay. Updates stored compensation records. - **Create payroll period** (`create_payroll_period`, write, asks first): Create payroll period. Creates a stored period. - **Close payroll period** (`close_payroll_period`, write, asks first): Close payroll period. Marks the period Closed. - **Delete generated payroll period** (`delete_payroll_period`, write, asks first): Delete generated payroll period. Destructive; the period can be recreated. - **Download payroll-period CSV** (`export_payroll_period_csv`, read): Download payroll-period CSV. Local download only; sending it elsewhere needs confirmation. ### Products & Merchandise Documented products & merchandise work in Pike13. - **View customer passes and plans** (`view_client_passes_plans`, read): View customer passes and plans. Active, Upcoming and Inactive lists. - **Edit pass product** (`update_pass_product`, write, asks first): Edit pass product. Term changes generally apply to future sales; applicable-service changes affect existing holders. - **Delete pass product** (`delete_pass_product`, write, asks first): Delete pass product. Only never-sold passes can be deleted; otherwise stop selling. - **Delete merchandise item** (`delete_merchandise_item`, write, asks first): Delete merchandise item. Only never-sold items; the article's entitlement table excludes Essential. - **Create recurring plan product** (`create_recurring_plan`, write, asks first): Create recurring plan product. Customer service plan, not the owner's Pike13 subscription. - **Edit plan product** (`update_plan_product`, write, asks first): Edit plan product. Settings → Plans; group rates and plan policies are not included. - **Set services covered by plan** (`configure_plan_service_eligibility`, write, asks first): Set services covered by plan. Changes affect existing holders. - **Set required payments and renewal terms** (`configure_plan_renewal_commitment`, write, asks first): Set required payments and renewal terms. Includes custom-term renewal into a different commitment duration (2026 release). - **Stop selling plan** (`stop_selling_plan`, write, asks first): Stop selling plan. Hides the plan from the store; current holders stay active. - **Resume selling plan** (`resume_selling_plan`, write, asks first): Resume selling plan. Restores a suspended plan to sale. - **Delete plan product** (`delete_plan_product`, write, asks first): Delete plan product. Only plans that have never been sold; otherwise stop selling. - **Change recurring-plan prices for active plans** (`update_recurring_plan_prices`, write, asks first): Change recurring-plan prices for active plans. Changes future customer charges. - **Import customer's existing plan or pass** (`import_existing_client_plan_pass`, write, asks first): Import customer's existing plan or pass. Managers and Owners; no initial bill is created. ### Transactions Documented transactions work in Pike13. - **View customer invoices and upcoming bills** (`view_customer_invoices`, read): View customer invoices and upcoming bills. Upcoming bills confirmed on the dashboard; full invoice view from the invoices article. - **View purchase requests** (`view_purchase_requests`, read): View purchase requests. Dashboard listing confirmed; tracking workflow in the purchase-requests article. - **Apply full invoice payment with a saved method** (`pay_invoice_in_full`, write, asks 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. - **Pay invoice using multiple methods** (`split_invoice_payment`, write, asks first): Pay invoice using multiple methods. For recurring plans, split applies to the first transaction only. - **Apply partial invoice payment** (`apply_partial_invoice_payment`, write, asks first): Apply partial invoice payment. Passes and plans are usable only after full payment. - **Pay remaining invoice balance** (`complete_partial_invoice_payment`, write, asks first): Pay remaining invoice balance. Customer charge. - **Refund customer payment** (`refund_customer_payment`, write, asks first): Refund customer payment. Returns funds; the refund can cancel associated products and sends a receipt by default. - **View customer account credit** (`view_account_credit`, read): View customer account credit. Balance and associated transactions. - **Add customer account credit** (`grant_account_credit`, write, asks first): Add customer account credit. Grants financial value; actual tenant permissions govern who may do this. - **Remove customer account credit** (`withdraw_account_credit`, write, asks first): Remove customer account credit. Removes stored credit only; any reimbursement happens outside Pike13. - **Refund purchase as account credit** (`refund_to_account_credit`, write, asks first): Refund purchase as account credit. Refund operation. - **Apply customer credit to purchase** (`apply_account_credit`, write, asks first): Apply customer credit to purchase. Consumes credit. - **Enable or restrict account credit** (`configure_account_credit`, write, asks first): Enable or restrict account credit. Owner-level setting; changes customer financial policy. - **View saved payment-method summaries** (`view_saved_payment_methods`, read): View saved payment-method summaries. Summary only; no secret extraction. ### Staff → Documents & Signatures Documented staff → documents & signatures work in Pike13. - **Create customer document template** (`create_miscellaneous_document`, write, asks first): Create customer document template. Settings → Documents; not required before enrolling or buying (unlike waivers). - **Edit customer document template** (`update_miscellaneous_document`, write, asks first): Edit customer document template. Customer document template. - **Add document placeholder** (`insert_document_placeholder`, write, asks first): Add document placeholder. Changes disclosed agreement content. - **Send customer signature request** (`request_customer_signature`, write, asks first): Send customer signature request. Sends the request only; does not sign for anyone. - **Send signature requests to selected customers or staff** (`send_bulk_signature_requests`, write, asks 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. - **Request several document signatures in one request** (`request_multiple_document_signatures`, write, asks first): Request several document signatures in one request. Sends one request covering several documents. - **Request staff signature** (`request_staff_signature`, write, asks first): Request staff signature. Sends the request only. ### Business Setup Documented business setup work in Pike13. - **View business details** (`view_business_details`, read): View business details. General Details. - **Update business contact information** (`update_business_contact_details`, write, asks first): Update business contact information. Published contact info, including the footer website URL. - **Update business name, address or language** (`update_business_identity_locale`, write, asks first): Update business name, address or language. Currency and subdomain are support-only and excluded. - **Set business clock format** (`set_business_clock_format`, write, asks first): Set business clock format. Existing notifications keep their old format. - **Set business time zone** (`set_business_timezone`, write, asks first): Set business time zone. Service times adjust when the time zone changes. - **Set age-of-majority rule** (`set_business_age_of_majority`, write, asks first): Set age-of-majority rule. Affected customers may be prompted for different waivers. ### Apps & Add-ons Documented apps & add-ons work in Pike13. - **Configure embedded appointment widget** (`configure_appointment_widget`, write, asks first): Configure embedded appointment widget. Staff member's Show on your Pike13 website must be Yes; publishes a booking interface. - **Configure external automation (Zapier)** (`configure_business_automation`, write, asks first): Configure external automation (Zapier). Premium and Advanced only (Essential no); Primary Owner or Owner only; downstream effects depend on the external workflow. - **Configure email-marketing audience synchronization (Emma)** (`configure_audience_sync_secondary`, write, asks 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. - **Submit branded-app assets and listing information** (`submit_branded_app_assets`, write, asks 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. - **Apply branded-app theme or colors** (`update_branded_app_theme`, write, asks first): Apply branded-app theme or colors. Premium and Owner/Manager restrictions documented; separate branded-app fees may apply. ### Reporting Documented reporting work in Pike13. - **Run Clients report** (`run_clients_report`, read): Run Clients report. Analytics & Reporting → Clients & Staff; filterable by Client Status; exports to external recipients need confirmation. ### Premium Reporting Documented premium reporting work in Pike13. - **Send premium report by email** (`send_premium_report`, write, asks first): Send premium report by email. Premium only; staff reporting permissions; sends data to external recipients immediately. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/pike13-api-mcp-server#tools ## 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](https://cotlet.dev/security.md)). ## What happens when Pike13 changes? 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. ## Approvals, undo and mistakes 1. **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. **Search customer records.** Search customer records. Per-tenant staff permissions. 3. **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. **Read the resulting record.** Check the record you selected before handing over the next task. | Action | Undo | |---|---| | Edit customer business profile | Review 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. ## How much does the Pike13 MCP server cost? **About $19 a month** for a class studio serving 80 clients with four group sessions on each weekday, 3,300 credits. Your Pike13 plan stays as it is. | Job | Calls | Credits | |---|---|---| | Search customer records | 1 × 60 | 600 | | Filter and sort customer list | 1 × 40 | 400 | | View customer dashboard | 1 × 32 | 320 | | Edit customer business profile | 1 × 28 | 280 | | Enroll customer in class | 1 × 20 | 200 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,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. ## Pike13 MCP server: connection options | Option | What it does | Where it stops | |---|---|---| | Official API or connector | 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. | | Native app features | Pike13 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 hand | Open 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. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the 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 your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.