Mmcp.market

Backwork MCP server

online · 100% uptime
by tylergibbs1·io.github.tylergibbs1/backwork-mcp·v2.1.6·1 stars

Medicare and commercial payer policies, prior auth, claim risk, and medical codes from Backwork.

A98/100grade A
What users say
No reviews yet
Be the first
Safety scan
A98/100

not scanned yet

Adoption
Growing

1 stars7 downloads/wk

Reviews

Write one

Nobody has reviewed Backwork yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Backwork tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New registry listings are scanned within a day of import.

Install Backwork in Claude Code, Cursor or VS Code

claude mcp add --transport http backwork-mcp https://backworkhealth.com/mcp
Add to Cursor

What the publisher says

From the Backwork repository's README, as published. We do not edit it. Read it on GitHub

Backwork MCP Server

Official Model Context Protocol (MCP) server for the Backwork API. It gives AI assistants controlled access to Medicare and payer medical policies, medical code intelligence, prior authorization checks, claim validation, compliance review, drug formulary evidence, and webhook operations.

There are two ways to connect:

The hosted endpoint only accepts OAuth. Do not send a Backwork API key as a bearer token to https://backworkhealth.com/mcp. The OAuth grant is read-only (backwork:mcp read), so the hosted server offers only read actions: no webhook management and no compliance acknowledgements. Use local stdio with a write-scoped live key for those.

Calls draw on your organization's request credits, like any other /api/v1 call. A bwktest key works only on the sandbox (https://backworkhealth.com/api/sandbox/v1), which covers policy search, code lookup, prior-auth check and coverage evaluation; to use it, set BACKWORKAPIBASE to that URL.

Claude Code

claude mcp add backwork --transport http https://backworkhealth.com/mcp

Add --scope user to make it available in every project. Then run claude, open /mcp, select backwork, and finish the browser login and Backwork consent screen. Check it with claude mcp get backwork.

If OAuth discovery needs to be pinned explicitly, add the same server as JSON:

claude mcp add-json backwork '{
  "type": "http",
  "url": "https://backworkhealth.com/mcp",
  "oauth": {
    "scopes": "backwork:mcp read"
  }
}'

Local stdio:

claude mcp add backwork -e BACKWORK_API_KEY=bwk_live_YOUR_API_KEY -- npx -y @backwork/mcp

Claude Desktop

Hosted remote: open Settings > Connectors > Add custom connector, name it Backwork, and enter https://backworkhealth.com/mcp. Claude Desktop runs the OAuth login when you connect.

Local stdio: add this to claudedesktopconfig.json (Settings > Developer > Edit Config) and restart Claude Desktop:

{
  "mcpServers": {
    "backwork": {
      "command": "npx",
      "args": ["-y", "@backwork/mcp"],
      "env": {
        "BACKWORK_API_KEY": "bwk_live_YOUR_API_KEY"
      }
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor opens the OAuth login the first time it connects:

{
  "mcpServers": {
    "backwork": {
      "url": "https://backworkhealth.com/mcp"
    }
  }
}

Local stdio:

{
  "mcpServers": {
    "backwork": {
      "command": "npx",
      "args": ["-y", "@backwork/mcp"],
      "env": {
        "BACKWORK_API_KEY": "bwk_live_YOUR_API_KEY"
      }
    }
  }
}

VS Code

code --add-mcp '{"name":"backwork","type":"http","url":"https://backworkhealth.com/mcp"}'

Or add it to .vscode/mcp.json in a workspace. VS Code asks you to sign in when the server starts:

{
  "servers": {
    "backwork": {
      "type": "http",
      "url": "https://backworkhealth.com/mcp"
    }
  }
}

Local stdio, with the key prompted for once and stored by VS Code:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "backwork-api-key",
      "description": "Backwork API key",
      "password": true
    }
  ],
  "servers": {
    "backwork": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@backwork/mcp"],
      "env": {
        "BACKWORK_API_KEY": "${input:backwork-api-key}"
      }
    }
  }
}

Codex

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Backwork: common questions

Is Backwork MCP server safe?
Yes, by our scan: it is graded A (98/100). Read the Backwork safety report
How do I install Backwork?
It runs remotely at backworkhealth.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Backwork need an API key?
Yes. The registry entry asks for BACKWORK_API_KEY.
Is Backwork maintained?
The last commit was 12 days ago (2026-10-01). The latest release is v2.1.6.
Is Backwork up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Backwork?
Servers from other publishers that do the same job: MyMedi-AI MCP server, ssh-mcp server and Rede MCP server. Compare all Backwork alternatives.

Alternatives to Backwork

Same job from other publishers: the closest match first, then the best rated.

All Backwork alternatives →
  • MyMedi-AI
    DME billing and medical coding: code lookup, DMEPOS fee schedules, Medicare prior-auth checks
    A
  • ssh-mcp
    MCP gateway for controlled SSH access with per-client auth, command policies, and audit logging.
    B
  • Rede
    MCP server for Rede — Itaú-owned BR acquirer: authorize/capture/refund, zero-auth, card tokens
    B
  • Healthclaw Guardrails
    Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation
    A
  • spintax.net MCP server
    Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth.
    A

More from tylergibbs1 →