HIPAA-aware healthcare AI. Clinical documentation, compliance checks, audit prep. Free local tier.
Breakthrough clinical workflow bottlenecks. AI healthcare assistance that respects HIPAA from day one.
HIPAA-aware AI for patient intake, clinical summaries, compliance checking, and appointment scheduling. Free tier runs locally with zero data transmission. Paid tier provides LLM-powered clinical analysis via HIPAA-compliant API. Every action is governed and receipted.
This MCP server returns structured JSON for seamless integration:
patient_intake -> hipaa_check to verify compliance -> clinical_summary for documentation -> appointment_scheduler for follow-upComposable with any MCP client: Claude Code, Cursor, VS Code, ChatGPT Desktop, Windsurf.
npx dingdawg-healthcare-agent
claude mcp add healthcare -- npx dingdawg-healthcare-agent
Add to .cursor/mcp.json:
{"mcpServers": {"healthcare": {"command": "npx", "args": ["dingdawg-healthcare-agent"], "env": {"DINGDAWG_API_KEY": "your-key"}}}}
npx dingdawg-setup
| Tool | Free Tier | Paid Tier |
|---|---|---|
patient_intake | 10/day, structured form generation | Unlimited, AI-powered intake with pre-population |
clinical_summary | 5/day, basic summary from notes | Unlimited, LLM-powered with ICD-10/CPT coding |
hipaa_check | 10/day, checklist-based compliance | Unlimited, deep HIPAA gap analysis with remediation |
appointment_scheduler | 10/day, basic scheduling | Unlimited, AI-optimized scheduling with conflict detection |
Get API key: https://dingdawg.com/developers
Every call is receipted and auditable. HIPAA checks reference specific administrative, physical, and technical safeguards (45 CFR Part 164). Clinical summaries include disclaimer that content is for informational purposes and does not constitute medical advice. All PHI processing on paid tier uses HIPAA-compliant infrastructure.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y dingdawg-healthcare-agentMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-dingdawg-dev-dingdawg-healthcare-agent": {
"command": "npx",
"args": [
"-y",
"dingdawg-healthcare-agent"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencedingdawg-healthcare-agentnpmio.github.DingDawg-dev/dingdawg-healthcare-agent works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.