FITsociety

FITsociety MCP

Connect AI assistants to your approved FITsociety coaching and fitness data.

Documentation · Setup guide · MCP Registry · Support

Connect

Add a remote MCP server in your AI application's settings:

Setting	Value
Name	FITsociety
Server URL	https://mcp.fitsociety.io/mcp/v1
Transport	Streamable HTTP
Authentication	OAuth

1. Add the server URL in an MCP client that supports remote HTTP connections and OAuth.
2. Complete the FITsociety sign-in flow for your coach or client account.
3. Review and approve the requested modules and permissions.
4. Ask the assistant to use your connected FITsociety data.

FITsociety hosts the server. You do not need to clone this repository or install a local server to connect.

Client-specific guides

• ChatGPT
• Claude
• Cursor
• Codex
• Gemini
• Agent setup

These guides describe direct connections. Marketplace availability is managed separately by each platform.

What you can do

Available tools depend on your account, company settings, and approved connection permissions.

Coaches can work with company-scoped clients, bookings, calendars, invoices, coaching records, nutrition, training, and conversations. Selected write actions can be enabled through the consent flow.

Clients can access their own permitted records, including bookings, credits, workouts, and nutrition. Client access requires the company's MCP integration and client MCP policy, an active company relationship, and the client's AI entitlement.

Example prompts:

• “Find a client by name and summarize their recent bookings.”
• “Show the workout plans assigned to me.”
• “Review my current credits without making a booking.”
• “Find squat exercises in the exercise library.”

See the current tools and modules for the maintained catalog and client AI access for client-specific permissions.

Permissions and privacy

Each connection is scoped to the approved company and account. Read access, write actions, health information, and private communications are controlled by the connection's permissions and consent. Access can be revoked in FITsociety.

See grants and permissions, authentication, and security and privacy.

Registry and versions

The official MCP Registry identity is io.fitsociety/mcp. The published server release is 1.0.0.

server.json mirrors the published registry manifest. CHANGELOG.md records public release changes. The release version is separate from the negotiated MCP protocol version and the /mcp/v1 endpoint path.

The hosted server supplies its live tool catalog and output schemas. This repository contains public connection information and registry metadata; the hosted implementation is maintained by FITsociety.

Help and feedback

For connection problems, start with troubleshooting. Open a GitHub issue for documentation feedback or reproducible integration issues. Contact FITsociety support for account-specific help or security reports.

Keep passwords, tokens, and personal coaching or health data out of public issues.