Skip to main content
FITsociety MCP exposes 37 modules, 297 tools, and 144 write tools. The registry has two subject surfaces:
  • Company/coach tools are approved by a Manager or Admin coach and operate on company-scoped client, calendar, finance, health, messaging, and nutrition data.
  • Client AI tools are approved by the client and operate only on that client’s own records in the active company context. The client must be connected to the company, have client AI access enabled, and the company MCP integration feature must be enabled.
Both surfaces use the same remote MCP endpoint:

Module Registry

Write Tool Registry

Write tools are hidden unless the grant is not read-only and the exact tool name is present in allowedWriteTools.

Tool Execution

Call tools through standard JSON-RPC:
Use tools/list after authorization to see the exact tools available for the current grant. The result is filtered by subject type, modules, consent flags, read-only state, write-tool permissions, and the relevant feature gate. Company grants require the company MCP integration feature. Client AI grants require client AI access for the connected company.

Shared member fields and tags

The company/coach clients module supports: Enable each write separately in the connection’s write-action grants; enabling member-value writes does not enable definition writes. Writes require an idempotency key through the tool argument or MCP request metadata. Reuse the same key and arguments to replay a completed operation. Normal query budgets, rate limits, auditing and company/client access checks apply. These tools are not available to client AI connections. Definition field inputs follow the shared field library contract. Create requires a stable key, localized label and type; updates cannot rename a key. Definition reads return customFields and pagination metadata. Definition writes return customField; delete returns key, deleted and retained. Deleting a used field deactivates and hides it while preserving member values. No definition operation rewrites member values.
For member values, supply 1–100 {key, value} entries. Values are strings, numbers, booleans or null. The selected member must be accessible in the connection’s company. Only active, non-hidden fields with clientPage usage are writable. Automatic numbering fields remain read-only. Other member values are preserved. Use null or an empty string to clear a value; dates use YYYY-MM-DD. Values are checked against the configured field type and options.
A successful value write returns clientId and updatedKeys; use get_client to read the resulting values. Value changes may emit configured client.updated webhooks. They do not send member emails. Invalid inputs return validation errors, inaccessible members fail access checks and concurrent library edits return a conflict. Read the current library before retrying a conflicting edit with a new operation key.