SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI codingmymedi-ai-mcp-server

mymedi-ai-mcp-server

Healthcare billing: ICD-10, CPT and HCPCS code lookup, prior authorization prediction, claims validation, denial-risk scoring and HIPAA compliance auditing.

Open website

About this tool

Purpose

MyMedi-AI/mymedi-ai-mcp-server is an MCP server for medical billing and medical coding, used to connect capabilities such as coding queries, prior authorization determinations, and claim validation to Claude, Cursor, VS Code, or other MCP clients. The materials describe it as intended for DME (durable medical equipment) billing and medical coding scenarios.

Main capabilities

  • Coding queries: covers a database of 90K+ ICD-10-CM, CPT, and HCPCS codes (the introduction also states 81,769 codes and includes RVU + OPPS pricing).
  • Fee schedules and lists: DMEPOS fee schedule, Medicare prior authorization list, face-to-face (F2F)/WOPD list checks.
  • Claims-related: denial code guidance, pre-submission claim checks, denial risk scoring, prior authorization prediction.
  • Other tools: NPI and drug information supplementation, HIPAA compliance audit (the materials list compliance_audit as a paid tool costing 250 credits per use).
  • Includes 5 DME billing prompts and 3 dataset resources.

Tools and authorization

  • 6 tools can be used without an API key (the free endpoint is limited to 60 requests per IP per hour).
  • The remaining tools require an API key or connector login: 24 are pay-per-call, while account_status and buy_credits are free but require a key to identify the account.
  • Tools are designed to contain no PHI: they only receive codes, modifiers, dates of service, and de-identified text, and do not receive patient identifying information. Except for buy_credits, which opens a Stripe checkout session, the tools do not change any state, and no charge is incurred until checkout is completed in the browser.

How to use

  • Claude (web or desktop): Settings → Connectors → Add custom connector, enter https://mymedi-ai.com/mcp-stream。该端点受 OAuth-protected; Claude registers itself and requires logging in to MyMedi-AI once. A free starter credit is given for the first connector login, with no need to copy an API key.
  • Other clients: install the server; when MCP_API_KEY is not set, it starts with the 6 free tools; when paid tools are needed, register first to obtain an API key.
  • API key registration is a POST request (not a web page): POST https://mymedi-ai.com/bot-marketplace/register，返回的 Set apiKey as MCP_API_KEY (MYMEDI_API_KEY is also accepted; when both are set, MCP_API_KEY takes precedence).
  • Free demo endpoint:https://mymedi-ai.com/bot-marketplace/demo，返回基本编码元数据，限每 60 per IP per hour.
  • Client configuration examples: claude_desktop_config.json, .cursor/mcp.json, .vscode/mcp.json.
  • HTTP mode (--http): the same server can be used via Streamable HTTP by clients that connect by URL. By default it listens on 127.0.0.1; a non-loopback MCP_HOST (such as 0.0.0.0) must set MCP_HTTP_TOKEN (at least 32 characters, such as openssl rand -hex 32), and clients send Authorization: Bearer <token>, otherwise a 401 is returned. The request Host must match localhost, 127.0.0.1, [::1], the MCP_HOST address, or a host in MCP_ALLOWED_HOSTS, otherwise a 403 is returned. Web requests with an Origin must be in MCP_ALLOWED_ORIGINS, otherwise 403. Request bodies over 1 MiB return 413; sessions are limited by MCP_MAX_SESSIONS and are closed after being idle for longer than MCP_SESSION_IDLE_MS; unknown session ids return 404. When traffic leaves the local machine, a TLS reverse proxy should be placed in front.
  • The SDK can be installed for non-MCP programmatic use.

Billing

  • 1 credit = 0.001 USD.
  • A single call to a paid tool ranges from 1 credit (code_lookup) to 250 credits (compliance_audit); code_lookup_batch, code_validate_batch, and pa_exposure_report are priced by the number of codes. Failed calls refund credits.
  • Each successful paid call result includes a _billing field: { "creditsSpent": …, "creditsRemaining": …, "priceUSD": … }. Under pure REST (non-MCP), the same data is sent in the X-Credits-Spent / X-Credits-Remaining response headers.
  • The per-tool price table is published as JSON at https://mymedi-ai.com/bot-marketplace/credits/pricing。
  • account_status shows the balance and recent transactions; buy_credits returns a Stripe checkout link, $1 buys 1000 credits, packages range from $1 to $500, and credits arrive after checkout is complete. The materials also mention the x402 USDC payment method.

Upgrade notes (1.7.6)

  • A breaking change for remote --http deployments: 1.7.5 and earlier HTTP mode listened on all interfaces, did not validate tokens, and sent Access-Control-Allow-Origin: *; starting with 1.7.6 it listens on 127.0.0.1, and cross-machine service requires setting MCP_HOST, MCP_HTTP_TOKEN, and MCP_ALLOWED_HOSTS (when MCP_HOST=0.0.0.0 it must include the LAN and Docker host IPs), and browser clients also require MCP_ALLOWED_ORIGINS. Unknown session ids changed from 400 to 404. stdio installations (Claude Desktop, Cursor, VS Code, Claude Code) are unaffected.
  • 1.7.6 requires Node.js 20 or higher.
  • Other changes: the server sends instructions during initialize; scrub-claim accepts an optional dateOfService and no longer asks about medical necessity; accepts MYMEDI_API_KEY as an alias for MCP_API_KEY; paid calls without a key explain how to register.

Data sources

  • ICD-10-CM and HCPCS Level II: CMS and CDC code sets.
  • CPT®: from CMS Physician Fee Schedule (RVU) files; CPT® is a registered trademark of the American Medical Association (AMA), and CPT codes and descriptions are AMA copyright.
  • Fee schedules and lists: CMS DMEPOS fee schedule, Medicare Physician Fee Schedule (RVU), Required Prior Authorization List, F2F/WOPD lists.
  • Providers: CMS NPI registry (NPPES) and CMS Open Payments.
  • Drugs: openFDA (labels, adverse events) and NIH RxNorm.
  • Clinical and public health: ClinicalTrials.gov and CDC NNDSS.

Applicable scenarios and limitations

Suitable for scenarios that integrate medical coding queries, prior authorization determinations, claim validation, and similar capabilities into MCP clients or custom workflows. Limitations and notes: requires Node.js 20+; free endpoints are rate-limited to 60 requests per IP per hour; paid calls consume credits; queries must use bare codes (such as E1390, 99213, M79.3), and denial codes accept CO-50, co50, or 50; reference data is updated according to the CMS release cycle, and prior authorization and F2F/WOPD answers include the version of the list on which their checks were based. The materials do not provide independent evaluations of effectiveness, accuracy, or clinical applicability. Support email support@mymedi-ai.com, and issues can be submitted to https://github.com/MyMedi-AI/mymedi-ai-mcp-server/issues。常见问题包括 402 payment_required, invalid_api_key, free tools 429, connector unable to connect (an unauthenticated request returning {"error":"unauthorized","error_description":"OAuth required"} is normal, and you can use curl -s https://mymedi-ai.com/.well-known/oauth-protected-resource to confirm the service is online), etc.

Related tools

Browse category