analytics-data

NPI Registry

eliotk

by eliotk

Easily perform NPI lookup and doctor NPI lookup with our NPI registry. Find providers by name, location, specialty, or N

Integrates with the National Provider Identifier (NPI) registry to search for healthcare providers and organizations by name, location, specialty, or NPI number with detailed contact information, credentials, and practice locations.

github stars

1

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Official CMS registry dataNo API key needed

best for

  • / Healthcare administrators verifying provider credentials
  • / Medical researchers finding specialists in specific areas
  • / Patients looking up their healthcare providers
  • / Healthcare organizations validating NPI numbers

capabilities

  • / Search providers by name or organization
  • / Look up provider details by NPI number
  • / Filter results by location (city, state, zip)
  • / Find providers by medical specialty
  • / Retrieve contact information and practice locations
  • / Validate NPI numbers

what it does

Search the official US National Provider Identifier (NPI) registry to find healthcare providers and organizations by name, location, specialty, or NPI number.

about

NPI Registry is a community-built MCP server published by eliotk that provides AI assistants with tools and capabilities via the Model Context Protocol. Easily perform NPI lookup and doctor NPI lookup with our NPI registry. Find providers by name, location, specialty, or N It is categorized under analytics data. This server exposes 1 tool that AI clients can invoke during conversations and coding sessions.

how to install

You can install NPI Registry in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

NPI Registry is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

NPI Registry MCP Server 🏥

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.

Overview 📋

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.

Features ✨

  • Search by Provider Name: Find individual healthcare providers by first name, last name, or both
  • Search by Organization: Look up healthcare organizations by name
  • Search by NPI Number: Direct lookup using a specific 10-digit NPI
  • Location-based Search: Filter results by city, state, or postal code
  • Specialty Search: Find providers by their specialty or taxonomy description
  • Comprehensive Data: Returns detailed information including addresses, practice locations, specialties, and other identifiers

Use Cases 💡

  • Verify healthcare provider credentials
  • Find provider contact information and addresses
  • Look up organization details and authorized officials
  • Validate NPI numbers
  • Research provider specialties and taxonomies
  • Find providers in specific geographic areas

Installation 🚀

Prerequisites 📋

  • Python 3.10 or higher
  • uv package manager

Development Setup 🛠️

  1. Clone the repository:

    git clone https://github.com/eliotk/npi-registry-mcp-server.git
    cd npi-registry-mcp-server
    
  2. Install uv (if not already installed):

    curl -LsSf https://astral.sh/uv/install.sh | sh
    
  3. Create a virtual environment and install dependencies:

    uv venv
    source .venv/bin/activate  # On Windows: .venv\Scripts\activate
    uv pip install -e ".[dev]"
    
  4. Run the server directly (for testing):

    uv run python -m npi_registry_mcp.server
    # or using the entry point:
    uv run npi-registry-mcp-server
    

Production Installation 🌟

Install from PyPI (once published):

uv pip install npi-registry-mcp-server

Or install from source:

uv pip install git+https://github.com/eliotk/npi-registry-mcp-server.git

Usage 📚

Available Tools 🛠️

search_npi_registry 🔎

Search the NPI registry with various criteria:

Parameters:

  • first_name (optional): Provider's first name
  • last_name (optional): Provider's last name
  • organization_name (optional): Organization name
  • npi (optional): Specific 10-digit NPI number
  • city (optional): City name
  • state (optional): State abbreviation (e.g., 'CA', 'NY')
  • postal_code (optional): ZIP/postal code (supports wildcards)
  • specialty (optional): Provider specialty or taxonomy
  • limit (optional): Maximum results to return (1-200, default: 10)

Examples:

# Search for a specific provider by name
search_npi_registry(first_name="John", last_name="Smith", state="CA")

# Look up a specific NPI
search_npi_registry(npi="1234567890")

# Find organizations in a city
search_npi_registry(organization_name="Hospital", city="Los Angeles", state="CA")

# Search by specialty
search_npi_registry(specialty="cardiology", state="NY", limit=20)

