@pipeworx/medicaid-quality
by pipeworx-io
README.md
# @pipeworx/medicaid-quality
State-level Medicaid and CHIP quality and service-use measures: the CMS Child and Adult Core Set quality measures (rates by state and year, 2021-2025) and the T-MSIS based service-use measures (well-child visits, mental health and substance use services, blood lead screening, contraceptive care, acute care, behavioral health, prematurity and severe maternal morbidity).
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2015+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `medicaid_quality_measures(query?, core_set?, domain?, include_retired?, limit?)` -- lists the ~70 Core Set measures with id, abbreviation, domain, years reported and number of states reporting.
- `medicaid_quality_rate(measure, state?, year?, all_populations?)` -- state-reported rate for one measure; one state across years or every state in one year. Includes the population reported, national median and number of states reporting.
- `medicaid_quality_compare(measure, year?, rate?, order?, limit?)` -- ranks the reporting states on one rate of one measure, lists states that did not report, and gives the median.
- `medicaid_service_use_annual(dataset, year?, geography?, category?, subpopulation_topic?, limit?)` -- annual T-MSIS service use: `well_child`, `mental_health_sud` (national, by age, race/ethnicity, program type), `prematurity_smm` (by state). 2020-2022.
- `medicaid_service_use_monthly(dataset, state?, year?, month?, service?, condition?, limit?)` -- monthly state counts and rates per 1,000 beneficiaries: `blood_lead`, `contraceptive`, `acute_care`, `behavioral_health`. 2018-2022.
## Auth
Keyless.
## Data sources
- CMS, Medicaid and CHIP Child and Adult Core Set quality measures (production release; state-reported through CMS's Quality Measure Reporting system, analysed by Mathematica for CMS).
- CMS, Medicaid and CHIP Scorecard service-use measures built from T-MSIS (Transformed Medicaid Statistical Information System) Analytic Files.
Every response carries `source` and `data_as_of` (the Core Set year, data version and ETL version for the quality tools; the publisher's last-modified time for service-use tools).
Notes for the next person:
- The federal Medicaid open-data catalog carries several copies of the same Core Set tables from CMS's development, implementation, feature and local test environments (titles carrying dev, imp, impl, test, local). Those are test builds and have higher version numbers than production. This pack reads only the release titled "(Production)"; the dataset ids are pinned at the top of `src/index.ts`. When CMS promotes a new production release the ids change and must be updated.
- Rates are published as fractions (0.531 = 53.1%) when `value_indicator` is `percent`; `display` gives the formatted percent. A null `value` means the state did not report or the rate was suppressed.
- Each state/year/rate can have several population variants (Medicaid only, Separate CHIP, combined). The default returns the publisher's headline (combined) variant; `all_populations: true` returns all.
- `well_child` and `mental_health_sud` are national-only breakouts; asking for a state returns the valid geography list.
- Unmatched measure, state, year or filter values return near matches or the list of valid values rather than an empty result.
- No data is stored by this pack; every call is a live request to the CMS Medicaid open data API.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"medicaid-quality": {
"url": "https://gateway.pipeworx.io/medicaid-quality/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/medicaid-quality/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:
```json
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
```
Both URLs reach the same gateway and the same 2015+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.
## No MCP client? Call it over HTTP
```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/medicaid_quality_measures \
-H 'Content-Type: application/json' \
-d '{"query":"follow-up hospitalization","core_set":"Child"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/medicaid_quality_measures`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-medicaid-quality` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/medicaid-quality/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"medicaid-quality": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-medicaid-quality"]
}
}
}
```
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.
## Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:
```
ask_pipeworx({ question: "your question about Medicaid Quality data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues