Skip to main content
Client MCP access lets an AI client act only for the authenticated client who approved the connection. It uses the same remote MCP endpoint as company MCP, but the grant has 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.
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.
  1. The client signs in with their client email and password.
  2. 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, or client_mcp_disabled.
  3. The client picks an available company and reviews the requested modules, write tools, and consent flags before approving or declining.
Clients who sign in with Google or Microsoft can still continue through the company-branded client portal. Consent requests are single-use and valid for 10 minutes. Approval or denial redirects back to the AI client with the original 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:
  1. If company MCP access is disabled, approval fails with COMPANY_MCP_FEATURE_DISABLED.
  2. If the client is not connected to the active company, approval fails with COMPANY_MCP_CLIENT_COMPANY_CONNECTION_REQUIRED.
  3. If client AI access is disabled for that company relationship, approval fails with COMPANY_MCP_CLIENT_AI_DISABLED.
  4. If the company’s client MCP policy is disabled or has no allowed modules, approval fails with COMPANY_MCP_CLIENT_MCP_DISABLED.
  5. 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

Client AI modules follow the same sensitivity model as company MCP:
  • health modules require explicit health data consent from the client.
  • private_communication modules require explicit private communication consent from the client.
  • operational modules do not require an extra consent flag beyond the OAuth approval.

Runtime Filtering

At runtime, tools/list and tools/call are filtered by:
  • subjectType
  • subjectClientId
  • allowedModules
  • allowedWriteTools
  • healthDataConsent
  • privateCommunicationConsent
  • company MCP integration feature
  • client AI access for the active company relationship
  • company client MCP policy
  • grant status and expiry
Client grants can discover and call only client_ai_* modules. Every tool call is limited to the authenticated client.