# Find providers in a specific ZIP code area
search_npi_registry(postal_code="902*", state="CA")

Response Format 📄

The search returns a structured response with:

{
  "success": true,
  "count": 5,
  "results": [
    {
      "npi": "1234567890",
      "entity_type": "Individual",
      "is_organization": false,
      "status": "A",
      "enumeration_date": "2010-05-05",
      "last_updated": "2023-01-15",
      "name": {
        "first": "John",
        "last": "Smith",
        "credential": "MD"
      },
      "addresses": [...],
      "practice_locations": [...],
      "taxonomies": [...],
      "identifiers": [...]
    }
  ]
}

Claude Desktop Configuration 🖥️

To use this MCP server with Claude Desktop, add the following configuration to your Claude Desktop config file:

macOS 🍎

Location: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows 🪟

Location: %APPDATA%/Claude/claude_desktop_config.json

Configuration 📝

{
  "mcpServers": {
    "npi-registry": {
      "command": "uv", # may need full path to executable
      "args": [
        "--directory",
        "/path/to/npi-registry-mcp-server",
        "run",
        "npi-registry-mcp-server"
      ]
    }
  }
}

Verification ✅

  1. Save the configuration file
  2. Restart Claude Desktop completely
  3. Look for the 🔧 icon in Claude Desktop to verify the server is connected
  4. Try asking Claude: "Search for doctors named Smith in California"

Development 👨‍💻

Project Structure 📁

npi-registry-mcp-server/
├── src/
│   └── npi_registry_mcp/
│       ├── __init__.py
│       └── server.py
├── tests/
├── pyproject.toml
├── README.md
└── .gitignore

Running Tests 🧪

uv run pytest

Code Formatting 🎨

# Format code
uv run black src/ tests/

# Sort imports
uv run isort src/ tests/

# Lint
uv run ruff check src/ tests/

# Type checking
uv run mypy src/

Building the Package 📦

uv build

API Reference 📖

This server uses the official NPI Registry API provided by CMS:

Data Sources 🗃️

All data comes directly from the official NPI Registry maintained by:

  • Centers for Medicare & Medicaid Services (CMS)
  • U.S. Department of Health and Human Services

Contributing 🤝

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature-name
  3. Make your changes and add tests
  4. Run the test suite: uv run pytest
  5. Format your code: uv run black src/ tests/
  6. Submit a pull request

License 📄

MIT License - see LICENSE file for details.

Support 🆘

  • Issues: Report bugs and request features via GitHub Issues
  • Documentation: Additional documentation available in the /docs directory
  • API Questions: Refer to the official NPI Registry API documentation

Changelog 📝

v0.1.0 🎉

  • Initial release
  • Basic NPI registry search functionality
  • Support for individual and organization searches
  • Location and specialty filtering
  • Comprehensive provider data retrieval

For more information about the Model Context Protocol, visit: https://modelcontextprotocol.io/

FAQ

What is the NPI Registry MCP server?
NPI Registry is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for NPI Registry?
This profile displays 36 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.636 reviews
  • Noor Lopez· Dec 20, 2024

    NPI Registry is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Ishan Chen· Dec 16, 2024

    I recommend NPI Registry for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Pratham Ware· Dec 12, 2024

    NPI Registry has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Dhruvi Jain· Dec 8, 2024

    Useful MCP listing: NPI Registry is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Oshnikdeep· Nov 27, 2024

    NPI Registry reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Jin Yang· Nov 11, 2024

    We wired NPI Registry into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Hana Bhatia· Nov 7, 2024

    We evaluated NPI Registry against two servers with overlapping tools; this profile had the clearer scope statement.

  • Ishan Tandon· Oct 26, 2024

    Useful MCP listing: NPI Registry is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Ganesh Mohane· Oct 18, 2024

    I recommend NPI Registry for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Noor Haddad· Oct 2, 2024

    According to our notes, NPI Registry benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

showing 1-10 of 36

1 / 4