CharmHealth vs P.R.O. Apple Health MCP
CharmHealth is an MCP server published by CharmHealth. Marketplaces we read that list it: 1 (Docker MCP Catalog). P.R.O. Apple Health MCP is an MCP server published by runwithfun. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   CharmHealth |  P.R.O. Apple Health MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:23c0372dc40d Forks (GitHub): 11 Pulls (Docker Hub): 12 552 Stars (Docker Hub): 0 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | CharmHealth | P.R.O. Apple Health MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 12 552 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | On your machine (mcp/charmhealth-mcp-server) | Remote server (mcp.proapp.uk) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 17 | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 2 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/charmhealth/charm-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-11-02 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 28 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
CharmHealth
An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.
P.R.O. Apple Health MCP
Hosted Apple Health MCP: workouts, sleep and HRV in ChatGPT, Claude, Gemini, Grok. Free, no export.
How to run each
CharmHealth As a local MCP server: Docker image
claude mcp add --env "CHARMHEALTH_API_KEY=<YOUR_CHARMHEALTH_API_KEY>" --env "CHARMHEALTH_REFRESH_TOKEN=<YOUR_CHARMHEALTH_REFRESH_TOKEN>" --transport stdio charmhealth-mcp-server -- docker run -i --rm -e CHARMHEALTH_API_KEY -e CHARMHEALTH_REFRESH_TOKEN mcp/charmhealth-mcp-serverRequires: CHARMHEALTH_API_KEY (secret), CHARMHEALTH_REFRESH_TOKEN (secret)
P.R.O. Apple Health MCP As a remote MCP server
claude mcp add --transport http pro https://mcp.proapp.ukCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only P.R.O. Apple Health MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of P.R.O. Apple Health MCP publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of P.R.O. Apple Health MCP publish no settings it asks for, so we do not compare settings.
What it can do: CharmHealth · What it can do: P.R.O. Apple Health MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.