Skip to main content
This is the complete tool list for both 1club MCP servers. An assistant sees only the tools of the server it is connected to.

Admin server

https://mcp.1club.ai - authenticated, normally with 1club OAuth. Every call acts in one organization and needs the listed scope. A call whose scope is missing fails with a permission error, not with empty data. Over OAuth, the scope is only half of it: the assistant acts as the person who connected it, so a call also needs the permission their role holds in that gym, exactly as the same action would in the admin. A front desk login with bookings:delete still cannot delete a booking their role cannot delete.

Account

Gyms

Classes, programs, and progression

Areas and availability

Bookings and check-ins

Events

Contacts, tags, and accounts

Instructors, pay, and the staff roster

Staff, roles, and notifications

Plans and memberships

Products

Charges, payments, and invoices

Reports

Rules and policies

Promotions

Reviews

Automations

Forms

Messages and templates

Website

Content and media

Competitors

The transaction tools work on the records the 1club admin and member apps call Charges. The tool and scope names keep the Platform API’s word. See Charges.
get_account needs no resource scope, so it works with any valid connection. That makes it the right first call when an assistant is behaving as if it has no access: if get_account succeeds, authentication worked and the problem is usually the granted scopes. It also lists every organization the connection can act in. When there is more than one, the assistant passes the organization on every call, and should ask you which one you mean rather than guess.
The website tools edit a draft. Every change is invisible to the public until publish_website runs, which is why publishing is its own scope. An assistant that holds website:write but not website:publish can build a page and hand you the preview URL, and cannot put it live. Publishing and rolling back also need the Website Plan Addon. Read get_website_section_types before composing a page, and take image URLs from list_media rather than guessing them.update_website is the exception. The site’s name and the gym it represents apply immediately, and supportedLocales and defaultLocale are organization-wide rather than website content, so they need organization:write as well and apply immediately instead of waiting for a publish - the same languages drive the member portal, the mobile app, and outbound email.create_website builds a new website offline from a Website Template, with the template’s sample copy rewritten from your own data. Taking it online and connecting a domain stay in the admin.
Anything sold by name takes two steps. Booking someone is search_contacts then create_booking; selling a membership is search_contacts, search_plans, then create_membership. Read the plan first and you know the real total, since a plan can charge a joining fee on top of its price. When a name matches more than one person or plan, the assistant should ask which you mean rather than guessing.
Booking labels are titles only, and they are per gym. Ask an assistant to “call private training Coaching” and it changes the card title on that gym’s website, member portal, mobile app, and 1club.me page at once, with no publish step. The line under each card stays 1club’s, and a card named after an area type keeps that type’s name. With more than one gym, say which one, or the assistant should ask. A good assistant also translates the new title into the languages you offer. See Booking labels.
Some writes are refused to an API key. update_staff_role, update_role_permissions, and reset_role_permissions change who can do what, which is checked against the person making the change, so they only work for someone connected over OAuth. An API key can cancel or delete a booking, void or delete its charges, record a payment for it, or waive its cancellation charge only when the key created that booking itself.

Searching text

list_contact_notes, list_form_submissions, list_reviews and the body search of list_messages match words, not exact phrases: every word you search for must appear, accents are ignored (cafe finds café), and the start of a word is enough (knee finds knees). Latin and Cyrillic text are both searchable, each in its own script.

Reading the scope table

Scopes follow the resource:action format used across the Platform API. A connection carrying bookings:write does not automatically carry bookings:read; authorize both if the assistant should look a booking up as well as create one. Where the table lists two scopes joined by “or”, either one is enough.

How a connection gets its scopes

The MCP client asks for a scope set, and you decide how much of that request to grant:
  • A client that requests nothing gets a read-only connection. Every read scope in the tables above, and nothing that changes data.
  • Requested read scopes are granted when you approve. The authorization page lists them under What <assistant> can do, in the Always included group.
  • Everything that is not a read is opt-in, one at a time. Each appears under Make changes as a checkbox that starts unticked - the writes, and also the deletes and website:publish, which remove things for good or make draft edits public. Allow all changes ticks them all at once. Approving the page without ticking any of them produces a read-only connection, even if the client asked for everything.
  • Your role narrows it in each organization. A connection acts as you, so in each organization it holds only the scopes your role’s permissions stand for there. An owner holds every scope.
  • The set is fixed once approved. To add or remove a scope, revoke the connection and authorize it again - see Disconnect or revoke.
