Mymedi AI MCP Server

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

The MyMedi-AI/mymedi-ai-mcp-server MCP server gives compatible AI clients access to healthcare billing and clinical-information operations. Its tools cover ICD-10, CPT, and HCPCS lookup; code suggestions and validation; Medicare reimbursement; DMEPOS fee schedules; prior authorization; claims validation; medical named-entity extraction; and HIPAA-oriented data checks.

The catalog also includes drug lookup and interaction signals, RxNorm terminology, clinical-trial search, disease surveillance, NPI provider search, provider enrichment, Sunshine Act payment data, and state-level healthcare market analysis. CMS, OpenFDA, NIH RxNorm, ClinicalTrials.gov, CDC, and CMS Open Payments are identified as public or government data sources for relevant tools.

How it works

The server can be used as a hosted Streamable HTTP MCP endpoint at https://mymedi-ai.com/mcp-stream, or run locally through the npm package with npx. Claude, Cursor, VS Code, and other MCP clients can connect to it. The README also provides MCP prompts for denial decoding, order-readiness checks, claim scrubbing, appeal drafting, and reimbursement estimation, plus dataset resources for CMS prior-authorization and F2F/WOPD lists.

Six tools are available without an API key: prior-authorization requirement checks, denial-code explanations, basic code lookup, basic reimbursement, DMEPOS order-readiness checklists, and modifier guidance. These free tools are rate-limited to 60 requests per hour per IP. Other tools require an API key and consume credits, with prices varying by operation. Batch lookup, validation, and exposure-report tools charge per code and impose documented maximum batch sizes.

Setup and configuration

For a local MCP client, configure the package as npx -y @mymedi-ai/mcp-server. Set MCP_API_KEY to use the account-based tools; leaving it unset limits use to the free tools. MCP_API_BASE_URL changes the API base URL from its default of https://mymedi-ai.com. MCP_CONNECTOR_TOKEN is available for shared-egress rate limiting in hosted, multi-user deployments and is not needed for individual installations.

Accounts can be registered with the platform registration endpoint to receive starter credits. Additional credits can be purchased through Stripe. The hosted Claude connection does not require authentication for the free tools.

Tools and capabilities

• Look up, suggest, validate, batch-process, and cross-reference ICD-10, CPT, and HCPCS codes.
• Retrieve Medicare PFS, OPPS, and DMEPOS payment information, including state-specific fee schedules where supported.
• Check prior-authorization requirements, estimate approval outlook from historical cohorts, inspect request status, and map supplier catalogs against CMS requirement lists.
• Validate claims, extract medical entities, audit text for PHI patterns, and provide DMEPOS modifier or order-readiness guidance.
• Search drug, provider, clinical-trial, disease-surveillance, payment, and healthcare-market data.

Limitations and notes

The MyMedi-AI/mymedi-ai-mcp-server MCP server is read-only and described as PHI-free by design, but its documentation specifically warns that patient data should not be sent to the order-readiness tool. Prior-authorization features are scoped to Original Medicare fee-for-service. Modifier guidance is editorial content rather than payer policy, and prior-authorization prediction reports no probability when an adequate historical cohort is unavailable.

Paid calls require credits and may be refunded on specified no-match or no-cohort paths. Batch operations have maximum sizes, and free access is rate-limited. Results should therefore be checked against the applicable payer rules, dates of service, and operational requirements before use in billing or clinical workflows.