Skip to main content
Glama
README.md
# @pipeworx/il-medicaid-rates

Illinois Medicaid FQHC (Federally Qualified Health Center) encounter rates per health center agency: the medical, dental and behavioral-health dollar rate for each calendar year CY2021 to CY2026, from the Illinois Department of Healthcare and Family Services (HFS).

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2007+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Tools

- `il_fqhc_rates(provider?, calendar_year?, row_type?, has_dental?, has_behavioral_health?, limit?)` — rates per agency per calendar year (CY2026 by default; `"all"` for every year). Filter by agency name fragment. An unmatched name returns the nearest agency names and says what the files do not hold. A person-shaped search returns no row.
- `il_fqhc_rate_periods()` — the calendar years available, HFS publication date, health center counts, and what is not covered.

## Auth

Keyless.

## Data sources

- Illinois Department of Healthcare and Family Services (HFS), Medicaid reimbursement, Federally Qualified Health Center rates. Public, no account.

Things worth knowing:

- **Grain: one row per FQHC agency per calendar year.** Not per site. The files carry no NPI, Medicaid provider id, address, city or county, so a place name matches only where it is part of the agency name.
- **FQHCs only.** Rural health clinics and other encounter-rate clinics are not in these files.
- A blank dental or behavioral-health rate (returned as `null`) means HFS lists no such rate for that agency, not zero.
- Agency names are free text as HFS publishes them, and an agency can be renamed between years (for example a "Wabash" health center), so a name fragment can match in some years and not others.
- Two "interim rate" rows (downstate, metro Chicago) are the rates HFS applies to a clinic without its own rate. They come back with `row_type: "interim"` and are left out of the summaries.
- Every response carries the calendar year, its effective span (1 January to 31 December), `data_as_of` (the HFS publication date) and a scope line. Rates are US dollars per encounter, as published.
- Organisations only: any row whose name reads as a person is dropped when the data is read and counted in `individual_rows_dropped` (0 in the current files).
- Built as a Bruce ask ("more states", Medicaid build-out), with no measured demand yet.

## Data and refresh

About 380 rows (64 KB), registered in `workers/gateway/src/pack-baked-indexes.json`; the gateway loads it on the first call into this pack, so nothing is evaluated at module scope. `node mcps/il-medicaid-rates/scripts/bake-index.mjs` re-reads the HFS rate files and rewrites `src/il-rates-data.ts`; it refuses a file that changes layout, shrinks below its floor or carries a non-numeric rate. HFS posts a new yearly file each December: add one entry to `FILES` in that script.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "il-medicaid-rates": {
      "url": "https://gateway.pipeworx.io/il-medicaid-rates/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/il-medicaid-rates/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 2007+ 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/il_fqhc_rates \
  -H 'Content-Type: application/json' \
  -d '{"provider":"Erie","calendar_year":"all","limit":6}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/il_fqhc_rates`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-il-medicaid-rates` 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/il-medicaid-rates/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "il-medicaid-rates": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-il-medicaid-rates"]
    }
  }
}
```

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 Il Medicaid Rates 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