Npi Registry MCP
The NPI Registry MCP Server provides access to the CMS National Provider Identifier Registry, containing data on approximately 7 million US healthcare providers. It enables agents to search for providers using various filters such as name, organization, taxonomy, and location, or to fetch specific provider details by their 10-digit NPI number. The server operates via a JSON-RPC 2.0 gateway and supports integration with major AI clients like Cursor, VS Code, and Claude.
Package and access
Local package with source-attributed installation metadata. Koskamo does not execute packages during review.
What you can do with it
- Search healthcare providers by name, taxonomy, or location
- Fetch specific provider details using a 10-digit NPI
- Identify providers by organization name or city/state
- Retrieve provider contact and credential information
Source and maintenance
- Last repository push
- Maintenance checked
Packages and installation
Source-provided package data. Koskamo has not executed or live-probed this package.
@pipeworx/mcp-npi-registry 0.2.0
{
"version": "0.2.0",
"transport": "stdio",
"identifier": "@pipeworx/mcp-npi-registry",
"registryType": "npm",
"environmentVariables": [
{
"name": "PIPEWORX_API_KEY",
"description": "Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap."
}
]
}Tools
Reported by the attributed source; not independently observed by Koskamo.
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · repository · passed · metadata changed · updated
- · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown
Connect from your client
Each snippet configures the same source-provided package; replace placeholders before use.
Cursor
{
"mcpServers": {
"npi-registry-mcp-pipeworx-mcp-npi-registry": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-npi-registry@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<YOUR_PIPEWORX_API_KEY>"
}
}
}
}Cline
{
"mcpServers": {
"npi-registry-mcp-pipeworx-mcp-npi-registry": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-npi-registry@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<YOUR_PIPEWORX_API_KEY>"
}
}
}
}VS Code
{
"servers": {
"npi-registry-mcp-pipeworx-mcp-npi-registry": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-npi-registry@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<YOUR_PIPEWORX_API_KEY>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"npi-registry-mcp-pipeworx-mcp-npi-registry": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-npi-registry@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<YOUR_PIPEWORX_API_KEY>"
}
}
}
}Let your agent find its tools
Find servers like Npi Registry MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.