npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pipeworx/mcp-georgia-code

v0.2.1

Published

Official Code of Georgia Annotated (O.C.G.A.) — Georgia state statutes by citation, topic search, historical versions, and amendment/enactment history.

Readme

@pipeworx/georgia-code

Official Code of Georgia Annotated (O.C.G.A.) — Georgia state statutes by citation and by topic search, with historical versions and legislative/amendment history.

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

Tools

  • ga_code_section(citation) — the current text of a Code section by citation (any natural form: "16-5-1", "O.C.G.A. § 44-7-34", "Ga. Code Ann. § 16-5-1", "Title 16, Chapter 5, Section 1"). Returns status (active/repealed/reserved), the legislative history line (the Acts that enacted and amended it), editor's notes and cross references, and every stored historical version when a section has more than one — e.g. a delayed effective date.
  • ga_code_search(query, limit?, headings_only?) — full-text topic search over the Code's body text and catchlines. Returns ranked citations with a highlighted snippet; pass the citation to ga_code_section for the full text.

Auth

Keyless. No signup, no key, on either side of the call.

Data sources

Why this isn't a Lexis call. Georgia's own publishing arrangement — the Code Revision Commission, for the General Assembly (legis.ga.gov) — contracts the OCGA's online text out to LexisNexis (advance.lexis.com), which is a login-shaped surface this pack does not touch. The statutory text itself carries no copyright: Georgia v. Public.Resource.Org, Inc., 590 U.S. 255 (2020) held the OCGA (text and annotations) is an edict of government. Georgia Commons — an independent project of Georgia Civic Data, explicitly "not affiliated with, operated by, or endorsed by the State of Georgia" — publishes that public-domain text as a CC0-1.0, keyless, no-signup JSON API, current through the 2025 Regular Session, extracted from the state's own officially released volumes (each record's source_link points back to the original legis.ga.gov PDF). This pack calls that API live, per request.

Four capabilities, one response shape. GET /api/code/sections/{citation} carries all four at once:

  • citation lookup — the top-level fields (catchline, status, heading_path).
  • topic/full-text search — the separate /search endpoint.
  • historical version — the versions[] array; version_count is 1 for most sections and >1 for ones with a delayed or superseded effective date.
  • amendments/history — the history string (Acts that enacted/amended the section) and notes (editor's notes, cross references, law review articles).

Rate limits (documented, no key): 120 requests/min, 2,000/hr, shared across Georgia Commons' bills/opinions/code collections. One request per tool call here; a 429 carries Retry-After.

Citation parsing is upstream's job, not ours. The API itself accepts "16-5-1", "O.C.G.A. § 16-5-1", "Ga. Code Ann. § 16-5-1", "Code Section 16-5-1", and "Title 16, Chapter 5, Section 1" — this pack passes the caller's string through URL-encoded rather than re-parsing it, and lets the upstream's own 404 (which names the nearest sections and the accepted forms) do the error handling.

Scope note. The upstream API also serves General Assembly bills, Supreme Court of Georgia opinions, and both the Georgia and U.S. constitutions under the same /api/{collection} grammar — out of scope for this pack, which is statutes only.

Quick Start

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

{
  "mcpServers": {
    "georgia-code": {
      "url": "https://gateway.pipeworx.io/georgia-code/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/georgia-code/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 1865+ 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/ga_code_section \
  -H 'Content-Type: application/json' \
  -d '{"citation":"16-5-1"}'

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

Run it from npm

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

{
  "mcpServers": {
    "georgia-code": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-georgia-code"]
    }
  }
}

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 Georgia Code data" })

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

More

License

MIT