Log inSubmit server
Npi Providers MCP Server logo

Npi Providers MCP Server

Search the US NPPES registry, retrieve provider records, and resolve NUCC specialty taxonomy codes over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Npi Providers MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "npi-providers-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/npi-providers-mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

npi-providers-mcp-server connects MCP clients to the public US NPPES NPI Registry and a bundled NUCC Healthcare Provider Taxonomy. Its tools search providers, retrieve decoded records by NPI, and resolve or browse specialty codes without a second taxonomy service. It supports STDIO and Streamable HTTP, including a publicly hosted endpoint, and fits directory lookup, provider identity, and specialty research workflows.

Use cases

  • Search for providers by specialty and practice location
  • Retrieve and inspect records for a set of NPIs
  • Resolve plain-language specialties to NUCC taxonomy codes
  • Browse NUCC taxonomy groupings and classifications
  • Verify provider status, credentials, identifiers, and endpoints

Key features

  • NPPES provider search by name, organization, location, type, and specialty
  • Batch NPI validation and professional-practice record retrieval
  • Offline NUCC taxonomy resolution, lookup, and browsing
  • STDIO and Streamable HTTP transports
  • Provider and taxonomy MCP resources
  • Keyless access to the public CMS NPPES API

Tools3

What Npi Providers MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~129 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 53d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @cyanheads/npi-providers-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit9d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Npi Providers MCP Server works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Npi Providers MCP Server

npi-providers-mcp-server is an MCP server that connects AI clients to the US NPPES NPI Registry and a bundled NUCC Healthcare Provider Taxonomy. Its main tools search providers, retrieve records for NPIs, and resolve, fetch, or browse specialty taxonomy codes, with support for STDIO and Streamable HTTP transports.

Install it through the provided MCP links for Claude Desktop, Cursor, or VS Code, which launch the npm package with `npx`. It can also be reached through the public Streamable HTTP endpoint at `https://npi-providers.caseyjhand.com/mcp`.

No, it uses the public CMS NPPES NPI Registry API without an API key or account. NUCC taxonomy resolution and lookups use data bundled with the package and loaded locally at startup.

It returns decoded professional-practice data including taxonomies, practice addresses, credentials, identifiers, endpoints, and status. For individual providers, only address rows marked as practice locations are included.

Yes, Cursor is one of the clients with a provided installation link. The server also supports standard STDIO and Streamable HTTP MCP connections.

Related MCP servers

All in Biology & Bioinformatics All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNpi Providers MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/npi-providers-mcp-server?style=directory)](https://allmcps.com/mcp/npi-providers-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/npi-providers-mcp-server"><img src="https://allmcps.com/api/badge/npi-providers-mcp-server?style=directory" alt="Npi Providers MCP Server on AllMCPs" /></a>