google-health-mcp

★ 71

icuvisor

★ 41

google-health-mcp vs icuvisor

Q: Which is better, google-health-mcp or icuvisor?

By GitHub stars, google-health-mcp has more community adoption, but the best choice depends on your specific use case.

google-health-mcp: Google Health MCP is a local-first server designed to provide AI agents with user-authorized data from Google Health API v4, including Fitbit and Pixel Watch. It emphasizes privacy by ensuring that OAuth tokens never leave the user's machine, enabling secure and direct access to personal health information.; icuvisor: icuvisor is an open-source, local-first server enabling AI assistants to securely access and interact with training data from intervals.icu. It simplifies fitness data analysis and planning by providing structured responses and ensuring local API key management.

TL;DR

google-health-mcpAPI Integration · ★ 71

Check Google Health API connection status and data inventory for AI agents.

Read google-health-mcp full review →

icuvisorAPI Integration · ★ 41

Allowing AI assistants (Claude, ChatGPT, Cursor) to talk to your intervals.icu training data.

Read icuvisor full review →

Side-by-Side Comparison

Field

google-health-mcp

icuvisor

Features

google-health-mcp

01Local-first operation ensures tokens and data remain on your machine.

02Connects AI agents to Google Health API v4 data (Fitbit, Pixel Watch, partners).

03Supports OAuth for secure user authorization.

04Provides diagnostic tools for setup verification and API reachability (`doctor`).

05Offers structured and redacted data access for privacy and debugging.

icuvisor

01Local-first by default: API keys are read from the OS keychain, not passed as tool arguments.

02One binary to install: The server ships as a single Go binary, simplifying setup without language runtime dependencies.

03Structured, terse responses: Read tools return compact JSON-shaped results, optimized for AI consumption.

04Calendar writes are safety-shaped: Assistants can add workouts, notes, and unavailable dates safely, with conflict reporting.

05Delete safety is outside the model's reach: Destructive tools are only registered when explicitly allowed by a process-level flag.

Use Cases

google-health-mcp

↳Check Google Health API connection status and data inventory for AI agents.

↳Retrieve daily and weekly health summaries from authorized Google Health data.

↳Audit local privacy settings and data flow for Google Health interactions.

icuvisor

↳Allowing AI assistants (Claude, ChatGPT, Cursor) to talk to your intervals.icu training data.

↳Analyzing activity summaries and details with explicit gear names and unit-labelled fields.

↳Projecting fitness (CTL/ATL/TSB) based on weekly training-plan targets or planned daily loads.

↳Adding workouts, notes, races, or marking unavailable date ranges (e.g., Sick, Injured, Holiday) to your calendar.

↳Receiving profile readiness warnings for missing sport thresholds or zones from the AI assistant.

FAQ

What is the difference between google-health-mcp and icuvisor?

Both google-health-mcp and icuvisor are in the API Integration category. google-health-mcp has 71 stars, while icuvisor has 41 stars.

Which is better, google-health-mcp or icuvisor?

The best choice depends on your use case. Choose google-health-mcp if Check Google Health API connection status and data inventory for AI agents., and icuvisor if Allowing AI assistants (Claude, ChatGPT, Cursor) to talk to your intervals.icu training data..

Is google-health-mcp free or open source?

Yes, google-health-mcp is open source on GitHub (MIT).

Is icuvisor free or open source?

Yes, icuvisor is open source on GitHub (MIT).

Cloud Infrastructure

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit

→

Alternatives to google-health-mcp →Alternatives to icuvisor →google-health-mcp details →icuvisor details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related