Wellness Project

What the Wellness Project MCP server does

The Wellness Project MCP server gives MCP-compatible assistants access to health and fitness information held in a Wellness Project account. Supported data includes workouts, nutrition, sleep, recovery, body metrics, goals, labs, and wellbeing records. The account can combine data from Apple Health, Fitbit, Oura, and Health Connect, subject to the sources connected by the user.

The service supports both read and write operations. An assistant can answer questions about trends, retrieve logged records, and compare measures over a requested period. It can also add, change, or remove entries when the user asks, such as logging a meal or recording water intake.

How it works

The Wellness Project MCP server is hosted at https://wellnessproject.ai/api/mcp. The repository documents and catalogs the hosted service; it does not contain the private backend and is not intended to be run as a self-hosted server.

After connecting a client, the assistant selects an appropriate tool from the production registry based on the request. The public catalog lists 73 advertised tools, while 15 interactive tools can return structured views through the MCP Apps UI extension. These views cover areas such as weekly workouts, sleep, macros, body composition, recovery, running, exercise progression, and wellbeing.

Authentication uses OAuth 2.1 with Dynamic Client Registration. The current public connection flow does not use personal API keys.

Setup and configuration

Create an account at wellnessproject.ai and connect desired health sources under Settings → Devices before configuring a client. Use the same MCP endpoint for each supported connection.

Claude and Cline use the remote endpoint directly. Claude Code installs a plugin containing the server configuration and setup skill. Gemini CLI installs an extension from the public repository and authenticates through a browser. Cline should be configured with the streamableHttp transport rather than relying on its legacy SSE fallback.

OAuth approval is completed in the client or a browser. Gemini CLI requires browser access and a localhost callback during authentication. ChatGPT availability and write permissions depend on the account plan, while Gemini Spark and Grok access may also depend on service eligibility or plan settings.

Tools and capabilities

The catalog groups the advertised tools by health domain. Examples of supported requests include:

• Review training activity or workout progress.
• Inspect sleep history and trends.
• Compare resting heart rate with HRV.
• Log meals, calories, water, or other records.
• Check progress toward goals.
• View weight, body composition, recovery, steps, macros, or wellbeing.

Interactive widget tools include show_health_overview, show_week_workouts, show_week_sleep, show_recovery, show_runs, and show_exercise_progression, among others. Widget availability depends on whether the MCP client supports the MCP Apps UI extension.

Limitations and notes

The Wellness Project MCP server requires an account and connected data sources; it does not itself describe a replacement for Apple Health, Fitbit, Oura, or Health Connect. The repository is documentation and a catalog for the hosted service, not a deployable implementation.

Client support is not uniform. Some clients may offer read-only access, restrict write actions, require a particular plan, or lack interactive widget rendering. The generated tool catalog represents advertised public tools and excludes admin-only tools and retired tools that may remain callable by older cached clients.