Use Compteam with AI agents
Connect a compatible MCP client to discover public BJJ classes or securely manage your own Compteam attendance.
What the Compteam MCP server does
The Model Context Protocol (MCP) lets compatible AI agents use a small, controlled set of Compteam tools. Public discovery works without an account. Personal or linked-child information always requires a Compteam sign-in.
Available without signing in
- Find Compteam clubs that publish a public class schedule.
- List a club’s public classes for a selected week.
- View a club’s public membership plans, including recurring price and billing cadence, plus any one-time signup fee.
- View public branch details such as address, contact and social links, language, currency, policies, and links to booking, registration, and the club page.
Available after connecting your Compteam account
These account-connected features are available only through the Compteam ChatGPT/OpenAI plugin or an MCP client that Compteam has registered. The athlete must complete Compteam authentication in the chat before personal data or actions are available.
- List your own member profile and children linked to your account.
- View upcoming classes and limited membership or payment status.
- Confirm or cancel an RSVP for yourself or a linked child.
- Open and submit an inquiry for an eligible free trial class.
Register an MCP client
Public discovery does not require registration. If your client needs account-connected tools, send us the details below. We review each client manually and reply with the approved OAuth setup and access scope.
- Add the Compteam endpoint and test public discovery first.
- Submit your client details, security links, and exact OAuth redirect URIs.
- Compteam confirms the client registration and the capabilities available to it.
OAuth bootstrap for client operators
Use this read-only descriptor to discover the MCP resource, Supabase authorization-server metadata, required PKCE method, and registration request path. It never creates credentials or grants access; Compteam must approve and activate each client ID first.
Open OAuth bootstrap descriptor: https://api.compteam.io/api/v1/public/mcp-client-registration/bootstrapRequest client registration
Do not include passwords, client secrets, API keys, or member data.
Full MCP clients only · registration_full
Registration flows for full MCP clients
These account, branch, membership, billing, and consent flows are supported through an explicitly approved full MCP client (`registration_full`) after the athlete authenticates in the chat. They are not available to anonymous, OpenAI/ChatGPT marketplace, or `marketplace_safe` clients.
- Adult first registration: create an athlete account, select an existing gym, or start a new unmanaged gym.
- Imported and managed-profile claims: match an invited or imported profile after account verification without creating a duplicate athlete.
- Joining an additional branch: keep one personal profile while adding membership at another gym.
- Guardian-led registration for children under 16: a guardian creates the child profile and gives required training consent.
- Athlete-created unmanaged gyms: an athlete can create a branch that starts unmanaged and remains claimable by a branch administrator.
- New branch registration and unmanaged-branch claiming: create a new organization/branch or claim an eligible unmanaged branch during admin setup.
- Membership-plan eligibility and approval gates: age/tier eligibility, self-subscription approval, and branch activation rules are checked before access is granted.
- Exact terms versions and required consent: the current branch terms version, privacy/data-processing consent, and any membership signature are recorded.
- SEPA mandate validation: IBAN, account-holder details, mandate authorization, and branch billing requirements are validated before a plan is submitted.
- Signup-fee clearance status: registrations can remain pending until the one-time signup fee is reconciled or explicitly cleared by the branch.
- Optional authenticated adult profile photo: an adult may upload a profile photo after authentication; it can be skipped and added later.
Full MCP client access (`registration_full`) is granted per registered client ID. After OAuth, the athlete must authenticate in the chat and the client must refresh its tool list before these registration tools appear. OpenAI/ChatGPT and marketplace_safe clients cannot create athletes, branches, memberships, mandates, or consents. Sensitive billing and photo fields stay in the secure registration form.
Connect a compatible client
Registry-aware clients can find Compteam by its verified Registry name. Other MCP clients can connect directly to the HTTPS endpoint.
- Registry name
- io.compteam/compteam
- Endpoint
- https://api.compteam.io/mcp
- Transport
- Streamable HTTP
When a client accepts a JSON MCP server entry, use this generic configuration:
{
"mcpServers": {
"compteam": {
"type": "streamable-http",
"url": "https://api.compteam.io/mcp"
}
}
}Safety and account boundaries
- Connected tools can only access your profile or a child already linked to your account.
- The agent must ask for confirmation before changing an RSVP or submitting a free-trial inquiry.
- Membership plan details are for discovery only; membership signup, paid class checkout, and payments are not available through this MCP server.
- Authentication uses the client’s OAuth connection. Do not paste a normal Compteam web token into an MCP client.
Example prompts
After adding Compteam to your agent, try:
- “Find Compteam clubs with public BJJ classes.”
- “Show the public classes at this club next week.”
- “Show the membership plans and prices at this club.”
- “Show me this branch’s address, Instagram, policies, and public booking and registration links.”
- “Show my upcoming Compteam classes.”
- “Cancel my RSVP for tomorrow’s class.”
- “Ask this club about a free trial class.”