A Model Context Protocol (MCP) server for searching the National Provider Identifier (NPI) registry. This server provides tools to search and
A Model Context Protocol (MCP) server for searching the National Provider Identifier (NPI) registry. This server provides tools to search and retrieve information about healthcare providers and organizations in the United States. The npi registry mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.
NPI is a unique identification number for covered health care providers in the United States. This MCP server allows Claude and other MCP-compatible clients to search the official NPI registry maintained by the Centers for Medicare & Medicaid Services (CMS), and integrates the results into an LLM context for enhanced analysis and insights.
The server ships on PyPI as npi-registry-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
Documentation — https://npiregistry.cms.hhs.gov/registry/help-apiAmong the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Npi Registry's toolset — Documentation — is a fair guide to whether it matches your workflow. It is maintained by eliotk; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Npi Registry's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Documentation | https://npiregistry.cms.hhs.gov/registry/help-api |
{
"mcpServers": {
"npi-registry": {
"command": "uvx",
"args": ["npi-registry-mcp-server"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.