Health Access MCP

com.healthaccessmcpPublished by healthaccessmcp.comv0.6.2Updated Oct 29, 2026

Apple Health and Apple Watch workouts for your AI, from local files. Plans go back to the Watch.

VerifiedSTDIODesktop onlyLocation & LifestyleFiles & Storage

Overview

AI-generated overview

Local MCP server that gives an AI assistant access to Apple Health and Apple Watch workout data from local files, and can send plans back to the Watch.

What you can do
  • Read Apple Health and Apple Watch workout data from local files on the user's machine.
  • Work with that health and workout information inside an AI assistant conversation.
  • Send training plans back to the Apple Watch.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Worth considering if you want an assistant to work with your own Apple Health and Apple Watch workout records stored locally, for example to review activity or produce plans for the Watch. It is a desktop-only local server, so it is not suitable for web or headless setups.
Requirements
Runs as a local process over stdio, installed from the npm package healthaccess-mcp, so a Node.js environment on a desktop machine is needed. Local Apple Health and Apple Watch data files must be available. No authentication, environment variables or headers are declared.
Before you install
It handles personal health and workout data, which is sensitive; check where the local files are read from and what the server does with them. It can send plans back to the Watch, so changes may be written to your device. The tool list is not published, so review the package before installing.

Installation

In SourceWeft

  1. Open Health Access MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.2LatestOct 29, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.