{
"mcpServers": {
"charm-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 6 days ago. 6 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Charm Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.
[!CAUTION] This server can access, transmit, and surface protected health information (PHI). Use it only with:
- HIPAA-compliant LLM services covered by a signed BAA and configured with no training and zero data retention
- HIPAA-compliant MCP clients, or clients operated entirely within your HIPAA compliance program
If you are using this with actual patient data (non-sandbox data), do not connect non-HIPAA consumer LLM endpoints or clients. You are responsible for enforcing access controls, audit logging, encryption in transit/at rest, and data retention policies for your deployment.
The server provides 15 comprehensive tools for complete EHR functionality:
Clone and install dependencies:
git clone https://github.com/CharmHealth/charm-mcp-server.git
cd charm-mcp-server
uv sync
Configure environment:
cp .env.example .env # Create from template if available
# Edit .env with your CharmHealth API credentials
Run the server:
uv run --directory src mcp_server.py
Configure your HIPAA-compliant MCP client (e.g., an enterprise/HIPAA-compliant deployment of your chosen client) to connect to the server.
git clone https://github.com/CharmHealth/charm-mcp-server.git
cd charm-mcp-server
Using uv (recommended):
uv sync
Note: This project uses pyproject.toml for dependency management. If you prefer pip, you can install from the project definition:
pip install -e .
Create a .env file in the project root with your CharmHealth API credentials:
# CharmHealth API Configuration
CHARMHEALTH_BASE_URL=your_base_uri_here
CHARMHEALTH_API_KEY=your_api_key_here
CHARMHEALTH_REFRESH_TOKEN=your_refresh_token_here
CHARMHEALTH_CLIENT_ID=your_client_id_here
CHARMHEALTH_CLIENT_SECRET=your_client_secret_here
CHARMHEALTH_REDIRECT_URI=your_redirect_uri_here
CHARMHEALTH_TOKEN_URL=your_to
... [View full README on GitHub](https://github.com/CharmHealth/charm-mcp-server#readme)