Alabama Code MCP server

@pipeworx/alabama-code

Code of Alabama 1975 (Alabama state statutes) — full section text by citation, real full-text topic search, and amendment history.

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

Tools

(e.g. "13A-6-2", murder), with the section title, the Legislature's own amendment-history citation list (amendmenthistory), repealed/transferred disposition, previous/next-section neighbors, and — when an Act has already been enacted but is not yet in force — a forward-looking pendingversion carrying its future effective date and text.

• al_statute(citation) — full current text of one Code of Alabama section

body text (e.g. "landlord", "concealed pistol permit"), run live against the Alabama Legislature's own search index. Unlike several sibling state-code packs, this is not limited to captions/catchlines.

• al_search(query, limit?) — REAL full-text search over actual section

Auth

Keyless.

Data sources

Legislature's own public GraphQL API, confirmed keyless and reachable from Cloudflare Worker egress (edge-probed, not just laptop-tested). Both tools call it live, per request; nothing is baked.

• https://alison.legislature.state.al.us/graphql — the Alabama

(and, when present, pending-future) text, title, and amendment-history string, plus codeOfAlabamaNeighbors for previous/next citation.

• query codeOfAlabamaSection($displayId: String!) — one section's current

full-text search (fullTextQuery argument) over section body content, not just titles; returns a count of total matches independent of limit.

• query searchCodeOfAlabama($query: String!, $limit: Int, $offset: Int) —

Trap avoided: there are TWO graphql-shaped hosts, only one of which serves statute data. cms.alison.legislature.state.al.us also answers POST /graphql (it serves the site's marketing/CMS content — page copy, the logo asset, etc.) and returns a plausible 400 (Cannot query field "codesOfAlabama" on type "Query") for every statute query, because it's a different schema on a different service, not an error about this pack's query shape. The real statute API lives on the main site's own domain, alison.legislature.state.al.us/graphql (found in a plain inline URL reference inside the page's own HTML — not something a build-config guess would find — and confirmed by pulling the query text for codeOfAlabamaSection/searchCodeOfAlabama straight out of the Next.js chunk bundle that defines them).

Trap avoided: the GraphQL endpoint answers HTTP 200 on a query-level error. A malformed or schema-mismatched query comes back as a 200 with a body-level errors array — not a 4xx. alstatute/alsearch read the body and check for errors explicitly and throw a LOUD error naming the GraphQL message; neither tool ever reshapes that into found: false.

Capabilities — three available, one is forward-looking instead of backward

Shortened. The full README is on GitHub.