Backwork

Name: Backwork
Author: tylergibbs1

by tylergibbs1version 2.1.6i★ –iComputer or cloud

Registry nameio.github.tylergibbs1/backwork-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Clinics & health
You need to fill in: BACKWORK_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: BACKWORK_API_KEY, BACKWORK_API_BASE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://backworkhealth.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Or run it on your computer

claude mcp add backwork --env BACKWORK_API_KEY=your-value --env BACKWORK_API_BASE=your-value -- npx -y @backwork/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "backwork": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@backwork/mcp"
      ],
      "env": {
        "BACKWORK_API_KEY": "your-value",
        "BACKWORK_API_BASE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://backworkhealth.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

BACKWORK_API_KEY secret required env
Backwork API key (bwk_live_...). The hosted remote uses OAuth instead and needs no key.
BACKWORK_API_BASE env
Override the Backwork API base URL. Defaults to https://backworkhealth.com/api/v1.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account tylergibbs1, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Clinics & healthi

More stars than 0% of the other 1022 servers in this category
Published to the registry more recently than 51% of the other 1022 servers in this category
Basic checks equal to or better than 100% of the other 1022 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Backwork safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: BACKWORK_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.1.6) reached the registry 27 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated today

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago

Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Quick start

The fastest way in is the hosted server with Claude Code:

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

There are two ways to connect:

	Hosted remote	Local stdio
Endpoint	`https://backworkhealth.com/mcp` (Streamable HTTP)	`npx -y @backwork/mcp`
Auth	OAuth in the browser, no key to copy	`BACKWORK_API_KEY=bwk_live_...`
Use when	Your client supports remote MCP with OAuth	Your client only runs local commands, or you want the server on your machine

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 bwk_test_ 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 BACKWORK_API_BASE to that URL.

Setup for each client is in Connect your client. Agent-oriented install notes are in llms-install.md.

How it works

flowchart LR

client[MCP client] -->|stdio or Streamable HTTP| server[Backwork MCP server] server -->|API key or OAuth bearer| api[Backwork API /api/v1]

The server exposes eight workflow-level tools rather than one tool per endpoint. Each tool calls the Backwork API only through the operation catalog in src/api-operations.ts, returns readable text plus structuredContent, and cites the policy sources it used. Which tools and actions you see depends on how you connect (see Production availability).

Tools

Tool names use the backwork_ prefix for discoverability when this server is installed alongside other MCP servers. The default surface is intentionally workflow-level rather than a 1:1 API wrapper, so agents see fewer choices and common tasks require fewer tool calls.

Primary tool	Purpose
`backwork_coverage_lookup`	Look up procedure codes and combine code details, policy evidence, prior authorization, claim risk, jurisdiction comparison, and spending evidence. With `payer`, code details list only that payer's policies and say how many other payers' policies were left out
`backwork_policy_research`	Search policies, fetch one policy, search extracted criteria, review policy changes, map MAC jurisdictions, or compare how MACs cover the same codes
`backwork_claim_validation`	Validate claim coverage, documentation requirements, denial risk, and optional policy-specific criteria
`backwork_prior_auth_research`	Check prior authorization from Backwork's policies (Medicare, or a named payer's), or start and poll a background job that searches public payer websites
`backwork_drug_formulary_research`	Search commercial pharmacy-benefit evidence from CVS Caremark, Express Scripts, and UnitedHealthcare / Optum Rx
`backwork_compliance_review`	Review compliance stats and list unreviewed policy changes; with an API key, also acknowledge changes
`backwork_webhook_management`	List, create, update, delete, or test webhook endpoints. Backwork sends one event, `compliance.acknowledged`; policy-change webhooks are not sent. Needs a write-scoped API key
`backwork_system_health`	Check Backwork API health and dependency status. API-key connections only

Response format

Every tool accepts:

"response_format": "markdown" }

Use "markdown" for readable output or "json" to make the text content mirror the returned structuredContent.

Example prompts

Is CPT 76942 covered in Texas, and does it require prior authorization?

Compare coverage for J0585 across JM and JH.

Validate denial risk for 99213 with diagnosis E11.9 for Medicare in Texas.

Search formulary evidence for Ozempic across commercial PBMs.

