Medical MCP Server

If you already use Medical, the medical mcp server is the piece that lets your assistant work with it directly. Offline US medical code lookup and crosswalk — ICD-10-CM, ICD-10-PCS, HCPCS Level II. Keyless.

What the server does

• Declarative tool definitions — single file per tool, framework handles registration and validation
• Unified error handling — handlers throw, framework catches, classifies, and formats
• Typed per-tool error contracts — capable clients preview failure modes from tools/list
• Structured logging with optional OpenTelemetry tracing
• STDIO and Streamable HTTP transports
• Bundled SQLite + FTS5 index — offline, keyless, deterministic; no runtime network I/O, no rate limit

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• medcode_get_code — Decode 1–50 codes to their official descriptions. Auto-detects the system per code; partial-success found / notFound
• medcode_search_codes — Full-text search over official descriptions — go from a clinical description to the code
• medcode_check_code — Validate a code's existence, currency, and billability, with a whyNot for non-billable/terminated cases
• medcode_map_codes — Crosswalk a code within its hierarchy (parents/children) or a drug across RxNorm (name ↔ RXCUI, NDC ↔ RXCUI, RXCUI → ingredients/brands)
• medcode_browse_hierarchy — Walk a system's hierarchy for discovery without a search term
• medcode_list_systems — List bundled systems with release identifiers, effective dates, and code counts (provenance)
• Prerequisites — The Prerequisites tool exposed by this server
• Installation — The Installation tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: MCP_TRANSPORT_TYPE, MCP_LOG_LEVEL, MEDCODE_DB_PATH, MCP_HTTP_ENDPOINT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Bun v1.3 or higher (or Node.js v24+ — the server falls back to the better-sqlite3 optional dependency when not run under Bun). - No API key, account, or network access required.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Medical's toolset — medcode_get_code, medcode_search_codes, medcode_check_code and 5 more — is a fair guide to whether it matches your workflow. It is maintained by cyanheads; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.