About dingdawg-healthcare-agent
dingdawg-healthcare-agent is an MCP server for healthcare workflows, aimed at clinical and administrative tasks. It provides local intake and summaries, HIPAA checks, scheduling, and auditable governance receipts; paid processing adds LLM-powered analysis.
Key features
- 01Patient intake and form generation
- 02Clinical summaries with ICD-10 and CPT references
- 03HIPAA checks with safeguard gap identification
- 04Appointment scheduling
- 05Auditable governance receipts
Use cases
- 01Structure patient intake information
- 02Summarize clinical notes for documentation
- 03Identify HIPAA safeguard gaps
- 04Schedule follow-up appointments
MCP support
Exposes healthcare workflow tools to MCP clients, including patient_intake, clinical_summary, hipaa_check, and appointment_scheduler. Calls return structured JSON and a governance receipt.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y dingdawg-healthcare-agentDINGDAWG_API_KEYSecretAPI key for paid tier access — get free at dingdawg.comLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEdingdawg-healthcare-agent
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.
For AI Assistants
This MCP server returns structured JSON for seamless integration:
- ICD-10 and CPT code references in clinical summaries
- HIPAA compliance scores with specific safeguard gap identification
- Governance receipt on every call (audit-ready)
- Chain-ready:
patient_intake->hipaa_checkto verify compliance ->clinical_summaryfor documentation ->appointment_schedulerfor follow-up
Composable with any MCP client: Claude Code, Cursor, VS Code, ChatGPT Desktop, Windsurf.
Install
npx dingdawg-healthcare-agent
Claude Code
claude mcp add healthcare -- npx dingdawg-healthcare-agent
Cursor
Add to .cursor/mcp.json:
{"mcpServers": {"healthcare": {"command": "npx", "args": ["dingdawg-healthcare-agent"], "env": {"DINGDAWG_API_KEY": "your-key"}}}}
Full Stack (all 13 agents)
npx dingdawg-setup
Tools
| 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 |
Pricing
- Free: 10 intakes/day, local processing (no data leaves your machine)
- Pro: $49/mo, 100 calls/day, AI-powered clinical analysis
- Pay-as-you-go: $0.25/call, no commitment
Get API key: https://dingdawg.com/developers
Governed
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.
Support
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.