Skip to main content
Glama

@pipeworx/az-medicaid-rates

Arizona Medicaid FQHC (federally qualified health center) and rural health clinic (RHC) per-visit rates, by clinic or health centre, one table per federal fiscal year (FY2022 to FY2027): the PPS rate in dollars, the program, the methodology (APM or BIPA, from FY2025) and the effective period. From the Arizona Health Care Cost Containment System (AHCCCS), fee-for-service rate tables.

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

Built on a Bruce ask ("more states", 2026-11-16) under the supply-creates-demand ruling; there is no measured demand for this state yet.

Tools

  • az_clinic_rates(provider?, program?, period?, methodology?, out_of_state?, limit?) — rates by clinic name fragment. Defaults to the newest fiscal year (FY2027: 2026-10-01 to 2027-09-30); period: "all" returns every year with the change from the prior year and any footnote. An unmatched filter returns the nearest provider names or the valid values, never a bare empty.

  • az_rate_summary(program?, period?, group_by?) — what each fiscal-year table is (effective period, version date, clinic counts), min/median/max/mean rate, optionally grouped by fiscal year, program or methodology.

Related MCP server: @pipeworx/fl-medicaid-rates

Auth

Keyless.

Data sources

  • Arizona Health Care Cost Containment System (AHCCCS), fee-for-service FQHC and RHC rate tables — one table per federal fiscal year, October 1 to September 30. Public, no account.

Things worth knowing:

  • The grain is the clinic or health centre, not the site and not the procedure code. AHCCCS lists one rate per billing organisation ("El Rio Health Center", "Banner Health Page"). The tables carry no NPI, address or city, so there are no such filters. AHCCCS fee schedules by procedure code are a different publication and are not in this pack.

  • Rates are PPS per-visit encounter rates. From FY2025 each rate is marked APM (alternative payment methodology) or BIPA; FY2022 to FY2024 carry no methodology (methodology: null).

  • Footnotes mark mid-year splits. Some older tables give two rates for one year with dates (for example Marana in FY2024: $271.41 to 2024-03-30, $284.26 from 2024-04-01). The published figure is the row's per_visit_rate; the dated split is in footnote.

  • Out-of-state clinics are listed. AHCCCS includes a few clinics in Utah, California, New Mexico and other states that treat Arizona Medicaid members; out_of_state_state carries the state, taken from the name.

  • prior_year_rate pairs an exact name match in the previous fiscal year; it is null when a name changed ("North Country Community Health Center" became "North Country HealthCare Inc.") or the clinic is new. Names are as printed each year and are not merged.

  • Tables are revised during the year (FY2027 carries "Revised 10/5/26 to add new providers"); table_version on each row quotes the publisher's own version line.

  • Organisations only. Any row whose name reads as a person is left out when the table is stored and counted in individual_rows_dropped (0 today: the tables list health centres and clinics). The rule is in src/individuals.ts.

  • Fee-for-service rates only: managed-care plans may pay under their own contracts.

  • Every response carries data_as_of (the newest table's version date), captured_at and the source.

Stored data and refresh

AHCCCS publishes these as small yearly workbooks with no query interface, so every listed year is read by scripts/bake-index.mjs into src/az-rates-data.ts (295 rows, about 47 KB), registered in workers/gateway/src/pack-baked-indexes.json; the deploy uploads it to KV and the gateway injects it on the first call into this pack, so nothing is evaluated at module scope. Refresh with node mcps/az-medicaid-rates/scripts/bake-index.mjs: it discovers the workbooks from the program page, reads each with the in-repo reader, and rewrites the module in place. It refuses a changed title, header or effective-date row, a file whose name and effective date disagree on the fiscal year, a non-positive rate, an unexpected row, a table under its row floor, a repeated provider, or a total more than 10% under the module on disk. AHCCCS posts a new workbook each October; data_as_of says which version is held.

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/az-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 2006+ 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/az_clinic_rates \
  -H 'Content-Type: application/json' \
  -d '{"provider":"El Rio","period":"all","limit":6}'

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

Run it from npm

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

{
  "mcpServers": {
    "az-medicaid-rates": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-az-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 Az 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
      Enables querying California manufacturers' required list-price (WAC) increase disclosures, their five-year WAC histories, and new-drug launch-price reports filed under the HCAI Cost Transparency Rx program. Keyless access supports filtering by drug, manufacturer, NDC, and year (2019–present) across both current and archived annual datasets.
      81 npm
      MIT
    • 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
      A
      quality
      B
      maintenance
      Enables assistants to compute 2026 health-insurance subsidy amounts, federal poverty level thresholds, 400% FPL cliff effects, and excess advance credit repayment caps using primary-source rules. It returns structured JSON plus plain-English summaries with sourcing and as-of dates.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search federally funded community health center (FQHC) and FQHC look-alike sites by name, state, city, ZIP, or county, or by distance within a radius of a ZIP, city, or coordinate pair, returning address, phone, website, weekly hours, operating health center, county, NPI, and Medicare billing number. Results flag school-based and administrative-only sites, report data-as-of dates, and make not-found answers explicit with near-name non-matches.
      MIT