oh-medicaid-rates
by pipeworx-io
README.md
# @pipeworx/oh-medicaid-rates
Ohio Medicaid FQHC and RHC prospective payment system (PPS) statewide parameters: the per-service add-on dollars and the rules by which per-visit payment amounts (PVPAs) are set. **Ohio does not publish per-clinic PVPAs**, so this pack does not serve them; it serves the statewide figures only.
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
- `oh_fqhc_pvpa_addons(service?)` — FQHC PVPA add-on dollars by service, original schedule and the reduced schedule effective 2025-07-01. Optional `service` substring filter; a filter with no match says so and lists the services.
- `oh_pps_methodology()` — annual Medicare Economic Index adjustment, new-site rules, the ceiling at 120% of the statewide 60th percentile, and the rule's effective and review dates.
Every response carries `source`, `data_as_of` (the rule's effective date) and a note that per-clinic amounts are not public. A source that cannot be read raises an error that says so; it is never returned as an empty result.
## Auth
Keyless.
## Data sources
- Ohio Department of Medicaid, FQHC and RHC PPS rule (Ohio Administrative Code Chapter 5160-28), as published by the Ohio Legislative Service Commission. Read live on each call; nothing is stored.
Demand: one operator asked for Ohio per-clinic rates (fleet #4345). Ohio's state plan describes PVPAs as specific to a service site and available to providers through the state claims portal; no public per-clinic table was found. A public-records request to the Department is an option nobody has sent.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"oh-medicaid-rates": {
"url": "https://gateway.pipeworx.io/oh-medicaid-rates/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/oh-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 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/oh_fqhc_pvpa_addons \
-H 'Content-Type: application/json' \
-d '{"service":"dental"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/oh_fqhc_pvpa_addons`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-oh-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/oh-medicaid-rates/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"oh-medicaid-rates": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-oh-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 Oh 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