Connect your fitness business to ChatGPT and Claude.
FITsociety is fitness, gym and studio management software with its own Model Context Protocol (MCP) integration. Give your AI assistant permission to work with your client records, bookings, training and nutrition data, and invoices, so you can turn questions into useful coaching and business insights.
Start with read-only access. When you need an assistant to create or update records, approve the specific actions it can perform.
MCP is an open standard that lets AI applications discover and use tools from another system. Instead of copying information into a chat, you connect an assistant to a defined set of FITsociety tools.
The assistant can then request the information needed for your question, within the access you approved. For personal trainers, online coaches, studios and gyms, that means working with coaching and business information from the same platform.
FITsociety hosts the MCP server. You do not need to install or maintain a server of your own. Your organisation needs MCP access enabled, and your chosen AI application must support remote MCP connections.
For the protocol itself, read the official Model Context Protocol introduction and MCP specification.
FITsociety MCP connects your gym, studio or coaching business to AI applications that support its remote MCP interface:
The same FITsociety access rules apply to every client. Compatibility depends on the application’s transport and authentication support; available tools depend on the connection’s permissions and enabled features.
Use natural-language requests to review your business and prepare your next coaching action. Available tools depend on your approved modules, permissions and enabled features.
Review attendance, cancellations and booking consistency over a chosen period. Try: “Summarise attended, cancelled and absent sessions for this client over the last 30 days.” Requires client and booking access.
Bring together the measurements, habits or nutrition logs you have permission to view. Try: “Summarise this client’s recent progress and suggest questions for our next check-in.” Relevant modules and explicit health-data consent are required.
Inspect invoice information and summarise balances or items needing follow-up. Try: “Review this client’s unpaid invoices and summarise what needs attention.” Invoice tools provide information; this workflow does not collect payments or change invoice status.
Inspect a client’s assigned training plan and suggest changes for the coach to review. Try: “Review this client’s current training plan and draft a revised session for my approval.” Training access, enabled training features and health-data consent are required. Saving or assigning changes also requires the relevant write tools.
Ask your assistant to draft a follow-up note, review it, then request that it be saved. This requires client-notes access, private-communication consent, write access and the specific create_client_note tool. Drafting and saving are separate steps.
For company and coach workflows, a coach with an active Manager or Admin role approves the connection. MCP must be enabled for your organisation. If you cannot access it, contact your company administrator or FITsociety support.
Use this remote MCP server URL:
https://mcp.fitsociety.io/mcp/v1See the FITsociety ChatGPT guide and OpenAI’s current custom MCP instructions for setup details.
See the FITsociety Claude guide and Claude’s current connector instructions. Other compatible remote MCP clients can use the same endpoint; consult our connection documentation for protocol requirements.
Each FITsociety MCP connection has an approved set of permissions. Connecting an assistant does not give it unrestricted access to your account.
Your chosen AI provider receives the results requested through the connection and handles them under its own terms and privacy policy. Revoking access stops future requests; it does not recall information already shared or messages already delivered.
For write workflows, ask your assistant to show you the proposed change before saving it. The connection’s permissions control what it can execute; the review step is part of how you use the assistant.
Read the MCP security and privacy documentation and grants and permissions guide.
The FITsociety REST API and MCP integration serve different integration needs. Use the API when building software that calls defined endpoints. Use MCP when an AI application needs to discover and call permitted FITsociety tools during a conversation or agent workflow.
MCP complements the API. It does not mean every API endpoint is available as an MCP tool, and it does not remove authentication or authorisation requirements. Check the current tool catalog for the actions your integration needs.
Yes. FITsociety provides its own hosted MCP server at https://mcp.fitsociety.io/mcp/v1. It exposes a defined catalog of tools for approved company, coach and client workflows. MCP must be enabled for the organisation before a connection can be used.
You can connect ChatGPT and Claude through their custom remote MCP options. FITsociety also documents Cursor and Codex connections. Custom agents and developer-built applications can connect when they support the documented HTTP transport and authentication. Workspace permissions, enabled features and the approved grant determine availability.
A Manager or Admin coach with active company access can configure company MCP connections once the company’s MCP feature is enabled. Ask your company administrator or FITsociety support if MCP access is unavailable. You choose modules and permissions during the authorisation flow or in the company MCP settings.
No. FITsociety hosts the server. Add its remote URL to a compatible AI application and complete authorisation. Developers building their own integration can use the connection and authentication documentation for the supported transport and OAuth flow.
Yes. Connections are read-only by default. Your assistant can search, inspect and summarise permitted records without creating or changing them. Only the modules and data covered by the approved connection are available.
Selected tools support write actions, such as creating a coach note or managing a booking. You must enable write access and explicitly allow the relevant tool. Additional module permissions, enabled features and sensitive-data consents still apply. Ask the assistant to present changes for review before executing them.
The provider receives the results needed for the requests made within your approved permissions. Health-related information and private communication require extra consent. You can revoke the connection in FITsociety to stop future access. Revocation does not recall results already shared with the provider.
No. The REST API supports applications that call endpoints directly; MCP provides a discoverable tool interface for AI applications. They complement each other. Consult the MCP tool catalog and API documentation to choose the interface that supports your workflow.
See how FITsociety brings fitness management, coaching and permissioned AI access together. Tell us which workflows you want to simplify, and we can show you where MCP fits.
Already using FITsociety? Read the setup documentation to get started.