Skip to main content
Work through the symptom that matches what you see. If it still fails, contact support@1club.ai with the MCP client name, the endpoint, and the exact error text.

​
The client does not open 1Club sign-in

Check these items:
  1. The endpoint is exactly https://mcp.1club.ai/admin.
  2. The client supports remote MCP servers with OAuth.
  3. OAuth is selected as the authentication method, if the client asks.
  4. Pop-ups are allowed for the client and auth.1club.ai.
  5. A workspace administrator has enabled custom MCP apps or connectors when the client requires it.
Remove and re-add the connection after changing its authentication settings. MCP clients often cache the server metadata from the first setup attempt.

​
Sign-in succeeds but authorization is denied

Authorizing an MCP connection requires organization settings management permission.
  • Confirm you selected an organization where you are an admin or owner.
  • Ask an owner to grant the required permission if you can use the dashboard but cannot authorize MCP.
  • If the organization is on a free plan or trial, upgrade before connecting the admin MCP server.
The discovery server at https://mcp.1club.ai/discovery remains public and does not require authorization.

​
A tool fails with a permission error

Ask the assistant to call get_account. It returns the authorized organization and the scopes on the connection. Read effectiveScopes, not scopes: a full-access API key reports scopes as ["*"], and only effectiveScopes spells out what that expands to. Compare that list with the tools reference. An OAuth grant’s scopes are fixed once you approve them - there is no way to widen or narrow a live connection. To change them, revoke the connection under Settings > Artificial Intelligence > AI assistants (MCP), disconnect it in the client, and authorize it again, ticking the write permissions you need this time. If the assistant authenticates with a Platform API key rather than OAuth - which the admin MCP server also accepts, for developer-managed clients - then it is that key’s scopes that apply, and you edit them under Settings > Organization > APIs & webhooks.

​
The assistant is connected to the wrong organization

  1. Revoke the connection under Settings > Artificial Intelligence > AI assistants (MCP).
  2. Disconnect it in the MCP client.
  3. Connect again and choose the correct organization on the 1Club authorization page.
Every MCP connection is bound to one organization. It cannot switch organizations during a conversation.

​
I see a mix of marketplace and organization tools

The client is using an old or incorrect endpoint. Remove the connection and add the correct address: The admin and discovery servers never expose each other’s tools.

​
The tool list is missing new tools

Compare the client’s list with the tools reference. Re-scan tools or remove and re-add the connection. Many clients cache the tool catalog. The admin server covers classes, areas and blocks, bookings, check-ins, contacts and instructors, plans, memberships, products, content, media, the website, gyms, and transactions. A missing OAuth scope causes a permission error when a tool runs. It does not normally remove the tool from the list.

​
Everything worked, then stopped

Check these items:
  • The connection was revoked. Review connected assistants in 1Club.
  • The person who authorized it lost access. A connection carries the permission of whoever approved it. If they left the organization or no longer hold settings.manage.organization, the connection is revoked on its next tool call. Someone who still holds the permission has to connect the assistant again. Check this first when an assistant stops working around a staff change.
  • The organization downgraded. API and MCP access stop when the paid feature is no longer available.
  • It sat unused for 90 days. The client registration and its tokens are deleted, so the client has to register and authorize again.
  • The client lost its refresh credentials. Disconnect and complete OAuth again. Replaying a refresh token that has already been rotated revokes the whole connection, so a client that restores an old copy of its credentials has to reconnect. Parallel refreshes are not affected: tool calls that all refresh at once are treated as one rotation.
  • The rate limit was reached. MCP shares the Platform API limit of 100 requests per minute per organization. Wait a minute and retry.
The Last used column on the MCP page shows whether recent requests reached 1Club.

​
A write fails even though reading works

Read and write scopes are separate. For example, classes:read does not satisfy classes:write. The usual cause is that no write box was ticked on the authorization page. Every write capability is offered there as an individual checkbox that starts unchecked, so approving the page without touching it produces a read-only connection - which is the intended default, not a bug. Call get_account to see the granted scopes, then revoke and reconnect if the assistant genuinely needs to write. The operation can also fail a business rule after authorization:
  • A plan cannot be deleted while memberships reference it. Retire it by setting isActive to false.
  • A class cannot be deleted while affected future occurrences have active bookings or waitlist entries.
  • A booking cannot be checked in outside its configured window, when required payment is outstanding, or after it was already checked in. Only a confirmed or pending booking can be checked in - a cancelled or no-show booking is rejected.
Read the error returned by the tool before retrying. Do not repeatedly retry a validation or conflict error with a new idempotency key.

​
The assistant invents data instead of calling a tool

Confirm the 1Club app or connector is enabled for that conversation. Ask the assistant explicitly to use the 1Club tools, or name the tool you expect, such as list_classes or list_checkins.