Skip to main content
This guide explains how coaches and company admins configure company/coach MCP access. Client MCP access is different: it is approved by the client in the client portal OAuth flow, requires the company mcp feature, requires client AI access to be enabled for that client-company relationship, and is limited by the company client MCP policy to explicit client_ai_* modules. See Client AI Access for that surface.

Prerequisites

The coach creating or approving the grant must:
  • have active access to the company
  • hold a Manager or Admin role
  • have access to the MCP settings in the coach dashboard
MCP is available to every company. Create a grant to authorize an AI connection.

Create a grant

A grant defines what an AI client can access. For a static company MCP API key:
  1. Open the company MCP settings.
  2. Create a new MCP grant.
  3. Give the grant a clear name, such as Claude - read-only client review.
  4. Choose an expiry period.
  5. Select allowed modules.
  6. Decide whether write tools should be enabled.
  7. Save the grant and copy the generated API key once.
For company/coach OAuth clients, the coach approves the grant during the consent flow started by the AI client.

Choose modules

Select only the modules the assistant needs. For example:
  • client lookup: clients
  • booking analysis: clients, bookings, calendar_events
  • invoice review: clients, invoices, subscriptions
  • nutrition check-ins: clients, nutrition_plans, nutrition_logs
Health and private communication modules require extra consent.

Enable write tools

Keep grants read-only unless the assistant must create or update data. When write access is needed, enable only the specific write tools required for the workflow. For example:
  • create_client for onboarding flows
  • create_booking for booking flows
  • update_attendance for attendance corrections
  • create_client_note for coach note workflows
  • nutrition plan/log write tools for meal-plan maintenance
The assistant should still ask for confirmation before using write tools. Use the Tools & Modules Registry page for the complete current write-tool list.

Handle client MCP requests

Client MCP requests are requests to enable client AI access and client MCP policy permissions for one client in one company. They are separate from company/coach MCP grants. If a client starts MCP OAuth while client AI access is disabled, no grant or tokens are issued. If the client portal offers a request-access action, the client can use it to ask their coach or company admin to enable access. After access is enabled in the client/company settings, the client can retry the connection and review its permissions.

Revoke access

Revoke a grant when:
  • a client integration is no longer used
  • a credential may have been exposed
  • the owning coach leaves the company
  • write access was granted temporarily
Revocation immediately stops the API key and revokes active OAuth tokens for the grant. Clients revoke their own client AI grants from their client connection settings.

Check audit logs

Use the MCP audit log to review what the assistant has done. Audit entries show:
  • which grant was used
  • which tool was called
  • when it was called
  • whether it succeeded or failed
  • which argument names were supplied
Argument values are not stored in the MCP audit log.