Backwork vs Dingdawg Healthcare Agent
A side-by-side look at the Backwork and Dingdawg Healthcare Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BackworkBiology & Bioinformatics · Local subprocess (stdio)Medicare and commercial payer policies, prior auth, claim risk, and medical codes from Backwork.57GoodAuth: not declaredVerdict: choose Backwork for biology & bioinformatics work as a local process; choose Dingdawg Healthcare Agent for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose Backwork when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BACKWORK_API_KEY, BACKWORK_API_BASE, BACKWORK_MCP_TRANSPORT, BACKWORK_MCP_HOST, BACKWORK_MCP_PORT, BACKWORK_MCP_PATH, BACKWORK_MCP_ALLOWED_HOSTS, BACKWORK_MCP_AUTH_MODE. - You want tools like
write, x-backwork-required-scopes, backwork_webhook_management.
Choose Dingdawg Healthcare Agent when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DINGDAWG_API_KEY. - You want tools like
patient_intake, clinical_summary, hipaa_check.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Backwork | |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 57/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | BACKWORK_API_KEYBACKWORK_API_BASEBACKWORK_MCP_TRANSPORTBACKWORK_MCP_HOSTBACKWORK_MCP_PORTBACKWORK_MCP_PATHBACKWORK_MCP_ALLOWED_HOSTSBACKWORK_MCP_AUTH_MODE | DINGDAWG_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 13 | 4 |
| Full listing | View Backwork | View Dingdawg Healthcare Agent |
Tools & capabilities
Backwork tools 13
writex-backwork-required-scopesbackwork_webhook_managementacknowledgebulk_acknowledgebackwork_compliance_reviewbackwork_system_healthidempotency_keybackwork_claim_validationdiff_iddiff_idsnotes- +1 more on the listing page
Dingdawg Healthcare Agent tools 4
patient_intakeFree AI patient intake form with triage priority and symptom analysis. Returns structured intake locally. Deep LLM-powered ICD-10 coding and clinical reasoning with API key.clinical_summarySummarize clinical notes into structured format. Extracts chief complaint, HPI, assessment, plan. Requires DINGDAWG_API_KEY for LLM-powered summarization.hipaa_checkFree HIPAA compliance quick check for processes and systems. Returns basic compliance gaps locally. Deep LLM-powered audit with API key.appointment_schedulerAI-powered appointment scheduling with conflict detection and optimization. Requires DINGDAWG_API_KEY.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Backwork
{
"mcpServers": {
"backwork": {
"command": "npx",
"args": [
"-y",
"@backwork/mcp"
],
"env": {
"BACKWORK_API_KEY": "YOUR_BACKWORK_API_KEY_HERE",
"BACKWORK_API_BASE": "YOUR_BACKWORK_API_BASE_HERE",
"BACKWORK_MCP_TRANSPORT": "YOUR_BACKWORK_MCP_TRANSPORT_HERE",
"BACKWORK_MCP_HOST": "YOUR_BACKWORK_MCP_HOST_HERE",
"BACKWORK_MCP_PORT": "YOUR_BACKWORK_MCP_PORT_HERE",
"BACKWORK_MCP_PATH": "YOUR_BACKWORK_MCP_PATH_HERE",
"BACKWORK_MCP_ALLOWED_HOSTS": "YOUR_BACKWORK_MCP_ALLOWED_HOSTS_HERE",
"BACKWORK_MCP_AUTH_MODE": "YOUR_BACKWORK_MCP_AUTH_MODE_HERE"
}
}
}
}
Dingdawg Healthcare Agent
{
"mcpServers": {
"dingdawg-healthcare-agent": {
"command": "npx",
"args": [
"-y",
"dingdawg-healthcare-agent"
],
"env": {
"DINGDAWG_API_KEY": "YOUR_DINGDAWG_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Backwork is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Dingdawg Healthcare Agent belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Backwork for biology & bioinformatics work and Dingdawg Healthcare Agent for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Backwork is bring-your-own-key: usage is billed by the API provider you supply a key for. Dingdawg Healthcare Agent has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add backwork and dingdawg-healthcare-agent as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Backwork has a quality signal of 57/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Dingdawg Healthcare Agent has 59/100 (Good) with 2 views, 0 installs and 1 GitHub stars.