Skip to main content
Connect your assistant directly to 1club with OAuth. You do not need to create, copy, or store an API token. If you already connected an assistant with an API key, that connection keeps working - see Existing API-key connections.

Before you start

You need:
  • A 1club account with access to the organization you want to connect.
  • The AI assistants (MCP) permission, which is what lets you connect an assistant. Owners always have it and administrators hold it by default; an organization can grant it to other roles in Settings > Organization > Permissions.
  • A paid 1club plan. MCP and API access are locked on free plans and during a trial.
  • A client that supports remote MCP servers over HTTP, with OAuth.
The admin MCP address is:
An assistant you connected at the earlier address, https://mcp.1club.ai/admin, keeps working; you do not need to reconnect it. The 1club server is https://mcp.1club.me. It searches what gyms publish on the 1club network without an account, and asks a person to sign in with their 1club.me account only when they book.

Connect the admin server

1

Add a custom MCP connection

Open your assistant’s apps, connectors, or MCP settings. Create a custom remote MCP connection and enter https://mcp.1club.ai.
2

Start the connection

Select Connect, Authenticate, or the equivalent action. The client discovers 1club’s OAuth configuration automatically.
3

Sign in to 1club

Sign in on the 1club authorization page, titled Connect followed by the assistant’s name. Under Organizations it lists every organization you are staff of: the connection works in each of them, and in any you join as staff later, with what your role allows there. When you manage more than one, name the business in your question and the assistant acts in that one.
4

Review and authorize access

Under What followed by the assistant’s name and can do, the read access the client asked for is listed as Always included. Everything that changes data appears below it, under Make changes, as its own checkbox that starts unticked. Allow all changes ticks every one at once.Leave every box unticked and the assistant gets view-only access, even if the client asked for everything. Tick only the capabilities you want it to have, then select Allow access.
5

Test the connection

Ask: “Which 1club organizations are you connected to?” The assistant should call get_account and return the organizations it can act in and the granted scopes.
Allow access stays disabled until at least one capability is granted. That only bites when a client requests no read access at all: it has nothing under Always included, so you have to tick one of its Make changes boxes to connect it. Every client that asks for any read scope can be approved with nothing ticked.
What the assistant can do in each organization is what you approved, narrowed to what your role allows there. A manager who ticks Make changes for bookings still cannot delete a booking if their role cannot, and in a gym where they only teach, the assistant reaches only what an instructor sees.
Only connect assistants you trust. Review tool confirmations carefully before allowing a write or delete action.

Claude

Claude and Claude Desktop support OAuth-based remote MCP connectors.
  1. Open Settings > Connectors.
  2. Select Add custom connector.
  3. Enter a name such as “1club” and the URL https://mcp.1club.ai.
  4. Add the connector, then select Connect.
  5. Complete the 1club sign-in and authorization flow.
  6. Enable the 1club tools from Claude’s tools menu when you want to use them.
Team and Enterprise workspace owners may need to add the connector for the organization before individual users can connect it. See Anthropic’s remote MCP connector guide.

Claude Code

Claude Code speaks OAuth over HTTP MCP, so one command is enough and no header is needed:
The sign-in and authorization pages open when you first use the server. Run claude mcp list to confirm it is connected. For the 1club server, use the same command with https://mcp.1club.me.

ChatGPT

1club Admin is listed in ChatGPT’s plugins, so you can run your business from ChatGPT without entering an address or setting anything up by hand. ChatGPT then answers from your live data: how full this week’s classes are, who is booked, how many sessions a member has left, how sales are going.
  1. Open 1club Admin in ChatGPT, or search for “1club” under Plugins in ChatGPT.
  2. Select Install plugin, then Connect 1club Admin.
  3. Complete the 1club sign-in and authorization flow.
  4. Select Try in chat, or pick 1club Admin from the tools menu in any new chat.
Try asking “Which classes are on this week, and how full are they?” or “Find Alex’s upcoming bookings and sessions left on their membership.” It sees only what your role allows, and changes nothing unless you tick Make changes boxes when you connect. To disconnect, open the plugin in ChatGPT and select Manage, or revoke the connection in 1club under Settings > Integrations > AI assistants (MCP).
A ChatGPT workspace admin may need to allow third-party plugins before members of a Team, Business or Enterprise workspace can install it. You can still add https://mcp.1club.ai as a custom app in developer mode instead; see OpenAI’s developer mode and MCP apps guide.

The 1club server

