@pipeworx/fl-medicaid-rates

Florida Medicaid reimbursement rates by provider and rate semester: FQHC and rural health clinic per-visit encounter rates, nursing home, skilled nursing unit, swing bed, hospice and hospital rates, with statewide min/median/max and the effective date.

Part of Pipeworx — an MCP gateway connecting AI agents to 1881+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• fl_fqhc_rates(period?, provider?, limit?) — Florida Medicaid (not Medicare) FQHC per-visit PPS encounter rate for each clinic in a semester, with statewide min/median/max/mean.

• fl_medicaid_rates(schedule, period?, provider?, limit?) — the same shape for any schedule: fqhc, rhc, pb_rhc, snu, swing_bed, hospice_level_of_care, hospice_room_board, nursing_home, hospital.

• fl_rate_periods(schedule?) — which effective periods are published for each schedule.

Related MCP server: Medicare MCP Server

Auth

Keyless.

Data sources

• Florida Agency for Health Care Administration (AHCA), Medicaid cost reimbursement rate schedules — the per-semester provider rate tables the agency publishes for each rate type. Public, no account.

Calls are answered from a stored copy of the agency's tables (see Stored copy below); a semester the copy does not list, or a copy older than 45 days, sends the call to the agency instead, so new semesters appear without a code change. Nothing is bundled in the gateway.

Things worth knowing:

• The agency states that published rates are those in effect on the first day of the semester and are not updated for later revisions to an individual provider's cost data. Responses repeat this.

• Effective dates come from the publication's naming, which is not uniform across rate types; undated entries are listed as undated.

• FQHC/RHC tables carry one rate column whose header embeds the MEI percentage for the year. Rate columns are detected by being numeric and not an identifier, so a header change flows through rather than breaking.

• The nursing home workbook has more than one sheet; rows carry a Sheet column.

• Provider number is a string in the FQHC/RHC tables (leading zeros) and a number in others; the provider filter matches the digits either way.

• hospital is the state mental health hospital per diem table only (3 hospitals). The agency's own page says community-hospital inpatient is paid by DRG (since July 2013) and outpatient by EAPG (since July 2017) and posts no per diem for them; only the state mental health hospitals still get one. A community hospital is not missing from the data, it is not in this schedule. Responses carry a scope line saying so. snu is the complete hospital-based skilled nursing unit table the agency posts (3 units in October 2026).

• A 0 in a rate cell is the agency's "no rate for this service" (the hospital table shows 0 for outpatient on every state hospital). It is returned as null, listed in null_rate_cells/null_rate_note, and left out of statewide, so no statewide mean is computed over zeros.

• Rates are rounded to the cent (some workbooks store float noise such as 159.18499999999997).

• A partial read is refused, not answered: the reader counts the cells it read against the cells in the sheet, refuses a workbook with a sheet it could not open or a data sheet with no header row, and refuses a latest table with fewer provider rows than a per-schedule floor.

• Rate-letter and calculation-sheet PDFs, and the reimbursement plans, are not parsed.

Stored copy and data_as_of (fleet #3614)

The agency's firewall refuses our egress by REGION, not by caller: over one measured window every call routed through Hong Kong, Singapore or Shanghai was refused (467 refused against 25 served) while US callers were served. A cache cannot help a region that never gets a first success, and the rates change about twice a year, so the parsed tables are stored in the shared R2 store (medicaid-rates/fl/: a manifest plus one object per workbook, 95 objects and about 2.8 MB for 9 schedules). The gateway hands the pack its R2 binding; nothing is loaded at module scope and nothing is in git.

• A call is answered from the copy with no request to the agency. The response carries served_from: "stored-copy", retrieved_at (when that workbook was read from the agency), copy_refreshed_at (when the refresh last checked the whole set), and data_as_of (the rate semester's effective date; for fl_rate_periods, the newest semester listed).

• A copy older than 45 days is not trusted to be current: the agency is asked first, and the copy answers only if that fails, with stale_copy: true, stale_note and upstream_refused. A period the copy does not list also goes to the agency, and its failure names what the copy holds.

• With no R2 binding (a standalone install) the pack reads the agency live, as before, with its one-day cache, its ten-minute refused-region pause and an earlier-copy fallback labelled upstream_refused.

• The same parser (src/parse.ts, src/xlsx.ts) writes the copy and reads the agency live, and the same per-schedule row floors apply to a stored latest table, so a partial read is refused either way.

Refresh

node mcps/fl-medicaid-rates/scripts/refresh-rates.mjs              # read the agency, write R2 (changed files only)
node mcps/fl-medicaid-rates/scripts/refresh-rates.mjs --dry-run    # read, parse, report; write nothing
node mcps/fl-medicaid-rates/scripts/refresh-rates.mjs --out <dir>  # write to a directory instead of R2
node mcps/fl-medicaid-rates/scripts/refresh-rates.mjs --only fqhc,rhc --r2-mode wrangler

The unattended refresh is the scheduled Worker workers/fl-rates-refresh (pinned to a US region; a daily tick that acts once the copy is 25 days old and retries on the next tick if a run fails). The script above is the operator's route for a manual or dry run, or if that Worker is down; both call the same loop (src/refresh.ts). The monitor's _fl_rates_copy check goes red at 38 days; the pack stops trusting the copy at 45. Either route runs from the US only (it checks the country and refuses otherwise, because a refresh from a refused region would store nothing and still exit 0). Exit 0 only when every schedule was read and parsed, its latest table cleared the row floor, and the manifest landed; any failure leaves the previous manifest, so copy_refreshed_at never claims a check that did not happen. A workbook whose content is unchanged keeps its object and its retrieved_at. R2 writes use wrangler r2 object put --remote under the operator login.

Licence: the tables are Florida public records (Fla. Stat. ch. 119), published on the agency's site with no reuse restriction stated on the pages; the copy republishes the agency's figures unchanged and names the agency.

Live-read behaviour (no stored copy, or a copy that cannot answer)

Each file is read from the agency at most once a day per region and kept; retrieved_at is when the agency was last actually read and from_cache says whether this answer used a stored copy. If the agency refuses a fresh read and an earlier copy exists, the earlier copy answers and the response carries upstream_refused with the agency's reason. If it refuses and there is no earlier copy, the call fails and says why. The agency's firewall refuses requests from some regions; the pack does not disguise itself or rotate addresses.

After the agency's firewall refuses a data centre, that data centre does not contact the agency again for ten minutes (the call fails at once and says so), so a caller retrying in a loop does not add load to the agency. A timeout or a 5xx never starts that pause.

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/fl-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 1881+ 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/fl_fqhc_rates \
  -H 'Content-Type: application/json' \
  -d '{"period":"October 2025","provider":"Escambia","limit":5}'

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

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-fl-medicaid-rates

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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 Fl Medicaid Rates data" })

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

More

• Docs and guides

• pipeworx.io

License

MIT