An assistant that authenticates with a Platform API key instead of OAuth uses that key’s scopes, which you edit on the token itself.
The wildcard scope * means “everything”, and the two credential types treat it differently. On a Platform API key it is stored as-is and satisfies every current and future scope. MCP OAuth accepts a request for * but never stores it: the wildcard is expanded into the concrete scopes that exist at that moment, so the authorization page can list each one and you can leave the destructive ones unticked. A connection therefore does not silently gain new powers as 1club adds scopes - reconnect when you want the newer ones. For a key, explicit scopes are the better choice unless the integration is fully trusted and internally managed.
Each admin tool is a thin wrapper over the documented Platform API, so the request limits, error shapes, and field meanings are the same as the API reference.

1club server

https://mcp.1club.me - the 1club network, across every listed gym and independent professional. Anyone can search it without an account. Listing, booking, and cancelling the person’s own bookings asks them to sign in with their 1club.me account the first time, and from then on the assistant acts as them. These tools never reach a single organization’s private data, and they have no scopes.

Book (signed in)

Each booking is made exactly as on 1club.me: a membership of theirs that covers it is used, and otherwise it is paid at the gym. A gym that requires paying online when booking cannot be booked this way, and the assistant hands the person the 1club.me link instead. The assistant should book only after the person agrees to what, when, and the price. Reach for find_availability for any “when can I play” question. It searches, prices and dates in one step, so there is no need to find gyms first and then look their availability up separately. Give it a date when someone names a day - without one it walks forward from today and may never reach the day they meant. Everything these tools return is the gym’s own: times are on the venue’s clock (localDay, localTime, localEndTime, localEndDay, with its timezone), and prices come with their currency. Report them as given rather than converting them. Tools address gyms and professionals by their network slug, which is what comes back from a search, and areas, classes, and instructors by the ids get_club and get_professional return - never the ids an assistant sees on the admin server. Do not mix ids between the two servers.
https://mcp.1club.me/me is the same server for clients connected before the root address offered sign-in: every tool there needs the sign-in up front, the search tools included.
Removed in September 2026: get_class_availability, get_area_availability and get_instructor_availability. They addressed classes, areas and instructors by database id, which nobody holds in a conversation, and they overlapped with find_availability. Move any client that called them to find_availability and get_club, which answer the same questions from a place or a gym slug instead of an id.

Optional inline interface

The 1club server’s tools also carry a small inline interface - club cards, slot chips, a club profile - for a host that supports MCP Apps, such as ChatGPT. A client that does not render it is unaffected: every tool still answers in text, and the interface is only ever a view of the same answer.

What is not exposed

The admin server is built strictly on the documented Platform API, so anything that API does not cover is unreachable through MCP today. That currently includes access control and taking card payments. Some areas are covered only in part:
  • Payments can be recorded but never taken: record_payment records money the desk already collected with one of your own payment methods, such as cash or a bank transfer, and the member gets a receipt. Charging a saved card and card payments stay in 1club.
  • Promotions are read-only. Creating and editing discounts and vouchers stays in 1club.
  • Automations and reviews are read-only. Turning an automation on or off, and replying to a review, stay in 1club.
  • Messages can be drafted, edited, and read, but not sent. A draft created with create_message_draft is sent from the 1club inbox.
  • Invoices are read-only. Issuing, sending, charging, and voiding invoices stay in the 1club dashboard.
  • Reports are summaries for a period (get_revenue_report, get_activity_report, get_memberships_report, get_members_report, get_tax_report), not the full analytics screens.
  • Contacts can be created, edited, and archived, but not deleted. Memberships are readable, creatable, and editable, but not deletable.
  • Forms go live as soon as they are created or edited, and can’t be deleted here, because deleting a form deletes every submission made through it.
  • Staff: an assistant can list your staff, change someone’s role, and edit what a role may do, but inviting someone and giving a coach a login stay in 1club. create_instructor makes a bookable coach with no login.
  • Gyms: update_club edits a gym’s profile, but closing a gym for good, its slug, billing, and kiosk settings stay in 1club. Changes to a gym listed on 1club.me are held for review before they reach the listing.
Media can be registered but not uploaded: create_media records a file that is already hosted, so putting a new image online still happens in 1club or through your own hosting. Products and product categories can be created, edited, and retired, but not deleted - deleting a product destroys its sales history. Stock is read-only: get_product_availability reports how many are left to sell, while booking a delivery in, correcting a count after a stocktake, and writing off damaged stock stay in the 1club dashboard. See Products. If you need one of these, the Platform API is where coverage grows first, and MCP follows it.