Anyone can add https://mcp.1club.me as a custom connector, with no 1club admin account and nothing to approve. It searches the 1club network for gyms, independent professionals, and free times straight away. The first time someone asks it to book, list, or cancel their own bookings, the client opens a sign-in with their 1club.me account, and from then on the assistant books as them. See Discovery server for its tools.

Other remote MCP clients

Use the same endpoint and choose OAuth when the client asks how to authenticate:
1club supports dynamic client registration, the authorization code flow with PKCE, access-token refresh, and revocation. A compatible client discovers all of it from the endpoint alone, with no manual URLs and no client secret. If you are building the client rather than configuring one, this is what it will find: A request without a valid bearer token gets a 401 whose WWW-Authenticate header names the resource metadata document. That is the normal way to start the flow, not an error to work around.

Existing API-key connections

OAuth is the recommended path and the one to use for a new connection. An assistant that was connected with a Platform API key before OAuth existed keeps working: the admin server accepts any bearer credential the Platform API accepts, so a 1club_sk_live_... key sent on Authorization still authenticates. This path stays available for developer-managed clients that cannot complete an interactive sign-in. The remote configuration is the same endpoint with a request header:
The key’s own scopes decide what the assistant can do, exactly as they do for a direct API call, and revoking the key under Settings > Integrations > APIs & webhooks cuts the assistant off. A key acts for one organization and is not limited to particular gyms, and it is refused the tools that change staff roles and permissions. To move an existing connection to OAuth:
1

Remove the header-based connection

Delete the custom connector, app, or MCP entry in the client. Clients cache server metadata, so re-adding it is more reliable than editing it in place.
2

Add it again with OAuth

Follow Connect the admin server above. Choose OAuth when the client asks how to authenticate, and do not enter any header.
3

Revoke the old API key

Once get_account returns the right organization over the new connection, revoke the API key that assistant was using, so the credential stops working everywhere.

Local stdio setup

A developer can also run the MCP servers locally over stdio, which is what an editor or a script on your own machine talks to. This path has no OAuth and is meant for local development. The servers are not published to a package registry, so build one from the product repository and start it with npm start: admin-mcp for your organization’s data, or public-mcp for anonymous search of the 1club network. Install the shared package first (npm install --prefix ../mcp-shared), then npm install and npm run build in the server’s own folder. They read these environment variables: Set BASE_URL explicitly. Left unset it points at a local API rather than failing, so an assistant aimed at production will simply find nothing there. Point your client’s stdio command at the built entry point. There is no global binary to install.

Verify access

Confirm these checks after connecting:
  1. Ask the assistant to call get_account. Confirm the organizations are correct, and read the reach from effectiveScopes rather than scopes.
  2. Ask for next week’s classes. This confirms classes:read access.
  3. Ask the assistant to list recent check-ins. This confirms checkins:read access.
  4. Before testing a write, use a disposable record and review the tool confirmation.

Review connected assistants

Go to Settings > Integrations > AI assistants (MCP). The page shows the MCP endpoint to hand to a client, and lists under Connected assistants every assistant that can act in this organization, with the Assistant, who it was Authorized by, the Scopes it holds here, and when it was Last Used. Connections appear here no matter who created them, because an assistant is authorized by whoever connects it rather than created on this page. A connection made by someone who is staff of several organizations shows in each of them, with the scopes it holds in that one. Seeing what has access, and cutting it off, is what the page is for. Viewing it needs settings.read.organization; revoking needs settings.manage.organization.

Disconnect or revoke

  • Disconnecting in the MCP client removes the connection from that client.
  • Revoking it in 1club with Revoke connection ends its access to this organization immediately. A connection that also works in other organizations keeps working there. The client must complete OAuth again to reconnect here.
  • There is nothing to rotate on an OAuth connection. The access and refresh credentials are managed by the client and 1club, and never handled by you. An access token lasts an hour, and the client refreshes it silently. Each refresh issues a fresh pair, so an assistant in regular use stays connected indefinitely and 30 days is the idle limit, not a deadline.
  • An approved scope set cannot be edited afterwards. To give an assistant a capability you did not tick, or to take one back, revoke the connection and authorize it again with the boxes you want.
Two things also revoke a connection without anyone pressing a button:
  • The authorizing person losing access. A connection carries the access of whoever approved it. If that person leaves an organization, or their role there loses the AI assistants (MCP) permission, the connection stops working in that organization the next time the assistant calls a tool.
  • Long disuse. A client that has not been used for 90 days is deleted along with its tokens, so it has to register and authorize again.
If setup fails, see MCP troubleshooting.