subjectType: "client" and a fixed subjectClientId.
Client MCP is available only when the company MCP integration feature is
enabled, the client is connected to the active company, client AI access is
enabled for that client-company relationship, and the company’s client MCP
policy allows client connections plus the requested client_ai_* modules.
Client Consent Flow
Clients connect from the central FITsociety connect page; they do not need to know their portal address. Client MCP consent never happens in the coach dashboard.- The client signs in with their client email and password.
- The page lists the companies the client can sign in to. Each company shows
whether AI connections are available, or why not:
company_blocked,company_ai_disabled,mcp_feature_disabled,client_ai_disabled, orclient_mcp_disabled. - The client picks an available company and reviews the requested modules, write tools, and consent flags before approving or declining.
state.
Restart the
connection from the AI client if the request has expired or was already used.
See Authentication & OAuth for the OAuth flow.
The approval gate is strict:
- If company MCP access is disabled, approval fails with
COMPANY_MCP_FEATURE_DISABLED. - If the client is not connected to the active company, approval fails with
COMPANY_MCP_CLIENT_COMPANY_CONNECTION_REQUIRED. - If client AI access is disabled for that company relationship, approval
fails with
COMPANY_MCP_CLIENT_AI_DISABLED. - If the company’s client MCP policy is disabled or has no allowed modules,
approval fails with
COMPANY_MCP_CLIENT_MCP_DISABLED. - Only after those checks pass can the client approve explicit
client_ai_*modules and optional write tools that the company policy allows.
If the client portal offers a “request access” action, use it to ask your
coach or company admin to enable access. This request does not approve an MCP
connection or issue tokens. After access is enabled, retry the OAuth flow and
review the connection permissions.
How It Differs
Client grants cannot request coach/company modules such as
clients,
client_notes, bookings, or invoices. Only the client AI modules listed
below are available to client grants.
Client AI Modules
Consent
Client AI modules follow the same sensitivity model as company MCP:healthmodules require explicit health data consent from the client.private_communicationmodules require explicit private communication consent from the client.operationalmodules do not require an extra consent flag beyond the OAuth approval.
Runtime Filtering
At runtime,tools/list and tools/call are filtered by:
subjectTypesubjectClientIdallowedModulesallowedWriteToolshealthDataConsentprivateCommunicationConsent- company MCP integration feature
- client AI access for the active company relationship
- company client MCP policy
- grant status and expiry
client_ai_* modules. Every tool
call is limited to the authenticated client.