Do I need an API key for the CDC tools?

Most CDC Content Services are public and do not require a key. However, providing an HHS API Key (from the digitalmedia.hhs.gov portal) can provide higher rate limits and access to restricted resources.

What kind of health recommendations are provided?

The recommendations are retrieved from the MyHealthfinder API (health.gov), providing evidence-based preventative clinical services and wellness tips authorized by the U.S. Department of Health and Human Services.

Can I embed CDC content into my own website?

Yes! Use the `get_syndication_html` tool with a media ID. It will return the standard HTML snippet that you can copy and paste into your site to display up-to-date CDC content automatically.

CDC Public Health / 美国疾控中心 MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: CDC Public Health / 美国疾控中心
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to CDC Public Health / 美国疾控中心 through Vinkius, pass the Edge URL in the `mcps` parameter and every CDC Public Health / 美国疾控中心 tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="CDC Public Health / 美国疾控中心 Specialist",
    goal="Help users interact with CDC Public Health / 美国疾控中心 effectively",
    backstory=(
        "You are an expert at leveraging CDC Public Health / 美国疾控中心 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 CDC Public Health / 美国疾控中心 "
        "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 CDC Public Health / 美国疾控中心 MCP Server

Empower your AI agent to orchestrate your public health research and content syndication with the U.S. Centers for Disease Control and Prevention (CDC). By connecting the CDC to your agent, you transform complex health resource searching, topic auditing, and evidence-based recommendation retrieval into a natural conversation. Your agent can instantly retrieve detailed media metadata, access comprehensive health topic lists, and even provide personalized health recommendations from the official MyHealthfinder API without you ever needing to navigate multiple government portals. Whether you are conducting academic research or coordinating a public health awareness campaign, your agent acts as a real-time health data coordinator, providing accurate results from a single, authorized source.

When paired with CrewAI, CDC Public Health / 美国疾控中心 becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CDC Public Health / 美国疾控中心 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

Media Orchestration — Search the vast CDC library for articles, infographics, and HTML resources.
Content Syndication — Retrieve HTML embed codes to share official health content directly on your platforms.
Topic Auditing — Access the complete catalog of health topics and their associated metadata.
Health Recommendations — Retrieve personalized, evidence-based health tips using age and gender parameters.
Multilingual Support — Access resources in various languages supported by the CDC Content Services.

The CDC Public Health / 美国疾控中心 MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect CDC Public Health / 美国疾控中心 to CrewAI via MCP

Follow these steps to integrate the CDC Public Health / 美国疾控中心 MCP Server with CrewAI.

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 CDC Public Health / 美国疾控中心

Why Use CrewAI with the CDC Public Health / 美国疾控中心 MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with CDC Public Health / 美国疾控中心 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

CDC Public Health / 美国疾控中心 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the CDC Public Health / 美国疾控中心 MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries CDC Public Health / 美国疾控中心 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 CDC Public Health / 美国疾控中心, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain CDC Public Health / 美国疾控中心 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 CDC Public Health / 美国疾控中心 against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

CDC Public Health / 美国疾控中心 MCP Tools for CrewAI (8)

These 8 tools become available when you connect CDC Public Health / 美国疾控中心 to CrewAI via MCP:

get_media_details

Get media item info

get_recent_health_media

Get latest media items

get_syndication_html

Get embed code for media

get_topic_metadata

Get topic details

list_health_topics

List public health topics

list_supported_languages

List available languages

search_health_media

) by keyword. Search CDC media items

search_hhs_resources

Search HHS Digital Media

Example Prompts for CDC Public Health / 美国疾控中心 in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with CDC Public Health / 美国疾控中心 immediately.

"Search for CDC resources about 'Influenza' and show me the latest articles."

"Get health recommendations for a 35-year-old female."

"List the most recently published health resources from the CDC."

Troubleshooting CDC Public Health / 美国疾控中心 MCP Server with CrewAI

Common issues when connecting CDC Public Health / 美国疾控中心 to CrewAI through the 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.

CDC Public Health / 美国疾控中心 + CrewAI FAQ

Common questions about integrating CDC Public Health / 美国疾控中心 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.