A side-by-side look at the Medicare Fee Schedule Rates and Backwork MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Medicare Fee Schedule Rates for biology & bioinformatics work; choose Backwork for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
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.write, x-backwork-required-scopes, backwork_webhook_management.Rows where the two servers differ are marked.
| Spec | M Medicare Fee Schedule Rates | |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 39/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | BACKWORK_API_KEYBACKWORK_API_BASEBACKWORK_MCP_TRANSPORTBACKWORK_MCP_HOSTBACKWORK_MCP_PORTBACKWORK_MCP_PATHBACKWORK_MCP_ALLOWED_HOSTSBACKWORK_MCP_AUTH_MODE |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 13 |
| Full listing | View Medicare Fee Schedule Rates | View Backwork |
No tool names declared yet. Check the project README from the listing page.
writex-backwork-required-scopesbackwork_webhook_managementacknowledgebulk_acknowledgebackwork_compliance_reviewbackwork_system_healthidempotency_keybackwork_claim_validationdiff_iddiff_idsnotesPaste 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.
No confirmed install command for Medicare Fee Schedule Rates yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"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"
}
}
}
}