Wellness Project

What Wellness Project MCP server does

The Wellness Project MCP server gives compatible AI assistants access to health and fitness data collected in one Wellness Project account. Supported sources include Apple Health, Google Health Connect, Fitbit, Oura, Withings, Wyze, Hevy, Ultrahuman, Liftosaur, Polar, and selected WHOOP data. Manual and chat-based logging are also supported.

The server covers multiple wellness categories, including workouts, meals, hydration, sleep, recovery, heart data, body measurements, goals, labs, and wellbeing. Read operations retrieve synced or logged records. Write operations can add, modify, or remove entries when the user requests those changes.

How it works

The Wellness Project MCP server is hosted at https://wellnessproject.ai/api/mcp. The repository documents the production service and its tool catalog; it does not contain a self-hosted backend implementation. Clients connect to the same remote endpoint and authenticate through OAuth 2.1 with Dynamic Client Registration. Personal API keys are not part of the documented public connection flow.

The production registry advertises 73 public tools. Their names, annotations, and JSON Schemas are documented in the repository's generated catalog. Compatible MCP Apps UI clients can also render 15 interactive widget views, such as weekly sleep, workout, macro, steps, recovery, body composition, running, exercise progression, and wellbeing views.

Setup and configuration

Create an account at Wellness Project, then connect the desired health sources under Settings → Devices. Add the remote MCP endpoint to a supported client and complete the browser-based OAuth authorization. No local process, clone, client secret, or API key is required for the documented connections.

Claude Code provides a plugin installation flow using the wellness-project-mcp marketplace repository. Cline can add the endpoint as a remote server and should use the streamableHttp transport explicitly. Claude web, ChatGPT developer mode, Gemini Spark, Grok, and Mistral Le Chat each have client-specific connector setup steps in the repository. Availability and permissions can depend on the client, plan, workspace, or account.

Tools and capabilities

The Wellness Project MCP server supports conversational requests such as:

• Review training, sleep, recovery, heart-rate, or HRV trends.
• Retrieve workouts, meals, macros, body weight, or wellbeing records.
• Log meals, water, workouts, and other supported data.
• Compare progress against goals or examine exercise progression.
• Display structured views through supported MCP Apps UI clients.

Named widget tools include show_health_overview, show_week_sleep, show_workout, show_meal_diary, show_recovery, show_runs, and show_exercise_progression.

Limitations and notes

The Wellness Project MCP server depends on the data available from each connected source and on the integrations currently enabled for the account. WHOOP support is rolling out behind availability gating. Widget rendering requires a client that supports the MCP Apps UI extension, so other clients may return ordinary structured or textual tool results instead.

The repository does not document a local deployment option. ChatGPT write and modification access is plan-dependent, and other clients may impose their own connector or workspace requirements. The Wellness Project MCP server should therefore be evaluated against the target client's remote MCP, OAuth, and write-action support before deployment.