@pipeworx/npi-registry

CMS NPI Registry MCP — every US healthcare provider with a National Provider Identifier (~7M individuals + organizations). No auth.

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

• search(number?, name?, first_name?, last_name?, organization_name?, taxonomy?, city?, state?, postal_code?, country_code?, npi_type?, address_purpose?, limit?, skip?)

• get_provider(npi) — convenience: lookup by 10-digit NPI

Related MCP server: npi-providers-mcp-server

Data source

https://npiregistry.cms.hhs.gov/api/?version=2.1 — public REST.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "npi-registry": {
      "url": "https://gateway.pipeworx.io/npi-registry/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/npi-registry/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/npi_registry_search \
  -H 'Content-Type: application/json' \
  -d '{"name":"John Smith","taxonomy":"Internal Medicine","state":"CA"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/npi_registry_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "npi-registry": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-npi-registry"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-npi-registry

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Npi Registry data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides

• pipeworx.io

License

MIT