Mymedi AI MCP Server

What MyMedi-AI/mymedi-ai-mcp-server does

MyMedi-AI/mymedi-ai-mcp-server exposes healthcare billing and medical-data operations through MCP. Its coding coverage includes ICD-10-CM, CPT, and HCPCS records, with DMEPOS fee schedules, Medicare reimbursement values, code relationships, suggestions, and validation. Billing workflows cover prior-authorization requirements, face-to-face and written-order requirements, modifier guidance, denial-code explanations, claims checks, and supplier exposure reports.

The server also provides drug, provider, clinical-trial, disease-surveillance, and market data tools. Sources include CMS, OpenFDA, NIH RxNorm, ClinicalTrials.gov, NPPES, CMS Open Payments, CDC surveillance data, and the CodeReference database. Several tools add clearly labeled analysis or estimates to source data.

How it works

Run the package with Node.js 20 or later using npx -y @mymedi-ai/mcp-server. MCP clients can connect through stdio. The hosted streamable HTTP endpoint is https://mymedi-ai.com/mcp-stream; Claude authenticates through its custom connector flow rather than requiring a copied API key.

Without credentials, six tools are available: prior-authorization list checks, denial-code explanations, basic code metadata, basic reimbursement, order-readiness checklists, and modifier guidance. These free tools are rate-limited to 60 requests per hour per IP. Other operations use an API key or connector sign-in and consume credits. Batch code operations charge per code and impose limits of 25 codes, while exposure reports allow up to 100 HCPCS codes.

Setup and configuration

Install the package in an MCP client configuration and optionally set MCP_API_KEY. A key can be obtained by sending a registration request to the MyMedi-AI marketplace endpoint. MYMEDI_API_KEY is also accepted, but MCP_API_KEY takes precedence when both are set. New keys include starter credits, and the buy_credits tool returns a Stripe checkout link for adding more.

Claude Desktop, Cursor, VS Code, and Claude Code configurations use the package's npx command. Claude web users can add the hosted endpoint as a custom connector and complete the MyMedi-AI sign-in flow. A free demonstration endpoint provides basic code metadata and is limited to 60 requests per hour per IP.

Tools and capabilities

• Look up, suggest, validate, batch-process, and cross-reference ICD-10, CPT, and HCPCS codes.
• Retrieve national professional-service reimbursement, DMEPOS rental and purchase ranges, or state-specific fee schedule values.
• Check prior-authorization, F2F/WOPD, SWO, modifier, denial, and documentation requirements.
• Predict prior-authorization outcomes only when a qualifying historical cohort exists; otherwise return verifiable CMS facts without fabricating a probability.
• Validate claims before submission and generate supplier-level exposure reports.
• Extract codes and dates from de-identified text, or scan text for common SSN, MRN, and birth-date patterns.
• Query drug, provider, payment, clinical-trial, surveillance, and healthcare-market datasets.

Limitations and notes

The tools are designed for codes, modifiers, dates of service, facts, and de-identified text rather than patient identifiers. The compliance tool is a pattern-based scan, not a complete HIPAA audit, and the drug-interaction results represent statistical FAERS co-reporting signals rather than proof of interactions. Prior-authorization tools are scoped to Original Medicare fee-for-service; pa_status tracks requests entered in the MyMedi-AI workspace and does not query payers. Editorial modifier guidance is not payer policy, and claims validation does not determine medical necessity or prior authorization.

Paid calls consume credits. compliance_audit costs 250 credits and is intended for samples rather than every record. Calls for empty code-suggestion results, missing prior-authorization cohorts, and certain all-miss batch lookups are refunded according to the tool behavior.