Cdc MCP Server

Cdc MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server for discovering and querying CDC public health datasets via the Socrata SODA API.

What you get

• Declarative tool definitions — single file per tool, framework handles registration and validation
• Unified error handling across all tools
• Pluggable auth (none, jwt, oauth)
• Swappable storage backends: in-memory, filesystem, Supabase, Cloudflare KV/R2/D1
• Structured logging with optional OpenTelemetry tracing
• Runs locally (stdio/HTTP) or on Cloudflare Workers from the same codebase

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Cdc is connected, these are the calls the assistant has available:

• cdc_discover_datasets — Search the catalog by keyword, category, or tag. Entry point for all queries
• cdc_get_dataset_schema — Fetch column schema, row count, and metadata for a dataset. Essential before writing SoQL queries
• cdc_query_dataset — Execute SoQL queries — filter, aggregate, sort, full-text search, and field selection
• cdc_query_wonder — Query CDC WONDER for national mortality statistics (deaths, population, crude/age-adjusted rates) by year, age, sex, and race, filtered by ICD-10
• Prerequisites — The Prerequisites tool exposed by this server
• Installation — The Installation tool exposed by this server

Configuration and credentials

You will need 5 environment variables: MCP_TRANSPORT_TYPE, MCP_LOG_LEVEL, CDC_APP_TOKEN, CDC_BASE_URL, CDC_CATALOG_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Bun v1.3.2 or higher. - Optional: Socrata app token for higher rate limits.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cdc mcp server does with a few real requests.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cdc's toolset — cdc_discover_datasets, cdc_get_dataset_schema, cdc_query_dataset and 3 more — is a fair guide to whether it matches your workflow. It is maintained by cyanheads; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.