Skip to main content
FITsociety MCP provides company/coach access and client AI access through one remote endpoint. Use the grant approved for the account and company you want to connect.

Endpoints

Send MCP requests to https://mcp.fitsociety.io/mcp/v1 with Authorization: Bearer <credential>. Credentials are accepted in the header only. GET /mcp/v1 is not a compatibility SSE stream or a handshake endpoint. See Connection & Protocol for supported protocol versions, headers, tool discovery, and write idempotency. See Authentication & OAuth for OAuth request and token examples.

Company/coach connections

A Manager or Admin coach approves company-scoped modules, optional write tools, and required consent flags. They can connect using OAuth or create a static company MCP API key in the coach dashboard. A static key is displayed only once. Rotating a key invalidates the old key and displays its replacement once. Revoking a grant stops its static key and all associated OAuth tokens. The grant owner must retain active Manager or Admin access to the company.

Client AI connections

A client approves OAuth access to their own records in one connected company. Client grants have subjectType: "client" and a fixed subjectClientId, and can use only explicit client_ai_* modules. Static company keys cannot create client AI access. The company MCP feature, the client’s AI access for that company, and the company client MCP policy must all allow the connection. If access is disabled, the client can ask their coach or company admin to enable it and then retry consent. Requesting access does not issue a grant or tokens. Clients can revoke their own grants in their client connection settings.

Permission matrix

Tool access depends on these grant settings and account requirements:

Response contracts

Runtime MCP calls use JSON-RPC 2.0:
Runtime errors also use JSON-RPC:

Error categories