Skip to main content
The RCI MCP server is available as both a Streamable HTTP server and a stdio server. Choose the method that fits your environment. Endpoint:

Claude Desktop

Add to your Claude Desktop configuration (~/.config/claude/claude_desktop_config.json):

Claude Code

Cursor

Add to your Cursor MCP configuration (~/.cursor/mcp.json):

Stdio Server (Local)

For development or air-gapped environments, you can run the MCP server locally:
Then add to your MCP client configuration:

Verify the connection

Once connected, verify the MCP server is working by asking your agent:
Resolve the billing context for CCN 170001 with CPT 99213 for a Medicare outpatient visit.
Your agent should invoke the resolve_knowledge tool and return the full L1-L6 knowledge stack including a payment estimate.

Example use

Resolve billing context

Prompt: “What billing form should I use for an outpatient visit at facility 170001?” The MCP server invokes resolve_knowledge and returns the facility type (short-term hospital), billing form (CMS-1500 / 837P), and applicable TOB codes.

Calculate expected payment

Prompt: “How much should Medicare pay for CPT 99214 at this facility?” The MCP server invokes calculate_payment and returns the GPCI-adjusted RVU breakdown and estimated payment.

Research a billing code

Prompt: “What is the correct CPT code for a total knee replacement, and what documentation is required?” The MCP server invokes research_code, which dispatches to the AI code research agent. Results include the CPT code (27447), documentation requirements, and medical necessity criteria.

Resolve a denial

Prompt: “We received CARC 197 with RARC N479 on a claim. What should we do?” The MCP server invokes resolve_denial with the CARC/RARC codes, retrieves payer-specific appeal deadlines, and generates a resolution strategy.