Setup

Name: Setup
Author: turnnoblindeye

ASecurity

Connect the Wellness Project MCP server. Use when the plugin has just been installed, when the user asks how to connect Wellness Project, Apple Health, Fitbit, Oura, or Health Connect to Claude, or when a wellness-project tool call fails with an authentication or "no data" error.

2 stars

0 votes

0 copies

0 views

Added 9/19/2026

educationgoapisecurity

Works with

claude codecliapimcp

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add turnnoblindeye/wellness-project-mcp --skill setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Setup?

Add the live security badge to your README — it updates automatically with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/turnnoblindeye-setup/badge)](https://www.skillsdirectory.com/skills/turnnoblindeye-setup)

More formats (shields.io, HTML) on the badges page.

Download Zip

Files

SKILL.md

---
name: setup
description: Connect the Wellness Project MCP server. Use when the plugin has just been installed, when the user asks how to connect Wellness Project, Apple Health, Fitbit, Oura, or Health Connect to Claude, or when a wellness-project tool call fails with an authentication or "no data" error.
---

# Connecting Wellness Project

The plugin bundles one remote MCP server, `wellness-project`, pointed at
`https://wellnessproject.ai/api/mcp`. It needs a Wellness Project account and an
OAuth authorization before any tool returns data. Walk the user through the two
steps below in order.

## 1. Account and health sources

Tools read only what the user's account already holds, so an empty account
returns empty results rather than an error.

Tell the user to:

1. Create a free account at https://wellnessproject.ai.
2. Open **Settings → Devices** and connect the sources they want: Apple Health,
   Google Health Connect, Fitbit, or Oura.

Manual logging works without any device connected, so a user who only wants to
log workouts and meals by chat can skip step 2.

## 2. Authorize the connection

Run `/mcp`, select **wellness-project**, and choose to authenticate. Claude Code
registers itself dynamically and opens a browser for the Wellness Project OAuth
consent screen. No client ID, client secret, API key, or environment variable is
required.

After the user approves, `/mcp` shows the server as connected and its tools
become available.

## Verifying

Call a cheap read tool and check that it returns the user's own data, for
example `list_workouts` for the last 7 days or `list_body_metrics` for the last
30 days. An empty result means the account has nothing logged for that range,
not that the connection failed.

## Troubleshooting

- **Tools missing after install**: MCP servers register when the plugin loads.
  Restart Claude Code, then re-run `/mcp`.
- **401 or "Unauthorized"**: the OAuth grant expired or was revoked. Re-run
  `/mcp` and re-authenticate.
- **Connected but every read is empty**: no health source is connected and
  nothing has been logged. Return to step 1.
- **Revoking access**: the user can revoke the connection from Wellness Project
  account settings at any time.

## Scope

Every tool is scoped to the signed-in user's own account and enforced by
row-level security. The catalog of tools is in
[TOOLS.md](../../TOOLS.md) and the machine-readable schemas are in
[catalog/tools.json](../../catalog/tools.json).

Wellness Project is informational software, not a medical product.

Attribution

turnnoblindeye

View source More from turnnoblindeye →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- name: setup description: Connect the Wellness Project MCP server. Use when the plugin has just been installed, when the user asks how to connect Wellness Project, Apple Health, Fitbit, Oura, or Health Connect to Claude, or when a wellness-project tool call fails with an authentication or "no data" error. --- # Connecting Wellness Project The plugin bundles one remote MCP server, `wellness-project`, pointed at `https://wellnessproject.ai/api/mcp`. It needs a Wellness Project account and an OAuth authorization before any tool returns data. Walk the user through the two steps below in order. ## 1. Account and health sources Tools read only what the user's account already holds, so an empty account returns empty results rather than an error. Tell the user to: 1. Create a free account at https://wellnessproject.ai. 2. Open **Settings → Devices** and connect the sources they want: Apple Health, Google Health Connect, Fitbit, or Oura. Manual logging works without any device connected, so a user who only wants to log workouts and meals by chat can skip step 2. ## 2. Authorize the connection Run `/mcp`, select **wellness-project**, and choose to authenticate. Claude Code registers itself dynamically and opens a browser for the Wellness Project OAuth consent screen. No client ID, client secret, API key, or environment variable is required. After the user approves, `/mcp` shows the server as connected and its tools become available. ## Verifying Call a cheap read tool and check that it returns the user's own data, for example `list_workouts` for the last 7 days or `list_body_metrics` for the last 30 days. An empty result means the account has nothing logged for that range, not that the connection failed. ## Troubleshooting - **Tools missing after install**: MCP servers register when the plugin loads. Restart Claude Code, then re-run `/mcp`. - **401 or "Unauthorized"**: the OAuth grant expired or was revoked. Re-run `/mcp` and re-authenticate. - **Connected but every read is empty**: no health source is connected and nothing has been logged. Return to step 1. - **Revoking access**: the user can revoke the connection from Wellness Project account settings at any time. ## Scope Every tool is scoped to the signed-in user's own account and enforced by row-level security. The catalog of tools is in [TOOLS.md](../../TOOLS.md) and the machine-readable schemas are in [catalog/tools.json](../../catalog/tools.json). Wellness Project is informational software, not a medical product.