Search NPPES providers and resolve NUCC specialty codes via MCP over STDIO or Streamable HTTP.
Search NPPES providers and resolve NUCC specialty codes via MCP over STDIO or Streamable HTTP.
Public Hosted Server: https://npi-providers.caseyjhand.com/mcp
US healthcare provider directory over the NPPES NPI Registry, with plain-language specialty terms resolved offline against a bundled NUCC taxonomy. Search providers by name, organization, location, and specialty; decode NPIs into full provider records; and resolve or browse the NUCC taxonomy directly. Runs as a stdio process, a local Streamable HTTP server, or the public hosted endpoint above.
| Tool | Description |
|---|---|
npi_search_providers | Search the NPPES registry by name, organization, location, provider type, and specialty. Plain-language specialties resolve through the bundled NUCC taxonomy before searching. |
npi_get_provider | Fetch the complete NPPES record for up to 10 NPIs — taxonomies, addresses, credentials, identifiers, endpoints, and status. |
npi_lookup_taxonomy | Resolve, fetch, or browse the NUCC Healthcare Provider Taxonomy — fully offline. |
| Resource | Description |
|---|---|
npi://provider/{npi} | A single provider's full decoded record by NPI — the resource twin of npi_get_provider. |
npi://taxonomy/{code} | A single NUCC taxonomy entry by code — the resource twin of npi_lookup_taxonomy mode get. |
All resource data is also reachable via tools; the resources are convenience twins for resource-capable clients.
npi_search_providers toolname_search shortcut, explicit first_name / last_name, organization_name, city / state / postal_code, and provider_type (individual / organization); at least one criterion is required and the registry rejects state-only searchesspecialty resolves through the bundled NUCC taxonomy to the registry's exact description before searching, echoed back via resolvedTaxonomies / appliedTaxonomyDescription; taxonomy_description is an escape hatch for an already-known exact description (mutually exclusive with specialty)*) name/organization matching requires at least 2 leading characterslimit 1–200 (default 10), skip 0–1000; the registry never reports a true match total, only the first 1200 matches are reachable, and the response discloses page-size-not-total via truncated / noticeno_search_criteria, conflicting_specialty, unresolved_specialty, invalid_search_fieldnpi_get_provider toolfound (resolved records), notFound (confirmed absence — deactivated or never enumerated), errored (upstream failure, distinct from absence — retry these)none_found only when every requested NPI is a confirmed absence; an upstream failure on any NPI surfaces as that underlying error insteadnpi_lookup_taxonomy toolresolve (plain-language term → matching codes/descriptions), get (exact code → full entry), browse (walk grouping → classification → specialization, filterable by grouping and NPI section)resolve / browse cap results at limit (≤50, default 20) and disclose truncated; page past the cap with skip (0–1000, raised by limit each call)specialization (or classification when specialization is absent) is the exact value npi_search_providers.taxonomy_description acceptsno_match, missing_argumentnpi://provider/{npi} resourcenpi_get_provider, for one NPI, as application/jsonnpi must be a well-formed 10-digit NPI; no_record when the registry has none (deactivated or never enumerated)npi://taxonomy/{code} resourcenpi_lookup_taxonomy mode get, as application/json; cached publicly for 24 hourscode must match ^\d{3}[A-Z0-9]{6}X$; no_match when no entry exists for the codeBuilt on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.
NPI/NPPES-specific:
Errors[] body on validation failure and maps it to typed, recoverable error reasonsAgent-friendly output:
taxonomy_description sent to the registry are echoed back, so agents can see what was actually searched and re-run with a different codenpi_get_provider returns per-NPI found / notFound / errored rows instead of failing the whole batchA public instance is available at https://npi-providers.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP, with this client config:
{
"mcpServers": {
"npi-providers-mcp-server": {
"type": "streamable-http",
"url": "https://npi-providers.caseyjhand.com/mcp"
}
}
}
Add the following to your MCP client configuration file. No API key is required — the upstream NPPES registry is keyless.
{
"mcpServers": {
"npi-providers-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/npi-providers-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Or with npx (no Bun required):
{
"mcpServers": {
"npi-providers-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@cyanheads/npi-providers-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Or with Docker:
{
"mcpServers": {
"npi-providers-mcp-server": {
"type": "stdio",
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/npi-providers-mcp-server:latest"]
}
}
}
For Streamable HTTP, set the transport and start the server:
MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
# Server listens at http://localhost:3010/mcp
git clone https://github.com/cyanheads/npi-providers-mcp-server.git
cd npi-providers-mcp-server
bun install
cp .env.example .env
# edit .env only if you need to override the NPPES base URL or timeout
No required variables — the server runs out of the box against the keyless NPPES registry. All variables below are optional overrides.
| Variable | Description | Default |
|---|---|---|
NPPES_API_BASE_URL | NPPES NPI Registry API base URL. Override for a private mirror or testing. | https://npiregistry.cms.hhs.gov/api |
NPPES_TIMEOUT_MS | Per-request HTTP timeout for NPPES calls, in milliseconds. | 15000 |
MCP_TRANSPORT_TYPE | Transport: stdio or http. | stdio |
MCP_HTTP_PORT | Port for the HTTP server. | 3010 |
MCP_AUTH_MODE | Auth mode: none, jwt, or oauth. | none |
MCP_SESSION_MODE | HTTP session handling: stateless, stateful, or auto. This server pins stateless; the schema default auto resolves to stateful. | stateless |
MCP_LOG_LEVEL | Log level (RFC 5424). | info |
STORAGE_PROVIDER_TYPE | Storage backend. | in-memory |
OTEL_ENABLED | Enable OpenTelemetry instrumentation (spans, metrics, completion logs). | false |
See .env.example for the full list of optional overrides.
Build and run:
# One-time build
bun run rebuild
# Run the built server
bun run start:stdio
# or
bun run start:http
Run checks and tests:
bun run devcheck # Lint, format, typecheck, security
bun run test # Vitest test suite
bun run lint:mcp # Validate MCP definitions against spec
docker build -t npi-providers-mcp-server .
docker run --rm -e MCP_TRANSPORT_TYPE=http -p 3010:3010 npi-providers-mcp-server
The Dockerfile defaults to HTTP transport, stateless session mode, and logs to /var/log/npi-providers-mcp-server. OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.
| Directory | Purpose |
|---|---|
src/index.ts | createApp() entry point — registers tools and resources, inits services. |
src/config | Server-specific environment variable parsing and validation with Zod. |
src/mcp-server/tools | Tool definitions (*.tool.ts). |
src/mcp-server/resources | Resource definitions (*.resource.ts). |
src/services/nppes | NPPES NPI Registry API client — query building, Errors[]-on-200 detection, normalization. |
src/services/taxonomy | Bundled NUCC taxonomy service — in-memory index for resolve / get / browse. |
tests/ | Unit and integration tests mirroring src/. |
See CLAUDE.md/AGENTS.md for development guidelines and architectural rules. The short version:
try/catch in tool logicctx.log for request-scoped logging, ctx.state for tenant-scoped storagecreateApp() arraysProvider data from the CMS NPPES NPI Registry (public domain). The bundled specialty codes are the NUCC Health Care Provider Taxonomy, © American Medical Association on behalf of the National Uniform Claim Committee (NUCC), redistributed unmodified beyond formatting under the NUCC permission. See NOTICE.
Issues are welcome. Run checks and tests before submitting:
bun run devcheck
bun run test
Apache-2.0 — see LICENSE for details.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @cyanheads/npi-providers-mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cyanheads-npi-providers-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/npi-providers-mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.cyanheads/npi-providers-mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.