Apple Health MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow Apple Health schema and privacy-boundary changes as the integration evolves

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Private local analysis of Apple Health CSV exports.

What we know

Local stdio MCP that loads Simple Health Export CSV files into in-memory DuckDB and exposes schema discovery, SELECT-family analysis and reports.

Maintenance / activity evidence

Observed Oct 2, 2026 (UTC)chore: remove dead code and unused config ( 44)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read/SELECT-oriented access to configured export.
Authentication not yet verified.
Sensitive access: Highly sensitive health history

Network exposure is low, but all health history in the configured directory can be exposed to the trusted model/client.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

568 repository stars

Stars observed Sep 25, 2026.

Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.

All limitations / Review context

Which Health data types and local access controls are currently documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Network exposure is low, but all health history in the configured directory can be exposed to the trusted model/client.
Read/SELECT-oriented access to configured export.
Server makes no network requests; results may still go to the client's model provider.
Sensitive access: Highly sensitive health history
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Only Simple Health Export CSV is supported; native export.xml is not.
Whole configured history is accessible.
Reports are not medical advice.

Original activity observations

2026-10-02T03:55:22Z: chore: remove dead code and unused config ( 44)

Technical identity

github.com/neiltron/apple-health-mcp

Exact implementation source: https://github.com/neiltron/apple-health-mcp ↗
Reviewed resource type: MCP Server
Repository identity: neiltron/apple-health-mcp
Package identity: npm:@neiltron/apple-health-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

GitHub repository ↗
neiltron/apple-health-mcp
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

claude-desktop

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Apple Health MCP reads user-exported CSV data; it does NOT connect directly to HealthKit on a desktop.
Claude Desktop MCP JSON entry: `command: npx`, `args: ["-y","@neiltron/apple-health-mcp"]`, env `HEALTH_DATA_DIR=/absolute/path/to/export`; must first export Apple Health data to CSV.
Configure / authenticate
MCP100 setup guide
Apple Health MCP reads iPhone CSV exports via Simple Health Export, requiring local file placement and MCP registration; health data is sensitive and can be forwarded to client model provider.
Advanced configuration · claude desktop json · MCP100 composed guide
claude desktop json · MCP100 composed guide
{ "mcpServers": { "apple-health": { "args": [ "-y", "@neiltron/apple-health-mcp" ], "command": "npx", "env": { "HEALTH_DATA_DIR": "/absolute/path/to/export" } } } }
Check connection
Suggested check
Confirm permitted local export directory and MCP tool listing; do not upload real medical data for smoke tests.
Remove / uninstall / revoke
MCP100 setup guide
Only if registered as apple-health in Claude Code; Desktop remove its mcpServers entry. The source Apple Health CSV exports are not deleted.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
claude mcp remove apple-health

Official Documentation & Sources

What it does

Local stdio MCP that loads Simple Health Export CSV files into in-memory DuckDB and exposes schema discovery, SELECT-family analysis and reports.

Capability: Data & Databases
Resource type: MCP Server
Industry: Healthcare & Life Sciences
Best fit: Private local analysis of Apple Health CSV exports.

Representative uses

Discover health tables/schema
Run analytical SQL
Generate weekly/monthly/custom reports
Analyze full exported history

Limitations

Only Simple Health Export CSV is supported; native export.xml is not.
Whole configured history is accessible.
Reports are not medical advice.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Read/SELECT-oriented access to configured export.
Data handling: Server makes no network requests; results may still go to the client's model provider.
Cost: free
Risk and cautions: Network exposure is low, but all health history in the configured directory can be exposed to the trusted model/client.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Highly sensitive health history
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Discover health tables/schema; Run analytical SQL; Generate weekly/monthly/custom reports; Analyze full exported history.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @neiltron/apple-health-mcp. Recorded transport: stdio. Recorded environment-variable notes: HEALTH_DATA_DIR; MAX_MEMORY_MB optional; CACHE_SIZE optional. No configuration values are supplied here. Prerequisites: Node.js 22+; Simple Health Export CSV. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No remote auth; trusted local client boundary.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read/SELECT-oriented access to configured export.

What data-handling boundary should I consider?

Server makes no network requests; results may still go to the client's model provider. Recorded sensitive-access context: Highly sensitive health history.

What limitations and risks should I check before use?

Network exposure is low, but all health history in the configured directory can be exposed to the trusted model/client. Only Simple Health Export CSV is supported; native export.xml is not. Whole configured history is accessible. Reports are not medical advice. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

Neil Pullman / neiltron is listed as First-party MCP in MCP100’s current evidence.