# npi-providers-mcp-server [Health: Active]

**Category:** 🧬 Biology & Bioinformatics  
**Repository:** https://github.com/cyanheads/npi-providers-mcp-server  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1051  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/npi-providers-mcp-server

## Description
Look up US healthcare providers in the NPPES NPI registry and resolve NUCC specialty codes.

## Tools
Capabilities this server exposes over MCP:

- **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 NPPES professional-practice record for up to 10 NPIs — taxonomies, practice addresses, credentials, identifiers, endpoints, and status. Only LOCATION address rows are kept for individual providers.
- **npi_lookup_taxonomy** — Resolve, fetch, or browse the NUCC Healthcare Provider Taxonomy — fully offline.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "npi-providers-mcp-server": {
    "command": "npx",
    "args": ["-y","@cyanheads/npi-providers-mcp-server"]
  }
}
```

## Documentation

## What npi-providers-mcp-server does

npi-providers-mcp-server exposes US healthcare provider data through MCP. It searches the NPPES NPI Registry using provider names, organizations, practice locations, provider types, and specialties. Plain-language specialty terms are matched against the bundled NUCC taxonomy before the registry search runs.

The server also retrieves professional-practice information for NPIs, including taxonomies, credentials, practice addresses, identifiers, communication endpoints, and status. For individual providers, only address records marked as practice locations are retained; mailing addresses are excluded.

NUCC taxonomy data is included locally and contains 883 taxonomy codes. The taxonomy tool can resolve a term, retrieve an exact code, or browse its grouping, classification, and specialization hierarchy. Two MCP resources mirror tool results: `npi://provider/{npi}` and `npi://taxonomy/{code}`. A bundled guide skill covers specialty cohorts, provider identity, and the limits of exhaustive directory searches.

## How it works

Search requests require at least one criterion. Individual and organization filters cannot be mixed, and a state by itself is rejected. Results are compact rows containing the NPI, name, primary taxonomy, primary practice location, and status. Matching locations or alternate names can be identified in the response, along with the taxonomy resolution applied to the query.

Search results are paginated with `skip` and `limit`; the limit is capped at 200. The API does not report a true total. When the result window reaches its upper boundary, continuation postal codes indicate how a broad search can continue.

Provider lookups validate NPI check digits before querying the registry. Batch responses separate found records, confirmed missing NPIs, upstream failures that may be retried, and invalid NPIs. Taxonomy resolution excludes inactive codes, while exact lookups and browsing retain inactive entries and can show replacement codes.

## Setup and configuration

The package can run through STDIO or Streamable HTTP. MCP client installation links are provided for Claude Desktop, Cursor, and VS Code, and the package can be launched through the npm package command used by those installers. A public Streamable HTTP endpoint is available at `https://npi-providers.caseyjhand.com/mcp`.

No API key or account is needed: registry requests use the public CMS NPPES NPI Registry API. NUCC specialty resolution and code lookup use the taxonomy bundled with the server and loaded into memory at startup, so those operations do not require a separate upstream service.

The underlying framework supports optional authentication modes, storage backends, structured logging, and OpenTelemetry tracing. These are framework capabilities for deployments that need them rather than prerequisites for basic registry access.

## Tools and capabilities

- `npi_search_providers` searches by individual name, organization, location, provider type, or specialty. It supports first-name alias handling and wildcard criteria within the documented input rules.
- `npi_get_provider` accepts NPI values, validates them, removes duplicates, and returns decoded records for the valid values it looks up.
- `npi_lookup_taxonomy` provides `resolve`, `get`, and `browse` modes against the local NUCC dataset.
- `npi://provider/{npi}` exposes one decoded provider record as JSON.
- `npi://taxonomy/{code}` exposes one taxonomy entry as JSON and is publicly cached for 24 hours.

## Limitations and notes

Searches operate on NPPES registry data and are not a guarantee of an exhaustive directory result. Broad queries may require pagination or continuation postal codes. Provider retrieval distinguishes confirmed absence from upstream failure, while invalid NPIs are rejected without a registry request.

Taxonomy sections describe categories in the NUCC taxonomy, not an NPI entity's provider type. Use the search tool's `provider_type` filter when filtering by provider entity type. Individual provider results intentionally omit mailing-address rows.

_Full upstream README: https://allmcps.com/mcp/npi-providers-mcp-server/readme_