Backwork

Name: Backwork
Author: tylergibbs1

作者：tylergibbs1版本 2.1.6i★ –i电脑或云端

注册名称io.github.tylergibbs1/backwork-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 诊所与健康
你需要填写：BACKWORK_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： BACKWORK_API_KEY, BACKWORK_API_BASE

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://backworkhealth.com/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

或者在你的电脑上运行

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://backworkhealth.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

BACKWORK_API_KEY 机密必填 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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 tylergibbs1 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“诊所与健康”中的其他服务器比较i

星标数多于此分类中其他 1022 个服务器的 0%
发布到注册中心的时间比此分类中其他 1022 个服务器的 51% 更新
基础检查结果等于或优于此分类中其他 1022 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Backwork 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：BACKWORK_API_KEY

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.1.6）于27天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Mirobody, FHIR MCP Server, Google Health MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

作者：thetahealth

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

在你的电脑上运行★ 1,408Apache-2.0今天更新

安装

FHIR MCP Server

作者：wso2

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

在你的电脑上运行★ 137Apache-2.09天前更新

安装

Google Health MCP

作者：davidmosiah

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

在你的电脑上运行★ 79MIT4个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读

Backwork

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“诊所与健康”中的其他服务器比较i

常见问题

替代选择

Mirobody

FHIR MCP Server

Google Health MCP

作者的 README

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