Skip to main content
Glama

@pipeworx/in-medicaid-rates

Indiana Medicaid payment rates for federally qualified health centers (FQHC) and rural health clinics (RHC), per provider name: one per-visit rate per clinic, effective January 1, 2026, from the Indiana Family and Social Services Administration, Indiana Health Coverage Programs (IHCP).

Part of Pipeworx — 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

  • in_clinic_rates(program?, provider?, period?, limit?) — per-provider payment rates. Filter by program and by clinic-name fragment. Each row carries the rate rounded to the cent, the unrounded published value, the effective date and data_as_of. An unmatched name returns the nearest provider names and says what the table does not hold.

  • in_rate_periods(program?) — the periods available, provider counts and the lowest, median and highest rate per program.

Related MCP server: az-medicaid-rates

Auth

Keyless.

Data sources

  • Indiana Family and Social Services Administration, Indiana Health Coverage Programs (IHCP), FQHC and RHC payment rates — the two payment-rate tables the IHCP publishes in its fee-schedule listings. Public, no account.

Things worth knowing:

  • Lookup is by name only. The tables carry a provider name and a rate: no NPI, no Medicaid provider id, no address, city or county, and no per-row date. A place name matches only when it appears inside a provider's name. The pack does not invent identifiers.

  • One period. The only date is the table's own title line ("Effective January 1, 2026"). Earlier years' tables are not in the pack, so in_rate_periods lists one period per program. Every response carries data_as_of.

  • The rate is published as an unrounded decimal (for example 266.68227104999994). rate is that value rounded to the cent; rate_published is the value exactly as published.

  • The tables are fee-for-service payment rates; they say nothing about what managed-care plans pay.

  • Organisations only: the tables list clinics, and one rural health clinic enrolled under a physician's own name is left out when the data is read. The count is in individual_rows_dropped on every response.

  • Built on request rather than from measured demand; no caller has asked for Indiana yet.

Stored data and refresh

The two tables are small (about 180 rows, 26 KB). They are read from the IHCP by scripts/bake-index.mjs into src/in-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/in-medicaid-rates/scripts/bake-index.mjs re-reads both files and rewrites the module in place; it refuses a file whose title block or header changes, that shrinks below its floor, or that carries a non-numeric rate or a repeated name. The IHCP re-issues the tables about once a year, effective January 1.

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/in-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:

{
  "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

curl -X POST https://gateway.pipeworx.io/v1/tools/in_clinic_rates \
  -H 'Content-Type: application/json' \
  -d '{"program":"RHC","provider":"Fast Pace","limit":3}'

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

Run it from npm

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

{
  "mcpServers": {
    "in-medicaid-rates": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-in-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 In Medicaid Rates data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides Florida Medicaid reimbursement rate data from AHCA cost reimbursement schedules — FQHC and rural health clinic per-visit encounter rates, nursing home, skilled nursing unit, swing bed, hospice, and state mental health hospital per diem rates — queryable by provider and rate semester with statewide min/median/max and effective dates.
      190 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Arizona Medicaid (AHCCCS) fee-for-service FQHC and rural health clinic per-visit PPS rates by clinic name for federal fiscal years FY2022–FY2027, with program, methodology, footnoted mid-year splits and year-over-year comparisons. Also summarizes each fiscal year's table with min/median/max/mean rates and clinic counts, optionally grouped by program or methodology.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying California Federally Qualified Health Center wrap payment counts and managed care encounter match figures by health center, NPI, or calendar year, including statewide summaries and rankings. Data covers 2021–2023 and returns counts and match percentages, not dollar amounts.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying and comparing per-center, per-fiscal-year FQHC Medicare cost report figures, including visits, allowable costs, cost per visit, payer shares, and state-level summaries from CMS data.
      MIT