Claims desk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RCI_API_KEY | No | Optional API key for RCI enrichment. | |
| RCI_API_URL | No | Optional API URL for RCI enrichment. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_claim_requirementsA | Resolve claim documentation requirements for a payer + CPT. Fetches live cataloged policy sources (CMS or payer) and optionally enriches from an RCI knowledge API when RCI_API_KEY is set. Returns structured requirements plus document URIs — never PDF/HTML bytes. |
| read_document_bytesA | App-only: stream a fetched policy document in base64 chunks (offset/length/hasMore). Used by the claims App to render source docs. |
| preview_pdf_pagesA | App-only: rasterize the first pages of a cited policy PDF for the reviewer. |
| list_policy_libraryA | List live CMS policy documents wired into this claims desk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Claims desk | Interactive claims reviewer UI (MCP App) |
| LCD L33618 — Major Joint Replacement (Hip and Knee) | https://www.cms.gov/medicare-coverage-database/view/lcd.aspx?lcdId=33618&ver=23 |
| Medicare Claims Processing Manual — Chapter 1, §70 timely filing (PDF) | https://www.cms.gov/Regulations-and-Guidance/Guidance/Manuals/Downloads/clm104c01.pdf |
| Medicare Claims Processing Manual — Chapter 12 (PDF) | https://www.cms.gov/Regulations-and-Guidance/Guidance/Manuals/Downloads/clm104c12.pdf |
| LCD L33718 — Positive Airway Pressure (PAP) Devices | https://www.cms.gov/medicare-coverage-database/view/lcd.aspx?lcdId=33718 |
| CMS Required Prior Authorization List (DMEPOS) (PDF) | https://www.cms.gov/research-statistics-data-and-systems/monitoring-programs/medicare-ffs-compliance-programs/dmepos/downloads/dmepos_pa_required-prior-authorization-list.pdf |
| CMS DMEPOS prior authorization process | https://www.cms.gov/data-research/monitoring-programs/medicare-fee-service-compliance-programs/prior-authorization-and-pre-claim-review-initiatives/prior-authorization-process-certain-durable-medical-equipment-prosthetics-orthotics-and-supplies |
| CMS — CMNs and DIFs discontinued (Jan. 1, 2023) | https://www.cms.gov/newsroom/news-alert/cms-discontinuing-use-certificates-medical-necessity-and-durable-medical-equipment-information-forms |
| UHC Commercial / Individual Exchange — Radiology PA CPT list (PDF) | https://www.uhcprovider.com/content/dam/provider/docs/public/prior-auth/radiology/COMM-Radiology-Prior-Notification-Authorization-CPT-Code-List.pdf |
| UHC Commercial / Individual Exchange — Outpatient radiology PA FAQ (PDF) | https://www.uhcprovider.com/content/dam/provider/docs/public/prior-auth/radiology/COMM-Exchange-Radiology-Prior-Auth-FAQ.pdf |
TDQS
Scored across 4 tools
Each tool has a distinct primary purpose, and the names/descriptions are mostly clear. However, read_document_bytes and preview_pdf_pages both operate on cited policy documents for app rendering, and their raw-bytes vs. rasterized-preview distinction could cause minor selection confusion.
All tools follow a consistent verb_noun pattern: review_claim_requirements, read_document_bytes, preview_pdf_pages, and list_policy_library. No casing or style inconsistencies exist, and each name clearly suggests its action.
Four tools is well-scoped for a focused claims document and requirements server. Each tool covers a distinct step in the workflow: resolving requirements, reading document bytes, previewing PDFs, and listing the policy library.
The core workflow is covered end-to-end: review claim requirements, access document content, preview PDFs, and browse the policy library. Minor gaps remain, such as no general search/filter over the library and no non-app-facing document retrieval path.