Coach Watts

What Coach Watts does

The Coach Watts MCP server provides remote, OAuth 2.0-protected access to data in the Coach Watts endurance coaching platform. Its documented scope covers training, nutrition, wellness, and performance information. That makes it relevant for AI workflows that need an athlete’s broader context instead of a single activity stream.

Coach Watts itself is designed for cyclists, runners, and triathletes. The platform can aggregate information from a range of endurance and wellness services, including Intervals.icu, Strava, Whoop, Oura, Withings, Garmin, Wahoo, Polar, Yazio, Hevy, Fitbit, Rouvy, Ultrahuman, and Telegram. The available data depends on which integrations are configured in the Coach Watts deployment.

How it works

The Coach Watts MCP server is described as a remote MCP service. An MCP-compatible AI client authenticates through OAuth 2.0 before accessing the server’s data scope. The provided material does not state whether the service uses a particular MCP transport, publish a connection URL, or describe the authorization scopes presented to clients.

Coach Watts uses the connected data to support endurance-coaching functions such as workout analysis, daily recommendations, training-plan generation, fitness and fatigue analytics, nutrition tracking, and interactive chat. These platform capabilities provide context for the data exposed through the MCP connection, but the README does not map them to named MCP tools or specify which operations are read-only or mutating.

Setup and configuration

Use the Coach Watts MCP server when you have access to a deployed Coach Watts instance and an MCP client that supports OAuth 2.0. The supplied documentation does not include a server URL, client configuration example, callback URL, token instructions, or a list of required environment variables for the remote MCP service.

The repository’s local application setup is separate from connecting to the remote MCP service. Running the full Coach Watts application requires Node.js 24, Docker for PostgreSQL, a Google Cloud account for authentication and Gemini, database migrations, and provider API keys as needed. Those instructions are for deploying the platform, not a documented MCP-client installation procedure.

Tools and capabilities

The documented data areas include:

• Training and workout information
• Nutrition logs, macros, and hydration
• Wellness, recovery, sleep, and related health measurements
• Performance metrics and analytics
• Coaching context used for recommendations and planning

The Coach Watts MCP server’s individual tool names and argument schemas are not included in the supplied material. Review the deployed server’s MCP metadata or project documentation before building an agent integration that depends on specific tool contracts.

Limitations and notes

OAuth 2.0 is required for the remote connection, so an agent needs a compatible authentication flow and permission to access the relevant Coach Watts data. No public MCP endpoint, OAuth provider configuration, supported-client matrix, rate limits, or versioned API contract is provided here.

The platform supports ten listed interface languages and timezone handling, but the supplied material does not establish that these localization features affect MCP responses. Likewise, the presence of a provider integration in Coach Watts does not by itself document a separate MCP tool for that provider. Confirm the deployed instance’s enabled integrations and exposed capabilities before selecting this server.