mymedi-ai-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_API_KEY | Yes | API key from registration | |
| MCP_API_BASE_URL | No | API base URL | https://mymedi-ai.com |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| code_lookupA | Look up medical codes (ICD-10, CPT, HCPCS) by code string. Returns description, category, active status, and related codes. |
| code_suggestA | Get AI-powered medical code suggestions from a clinical description. Returns ranked code suggestions with relevance scores. |
| code_validateC | Validate a medical code for correctness, active status, and context. Returns warnings and errors. |
| pa_predictA | Predict prior authorization approval probability for a procedure. Returns approval likelihood (0-1), confidence level, estimated processing days, and contributing factors. |
| pa_statusA | Check the status of a prior authorization request. Returns current status, dates, and expiration info. |
| ner_extractA | Extract medical named entities from clinical text. Identifies ICD-10 codes, CPT codes, dates, medications, and 12 entity types with confidence scores. |
| claims_validateA | Pre-submission claims validation. Checks for errors, missing fields, code mismatches, and provides fix suggestions before you submit to the payer. |
| compliance_auditA | HIPAA compliance audit. Scans data for PHI exposure (SSN, MRN, DOB patterns), returns findings with severity, score (0-100), and remediation recommendations. |
| drug_lookupB | Look up drug information including label data, adverse events, and related diagnosis codes. Source: OpenFDA (public domain). |
| drug_interactionsB | Check drug-drug interaction signals from FDA adverse event co-reports. Returns co-reported reactions and signal strength. Source: OpenFDA FAERS (public domain). |
| code_reimbursementA | Look up Medicare reimbursement rates for a medical code. Returns RVU values and estimated payment amounts using CMS PFS conversion factor. Source: CMS PFS RVU 2026 (public domain). |
| trials_searchA | Search active clinical trials by condition, ICD-10 code, or intervention. Returns trial details including NCT ID, phase, enrollment, and eligibility. Source: ClinicalTrials.gov (public domain). |
| code_crossrefA | Cross-reference a medical code across ICD-10, CPT, and HCPCS systems. Returns related codes grouped by system. Source: CodeReference DB (ICD-10/HCPCS: public domain). |
| drug_rxnormA | Look up a drug in NIH RxNorm for normalized terminology (RxCUI) and optionally check clinical drug-drug interactions with severity ratings. Source: NIH RxNorm (public domain). |
| provider_paymentsA | Look up pharmaceutical and device company payments to a physician (Sunshine Act data). Returns total payments, breakdown by type, and top paying companies. Source: CMS Open Payments (public domain). |
| disease_surveillanceB | Look up disease surveillance data including case counts and trends by condition and geography. Source: CDC National Notifiable Diseases Surveillance System (public domain). |
| provider_searchB | Search the NPI provider directory. Find healthcare providers by name, specialty, or location. |
| provider_enrichB | AI-enriched provider intelligence from NPI number. Returns practice details, specialties, affiliations, and market context. |
| drug_enrichC | Drug information enrichment via OpenFDA. Returns drug details, indications, interactions, and AI analysis. |
| market_analysisB | Healthcare specialty market analysis for a specific state. Returns provider density, competition metrics, and market opportunity data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools are clearly distinct by their targeted resource and action (e.g., claims_validate vs. code_lookup), but the multiple drug tools (drug_lookup, drug_enrich, drug_rxnorm) have overlapping purposes that could cause confusion despite descriptive names.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., claims_validate, code_lookup, provider_search), making the naming predictable and easy to parse.
With 20 tools, the set is slightly larger than the typical well-scoped range, but the breadth of healthcare domains (claims, codes, drugs, providers, compliance, trials) justifies the count; no tool feels superfluous.
The tool surface covers a wide range of medical workflows (code management, drug interactions, provider intelligence, compliance, etc.). Minor gaps like claim submission or patient data management exist, but core informational and validation tasks are well covered.