Connect an AI assistant with MCP¶

Experimental

MCP support is an experimental feature of the Public API during the Beta test phase. Tool coverage grows as endpoints are added to the Public API, and access is granted per user account by the bsport team. Avoid relying on it for production workflows.

The bsport MCP server lets a compatible AI assistant use selected Public API operations as tools. The assistant can discover an operation, ask for its inputs, and call it without you copying API schemas or writing HTTP requests.

For an overview of capabilities, access requirements, and compatible assistants, start with the MCP overview. This guide contains the detailed setup steps for each client.

Model Context Protocol (MCP) is an open standard for connecting AI applications to tools and data. The bsport server covers management operations available through the Public API. For the authoritative and current coverage, use the API reference V2 instead of relying on a fixed tool list in this guide. MCP tools are generated from the V2 management operations.

Review actions before approving them

MCP tools can read or change bsport data. Check the inputs and requested action before approving a tool call. Data returned by a tool is also shared with the AI provider under that provider's terms.

Before you connect¶

You need:

A bsport company or franchise manager account that the bsport team has granted production MCP access. Access is granted to the user account, not to every user in a company.
An AI client that supports remote MCP servers over Streamable HTTP, OAuth authorization-code authentication with PKCE, and dynamic client registration.

The production MCP server URL is:

https://public.production.bsport.io/mcp

MCP authentication uses your bsport account through OAuth. Do not enter a Public API key, OAuth client ID, or OAuth client secret. Compatible clients register themselves and open the bsport sign-in page in your browser.

ChatGPT¶

In ChatGPT, open Settings > Security and login and enable Developer mode.
Open ChatGPT Plugins, select the plus button, and create a developer-mode app.
Give the app a name such as bsport, then enter the production MCP server URL above.
Complete the bsport sign-in and authorization flow in your browser.
In a conversation, open the plus menu, choose Developer mode, and enable the bsport app.

See OpenAI's ChatGPT Developer mode guide for current availability, controls, and UI details.

Claude¶

In Claude, open Customize > Connectors.
Select +, then Add custom connector.
Enter a name such as bsport and the production MCP server URL above. Leave the optional OAuth client ID and client secret empty.
Complete the bsport sign-in and authorization flow.
In a conversation, use + > Connectors to enable the bsport connector.

For Team and Enterprise plans, an Owner must first add the connector under Organization settings > Connectors. Each user then connects their own bsport account. See Anthropic's remote MCP connector guide for plan-specific instructions.

Claude Code¶

Add the server from a terminal:

claude mcp add --transport http bsport https://public.production.bsport.io/mcp

Start Claude Code, run /mcp, select bsport, and complete authentication in your browser. See the Claude Code MCP documentation for configuration scopes and management commands.

Cursor¶

Add the following server to your project or user MCP configuration:

{
  "mcpServers": {
    "bsport": {
      "url": "https://public.production.bsport.io/mcp"
    }
  }
}

Open Cursor's Customize page, enable the bsport server, and complete OAuth in your browser. See the Cursor MCP documentation for configuration locations and server controls.

Gemini CLI¶

Add the server from a terminal:

gemini mcp add --transport http bsport https://public.production.bsport.io/mcp

In Gemini CLI, run /mcp auth bsport and complete authentication in your browser. See the Gemini CLI MCP documentation for more configuration options.

Other MCP clients¶

Use the production server URL with the client's remote or HTTP transport. The client must support OAuth authorization-code authentication with PKCE and dynamic client registration. Some clients display optional OAuth client ID and client secret fields; leave them blank. A client is incompatible with the bsport server only if it requires pre-registered credentials and cannot perform dynamic client registration.

Start a conversation¶

Tell the assistant what you want to do:

Use bsport to list tomorrow's bookings.

For a franchise account, ask for the company by name: for example, "Show tomorrow's classes for Kaizen Lyon." Your assistant can discover the companies you can access and select the right one. If several companies match, it should ask you to clarify before taking action. You do not need a separate connection for each company.

Accounts attached to a particular company keep access to that company, including accounts that also have a franchise role.

bsport publishes its catalog through standard MCP tool discovery; it does not need a separate server-side tool search endpoint. Some clients load all tool descriptions immediately, while others load them only when needed. Claude Code, for example, enables tool search by default and loads matching definitions on demand. This behavior is controlled by the AI client. You can disable tools you do not need when your client provides tool controls.

Troubleshooting¶

Access is denied during sign-in: confirm that the bsport team granted MCP access to your active company or franchise manager account.
The assistant asks which company to use: give the company name. The assistant can find it among your accessible companies; you do not need to look up its ID.
The server does not connect: confirm that the client supports remote MCP, Streamable HTTP, OAuth authorization-code with PKCE, and dynamic client registration. Organization policies can also prevent users from adding custom connectors.
Tools look out of date: refresh or reconnect the server in the client's MCP settings.

Return to the MCP overview, or explore the complete API reference V2.