Tools reference

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/admin - authenticated, normally with 1Club OAuth. Every tool is scoped to one organization and needs the listed scope. A call whose scope is missing fails with a permission error, not with empty data.

Tool	What it does	Scope required
`get_account`	Names the authorized organization and lists its granted scopes	None
`list_classes`	Lists your classes	`classes:read`
`get_class`	Opens one class by id	`classes:read`
`list_class_bookings`	Lists a class roster, with each attendee’s status and what they paid	`bookings:read`
`create_class`	Creates one class occurrence	`classes:write`
`update_class`	Updates one class occurrence	`classes:write`
`delete_class`	Deletes one class or this and future recurring occurrences	`classes:write`
`list_areas`	Lists your bookable areas	`areas:read`
`get_platform_area_availability`	Checks when an area is free, for a date or a date range	`areas:read`
`list_area_blocks`	Lists area blocks overlapping a date range	`areas:read`
`create_area_block`	Closes one court, or a whole gym, for a time range	`areas:write`
`delete_area_block`	Deletes a block, reopening the courts it covered	`areas:write`
`search_contacts`	Finds customers by name, email, or phone	`contacts:read`
`get_contact`	Opens one customer by id	`contacts:read`
`create_contact`	Creates a customer	`contacts:write`
`search_instructors`	Finds coaches by name, gym, or sport	`instructors:read`
`get_instructor`	Opens one coach by id, with hourly rate and bookability	`instructors:read`
`search_plans`	Finds membership plans the gym sells, with price and joining fee	`plans:read`
`get_plan`	Opens one plan by id	`plans:read`
`create_plan`	Creates a membership plan	`plans:write`
`update_plan`	Updates or retires a membership plan	`plans:write`
`delete_plan`	Deletes an unused membership plan	`plans:write`
`list_memberships`	Lists memberships, with sessions remaining	`memberships:read`
`get_membership`	Opens one membership by id	`memberships:read`
`create_membership`	Puts a customer on a plan	`memberships:write`
`update_membership`	Pauses, resumes, or cancels a membership, or adjusts its allowance	`memberships:write`
`search_products`	Finds products by name, description, SKU, or barcode	`products:read`
`get_product`	Opens one product by id	`products:read`
`create_product`	Adds a product to the catalogue	`products:write`
`update_product`	Reprices, recategorises, or retires a product	`products:write`
`get_product_availability`	Reports how many of a product are left to sell, per gym	`products:read`
`list_product_categories`	Lists the product categories, in display order	`products:read`
`create_product_category`	Adds a product category	`products:write`
`update_product_category`	Renames a category or moves it in the display order	`products:write`
`list_checkins`	Lists attendance records with filters	`checkins:read`
`get_checkin`	Opens one attendance record	`checkins:read`
`create_checkin`	Checks in an existing booking	`checkins:write`
`get_booking`	Opens one booking by id	`bookings:read`
`list_bookings`	Lists bookings in a date window, across every channel	`bookings:read`
`create_booking`	Creates a booking, optionally with a coach	`bookings:write`
`cancel_booking`	Cancels a booking	`bookings:write`
`list_booking_participants`	Lists the extra players on a booking	`bookings:read`
`add_booking_participant`	Adds a player to a booking	`bookings:write`
`remove_booking_participant`	Removes a player from a booking	`bookings:write`
`get_club`	Opens one of your gyms by slug, with amenities and rating	`clubs:read`
`list_content`	Lists CMS content - posts, FAQs, documents, and reusable blocks	`content:read`
`get_content`	Opens one published content item by slug	`content:read`
`create_content`	Creates a content item	`content:write`
`update_content`	Updates a content item, including taking it back to draft	`content:write`
`delete_content`	Permanently deletes a content item	`content:write`
`get_website`	Opens the website: pages, layout, theme, and its public and preview URLs	`website:read`
`list_websites`	Lists every website the organization owns, its default one first	`website:read`
`get_website_section_types`	Lists every section type a page can use, and the fields each takes	`website:read`
`get_website_page`	Opens one page with all of its sections and settings	`website:read`
`get_website_css`	Reads the website’s custom stylesheet	`website:read`
`list_website_releases`	Lists the publish history, newest first	`website:read`
`update_website`	Updates site-level settings: name, theme support, SEO defaults, and the languages the organization offers	`website:write`, plus `organization:write` for the language fields
`create_website_page`	Adds a page to the website	`website:write`
`update_website_page`	Updates a page’s title, SEO fields, or entire content	`website:write`
`delete_website_page`	Deletes a page	`website:write`
`update_website_section`	Changes one section on a page, leaving the rest alone	`website:write`
`update_website_layout`	Updates the header or footer, including navigation links	`website:write`
`set_website_css`	Replaces the website’s custom stylesheet	`website:write`
`publish_website`	Publishes the draft, making every pending edit public	`website:publish`
`rollback_website`	Restores an earlier published version and puts it live	`website:publish`
`list_media`	Browses or searches the media library	`media:read`
`create_media`	Registers an already-hosted image or video in the library	`media:write`
`update_media`	Updates a media item’s name, alt text, or caption	`media:write`
`delete_media`	Permanently deletes a file from the library	`media:delete`
`list_transactions`	Lists billing transactions, newest first	`transactions:read`
`get_transaction`	Opens one transaction by id	`transactions:read`

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.

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. Read get_website_section_types before composing a page, and take image URLs from list_media rather than guessing them.supportedLocales and defaultLocale on update_website are the exception. They 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.

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.

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.

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 table above, and nothing that changes data.
Requested read scopes are granted when you approve. They are listed under “This assistant will be able to” on the authorization page.
Everything that is not a read is opt-in, one at a time. Each appears under “Also allow it to make changes?” as a checkbox that starts unchecked - the writes, and also media:delete and website:publish, which delete a file for good and make draft edits public. Approving the page without ticking any of them produces a read-only connection, even if the client asked for everything.
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.

Discovery server

https://mcp.1club.ai/discovery - no token, no scopes. These search the public 1club.me marketplace across every listed gym and read only published information.

Tool	What it does
`search_clubs`	Searches gyms by sport, location, distance, price, rating, amenities, and date
`get_class_availability`	Returns a class with its availability status, current bookings, and capacity
`get_area_availability`	Checks a public area’s availability for a date or a date range
`get_instructor_availability`	Checks a public instructor’s availability for a date or a date range

These tools take marketplace ids, which are not the same as the ids an assistant sees on the admin server. Do not mix ids between the two servers.

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 messaging and the inbox, automations and promotions, invoices and payments, access control, and reporting. Contacts and memberships are readable and creatable but not deletable. Instructors are read-only and are configured in 1Club. Plans and individual class occurrences can be managed through their write tools; recurring-series creation remains in the 1Club dashboard. 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.

Getting started

Dashboard

Members

Operations

Revenue

Point of sale

Marketing

Messaging

Content & website

Analytics

Settings

MCP

Reference

Admin server

Reading the scope table

How a connection gets its scopes

Discovery server

What is not exposed

​Admin server

​Reading the scope table

​How a connection gets its scopes

​Discovery server

​What is not exposed

Admin server

Reading the scope table

How a connection gets its scopes

Discovery server

What is not exposed