la-medicaid-rates
by pipeworx-io
README.md
# @pipeworx/la-medicaid-rates
Louisiana Medicaid per-visit encounter rates for federally qualified health centers (FQHC) and independent rural health clinics (RHC), one row per clinic location: the rate, the date it took effect, and the procedure codes (D0999, H2020, T1015) it is paid on, from the Louisiana Department of Health.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2018+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `la_medicaid_rates(program?, provider?, npi?, medicaid_id?, city?, zip?, procedure?, limit?)` — per-clinic rates. Filter by clinic name fragment, 10-digit NPI, Medicaid provider id, city, zip or procedure code. An unmatched filter returns the nearest clinic names or cities instead of an empty result. Summary statistics (min, median, max, mean) cover every clinic matched.
- `la_rate_periods(program?)` — the schedules served (schedule effective date, file date, range of per-clinic rate dates, clinic and NPI counts) and what is not covered.
## Auth
Keyless.
## Data sources
- Louisiana Department of Health, Louisiana Medicaid fee schedules (FQHC and independent rural health clinic schedules) — public, no account.
Things worth knowing:
- **Rates are per clinic, not statewide per code.** Each clinic has its own rate. The Department lists a clinic on three procedure codes at one rate; each clinic is one row here with its code list, and the data bake refuses to collapse clinics whose codes carry different rates (none do today).
- **Independent RHCs only.** Provider-based RHCs (clinics run by a hospital) are not in the Department's RHC schedule and are not here.
- **One current schedule.** The newest schedule (fee-for-service, effective for dates of service on and after 2026-07-01, file dated 2026-11-13) is served. Each clinic's own `rate_effective` is the date its rate took effect (FQHC 2025-07-01 to 2026-10-06, RHC 2026-07-01 to 2026-09-30). Earlier years are only in the Department's PDF archive and are not read.
- Clinic names are padded and cut off at 28 characters as published. NPI, Medicaid provider id and zip are strings. A few enrolled clinics are just over the state line and carry their own state.
- One RHC (Kaplan Family Care Clinic, provider id 194056) has the letter N where its NPI belongs; it is returned with `npi: null` and found by Medicaid provider id.
- Organisations only: a sole practitioner enrolled under their own name is dropped when the data is read and counted in `individual_rows_dropped` (source rows, 3 codes each).
- Louisiana Medicaid fee-for-service rates; managed-care plans may pay differently.
- Built to a request for more Medicaid states, not from measured demand for Louisiana.
## Stored data and refresh
The two schedules are small (585 clinic rows, about 156 KB). They are read from the Department by `scripts/bake-index.mjs` into `src/la-rates-data.ts`, registered in `workers/gateway/src/pack-baked-indexes.json`; the deploy uploads the table to KV and the gateway injects it on the first call into this pack, so nothing is evaluated at module scope. `node mcps/la-medicaid-rates/scripts/bake-index.mjs` re-reads both files and rewrites the module in place; it refuses a file that changes header, shrinks below its row floor, carries an unknown procedure code, an unreadable date or a non-numeric rate. The portal serves an incomplete certificate chain that Node's fetch rejects, so the script reads with curl when fetch fails. Set `LOCAL_DIR` to a folder holding already-downloaded workbooks to re-run offline.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"la-medicaid-rates": {
"url": "https://gateway.pipeworx.io/la-medicaid-rates/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/la-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 2018+ 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/la_medicaid_rates \
-H 'Content-Type: application/json' \
-d '{"program":"FQHC","city":"Baton Rouge","limit":5}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/la_medicaid_rates`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-la-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/la-medicaid-rates/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"la-medicaid-rates": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-la-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 La 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
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues