function-health-mcp

Function Health MCP

An MCP server and CLI for Function Health lab results. Query biomarkers, track changes between visits, and get health recommendations — all from Claude Code or the command line.

Features

• 13 MCP tools for querying lab results, biomarker deep dives, change detection, and more
• CLI with matching commands for terminal use
• Offline-first — query tools read from local storage, only sync/check hit the API
• Test round model — automatically groups multi-visit lab results by requisitionId into complete test rounds
• Change detection — compare test rounds to see what improved, worsened, or changed significantly
• Biomarker history — track any biomarker across all your test rounds
• Secure — credentials stored with owner-only permissions (0o600 files, 0o700 directories)

Quick Start

Option A: Install as Claude Code Plugin

Install from the plugin marketplace for zero-config MCP setup with skills included:

/plugin marketplace add daveremy/function-health-mcp
/plugin install function-health-mcp@function-health-mcp-plugins

This automatically configures the MCP server and installs the /fh-lab-results skill.

Option B: Manual MCP Setup

Add to your project's .mcp.json:

{
  "mcpServers": {
    "function-health": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "function-health-mcp"]
    }
  }
}

Optionally copy the skills for guided slash commands and background context:

mkdir -p .claude/skills
cp -r node_modules/function-health-mcp/skills/fh-lab-results .claude/skills/
cp -r node_modules/function-health-mcp/skills/fh-usage .claude/skills/

Authenticate

First, authenticate via the CLI (password input is hidden):

npx -y -p function-health-mcp function-health login

Automatic Re-authentication

Firebase tokens expire after 1 hour and are normally refreshed automatically. If the refresh token is revoked (e.g., after extended inactivity), you can provide credentials for hands-free re-authentication:

# Option 1: Environment variables (e.g., in .envrc with direnv)
export FH_EMAIL="[email protected]"
export FH_[REDACTED:Password]

# Option 2: .env file (works without direnv — ideal for MCP plugins)
# Add to ~/lifeos/.env or ~/.env:
[email protected]
FH_PASSWORD=your-password

The MCP server checks process.env first, then falls back to .env files. This means it works even when launched via npx (e.g., as a Claude Code plugin) where direnv isn't active.

Then ask Claude about your lab results:

"Show me my lab results" "Deep dive on my Vitamin D levels" "What changed between my last two visits?"

Claude will sync your data and show your results conversationally.

Alternative: Install from source

git clone https://github.com/daveremy/function-health-mcp.git
cd function-health-mcp
npm install && npm run build

Then use the CLI directly:

./dist/cli.js login
./dist/cli.js sync
./dist/cli.js summary

MCP Tools

Tool	Description
fh_login	Check auth status (directs to CLI login if needed)
fh_status	Check auth status, data availability, and sync history
fh_results	Query lab results with filters (biomarker, category, status, visit)
fh_biomarker	Deep dive on a biomarker: value, ranges, history, recommendations
fh_summary	Health overview: totals, biological age, BMI, out-of-range markers
fh_categories	List biomarker categories with counts
fh_changes	Compare two test rounds: improved, worsened, new, significantly changed
fh_sync	Pull latest data from Function Health API
fh_check	Lightweight check for new results (no full data fetch)
fh_notifications	Read or acknowledge change notifications from syncs
fh_recommendations	Health recommendations, optionally filtered by category
fh_report	Full clinician report for a visit
fh_version	Check installed version and whether an update is available

CLI Commands

function-health login                  Authenticate with Function Health
function-health status                 Show auth status and data stats
function-health sync [--force]         Pull latest data
function-health check                  Quick check for new results
function-health results [options]      Query lab results
function-health biomarker <name>       Deep dive on a biomarker
function-health summary                Health summary
function-health categories             List categories
function-health changes [--from] [--to]  Compare test rounds
function-health export [--markdown]    Full JSON export

Periodic Monitoring with /loop

Use Claude Code's /loop command to check for new results automatically:

/loop 6h /fh-lab-results check

This checks every 6 hours. When new results are detected, it syncs and summarizes what changed.