CMS.gov Data MCP Server for CrewAIGive CrewAI instant access to 8 tools to Get Dataset Metadata, Get Doctor By Npi, Get Hospital Ratings, and more

Name: CMS.gov Data
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Connect your CrewAI agents to CMS.gov Data through Vinkius, pass the Edge URL in the `mcps` parameter and every CMS.gov Data tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The CMS.gov Data MCP Server for CrewAI is a standout in the Brain Trust category — giving your AI agent 8 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="CMS.gov Data Specialist",
    goal="Help users interact with CMS.gov Data effectively",
    backstory=(
        "You are an expert at leveraging CMS.gov Data tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in CMS.gov Data "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About CMS.gov Data MCP Server

Connect to the Centers for Medicare & Medicaid Services (CMS) open data platform and query the US government's most comprehensive healthcare database.

When paired with CrewAI, CMS.gov Data becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CMS.gov Data tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Provider Search — Search 2.4 million+ Medicare-enrolled doctors and clinicians by name, specialty, or location, with NPI numbers and practice addresses
Hospital Intelligence — Query hospital quality star ratings (1-5), types (Acute Care, Critical Access), and emergency services availability across all 50 states
Nursing Home Lookup — Search skilled nursing facilities and long-term care homes with quality ratings and provider details
Open Data Catalog — Browse and retrieve metadata from hundreds of CMS open datasets covering Medicare utilization, prescription drugs, and healthcare spending

The CMS.gov Data MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 8 CMS.gov Data tools available for CrewAI

When CrewAI connects to CMS.gov Data through Vinkius, your AI agent gets direct access to every tool listed below — spanning public-health, medicaid, provider-data, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get dataset metadata on CMS.gov Data

Returns the dataset title, full description, publication date, last modification date, and publisher information. Use the dataset ID obtained from list_datasets. Get detailed metadata for a specific CMS dataset

get

Get doctor by npi on CMS.gov Data

Returns the provider's full name, primary and secondary specialties, practice address, city, state, ZIP code, and Medicare enrollment status. NPI is a unique 10-digit number (e.g. "1234567890"). Get detailed provider information by NPI number

get

Get hospital ratings on CMS.gov Data

Filter by US state code (e.g. "CA", "NY", "TX") to see hospitals in that state. Returns overall ratings (1-5 stars), hospital type, and emergency services. Without a state filter, returns top-rated hospitals nationwide. Get hospital quality ratings, optionally by state

list

List datasets on CMS.gov Data

gov. Returns dataset identifiers, titles, descriptions, publication dates, and last-modified timestamps. The CMS data catalog includes datasets on Medicare utilization, hospital quality measures, provider enrollment, prescription drugs, and more. List available CMS open data datasets

Search doctors on CMS.gov Data

Accepts names, specialties, cities, or states. Returns NPI numbers, full names, primary specialty, practice addresses, and Medicare enrollment IDs. The database covers 2.4 million+ active providers across the United States. Search for doctors and clinicians enrolled in Medicare

Search hospitals on CMS.gov Data

Accepts hospital names, cities, or states. Returns provider IDs, hospital names, types (Acute Care, Critical Access, etc.), overall quality ratings (1-5 stars), locations, and emergency services availability. Search for hospitals by name or location

Search nursing homes on CMS.gov Data

Returns facility names, provider IDs, locations, and overall quality ratings. Useful for finding elder care facilities in a specific area. Search nursing homes and long-term care facilities

Search providers by specialty on CMS.gov Data

Examples: "Cardiology", "Internal Medicine", "Orthopedic Surgery", "Family Practice", "Dermatology", "Psychiatry". Returns matching providers with their NPI, name, practice location, and enrollment details. Search for healthcare providers by medical specialty

Connect CMS.gov Data to CrewAI via MCP

Follow these steps to wire CMS.gov Data into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from CMS.gov Data

Why Use CrewAI with the CMS.gov Data MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with CMS.gov Data through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

CMS.gov Data + CrewAI Use Cases

Practical scenarios where CrewAI combined with the CMS.gov Data MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries CMS.gov Data for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries CMS.gov Data, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain CMS.gov Data tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries CMS.gov Data against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for CMS.gov Data in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with CMS.gov Data immediately.

"Search for cardiologists in New York using CMS.gov data."

"List top-rated hospitals in California according to CMS data."

"Get details for the provider with NPI 1234567890 from CMS."

Troubleshooting CMS.gov Data MCP Server with CrewAI

Common issues when connecting CMS.gov Data to CrewAI through Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

CMS.gov Data + CrewAI FAQ

Common questions about integrating CMS.gov Data MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.