CharmHealth vs MyMedi-AI
CharmHealth is an MCP server published by CharmHealth. Marketplaces we read that list it: 1 (Docker MCP Catalog). MyMedi-AI is an MCP server published by MyMedi-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  MyMedi-AI |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:23c0372dc40d Forks (GitHub): 11 Pulls (Docker Hub): 12 216 Stars (Docker Hub): 0 Stars (GitHub): 12 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.9 Downloads/month (npm): 207 Downloads/week (npm): 70 Forks (GitHub): 0 Stars (GitHub): 3 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 | MyMedi-AI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | 12 216 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-27 |
| Where it runs (differs) | On your machine (mcp/charmhealth-mcp-server) | Remote server (mymedi-ai.com/mcp-stream) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 17 | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 2 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/charmhealth/charm-mcp-server | github.com/mymedi-ai/mymedi-ai-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago, requires a key |
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.
MyMedi-AI
DME billing and medical coding: code lookup, DMEPOS fee schedules, Medicare prior-auth checks
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)
MyMedi-AI As a remote MCP server
claude mcp add --transport http mymedi-ai https://mymedi-ai.com/mcp-streamRequires: MCP_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only MyMedi-AI has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of MyMedi-AI publish no list of tools, so we do not compare tools.
Settings each asks for
Only CharmHealth asks for
CHARMHEALTH_API_KEY (secret)CHARMHEALTH_BASE_URLCHARMHEALTH_CLIENT_IDCHARMHEALTH_CLIENT_SECRETCHARMHEALTH_REDIRECT_URICHARMHEALTH_REFRESH_TOKEN (secret)CHARMHEALTH_TOKEN_URL
Only MyMedi-AI asks for
MCP_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: CharmHealth · What it can do: MyMedi-AI · 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.