Connect your client

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 Code plugin

The backwork plugin bundles the hosted MCP server with four research skills: prior authorization, coverage checks, policy changes, and denial appeal prep. Install it from this repository's plugin marketplace:

/plugin marketplace add tylergibbs1/backwork-mcp

/plugin install backwork@backwork

Then run /mcp, select plugin:backwork:backwork, and finish the OAuth sign-in. New accounts start with 100 free credits. See plugins/backwork/README.md for the skills and the /backwork:pa and /backwork:coverage commands.

The marketplace manifest is .claude-plugin/marketplace.json. npm test checks the manifests and every SKILL.md. CI also runs claude plugin validate --strict on the marketplace and the plugin.

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 claude_desktop_config.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

codex mcp add backwork --env BACKWORK_API_KEY=bwk_live_YOUR_API_KEY -- npx -y @backwork/mcp

ChatGPT

ChatGPT connects to the hosted server as a custom MCP connection in developer mode. Three tools return a small card that ChatGPT renders inline above its answer.

In ChatGPT, open Settings → Security and login and turn on Developer mode. Your plan or workspace admin may need to allow it.
Go to chatgpt.com/plugins and select the + button.
Name it Backwork, add a short description, and under Connection enter https://backworkhealth.com/mcp. Choose OAuth for authentication.
Select Create. ChatGPT opens Backwork's sign-in page; approve the read-only backwork:mcp read grant.
Check the discovered tools, then start a new chat, add Backwork from the tools menu, and ask something like *"Is CPT 76942 covered in Texas, and does it need prior auth?"*

After a server update, open the connection at chatgpt.com/plugins and select Refresh so ChatGPT picks up new tool and component metadata.

Tool	Card	What it shows
`backwork_coverage_lookup`	Coverage result	Each policy that lists the codes: payer (`CMS` for Medicare policies), title and number, effective date, a row per code with its disposition badge and source label, and an Open policy link to the policy's Backwork page (Medicare LCDs, Articles, and NCDs) or, for other policies, its source document
`backwork_prior_auth_research`	Prior-auth checklist	The determination and confidence, codes that require prior auth, documentation to gather, known gaps, and numbered citations. A started research task shows as pending until you ask again
`backwork_policy_research`	Policy research	Per action: `compare` shows the codes side by side across Medicare contractors (MACs), one column per jurisdiction, with each cell's disposition and policy, and a coverage count per column; `search` lists the matching policies with payer, number, effective date, a short summary and a link; `get` shows one policy's summary, a criteria excerpt per section, and its codes; `criteria` lists the matching criteria excerpts with their policies; `changes` lists recent changes; `jurisdictions` lists each MAC and its states

ChatGPT loads a tool's card for every call of that tool. A result with nothing to show, such as a search with no matches or an error, collapses the card to zero height and asks ChatGPT to close it, so no empty card is left in the conversation.

A code that a policy lists only because its title names the drug is labelled Inferred from policy title, in the card and in the text. Confirm it against the document before relying on it.

The cards follow ChatGPT's light or dark theme, load nothing from the network (their CSP allows no domains), and open links through the host. They are MCP Apps resources (text/html;profile=mcp-app), so other MCP Apps hosts can render them too. Clients without UI support ignore the _meta keys that link tools to cards and get the same markdown text as before; structuredContent.widget carries the card's data.

Claude.ai skills

The same four skills work in claude.ai. They need the Backwork connector to call tools.

Add the connector: Settings > Connectors > Add custom connector, name it Backwork, and enter https://backworkhealth.com/mcp. Finish the OAuth sign-in.
Build one zip per skill. The zips go to dist/claude-skills/, which git ignores:

   node scripts/build-claude-skills.mjs

Each zip holds the skill folder at its root, for example coverage-check.zip contains coverage-check/SKILL.md. The build fails if a SKILL.md breaks the claude.ai rules (name matches its folder, description 2

Only the beginning is shown; read the rest in the repo

Backwork

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Google Health MCP

README from the maker

Backwork MCP Server

Quick start

How it works

Tools

Response format

Example prompts

Connect your client

Claude Code

Claude Code plugin

Claude Desktop

Cursor

VS Code

Codex

ChatGPT

Claude.ai skills