New Jersey Code MCP server

@pipeworx/new-jersey-code

New Jersey Statutes (N.J.S.A.) by citation — with amendment history where the source lists one — plus full-text topic search. Keyless.

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

Tools

(e.g. "2C:11-3", "39:4-50", "46:8-19"), with its amendment_history line parsed out when the section has been amended.

• njstatutesection(section) — full text of one N.J.S.A. section by citation

("security deposit interest", "landlord grounds for eviction"); returns ranked sections with citation + heading where the hit title parses as one.

• njstatutesearch(query, limit?) — full-text search by topic/keyword

Auth

Keyless.

Data sources

Legislature's statute-viewer subdomain (NXT4/Folio document publishing, IIS-hosted). This is a DIFFERENT legislature subdomain than the njleg.state.nj.us Next.js site most links point at — that one is bills/session focused and does not itself host statute text.

• — the New Jersey

Shape of this source, because it is not a REST API

The viewer is session-cookie based, not a clean lookup-by-id endpoint:

its hit list as plain server-side HTML (title rows) — no JS execution needed to read it.

1. f=xhitlist is a full-text search. It sets a session cookie and renders

(trailing space, inside the search). That trailing space is load-bearing: an unquoted citation free-text-matches thousands of sections that merely contain the same digits, and even the quoted phrase WITHOUT the trailing space still matches dotted/lettered children ("39:4-50.17", "39:4-50c") because "50" is a literal prefix of "50.17". The space forces the match onto a token boundary.

1. A citation lookup queries the EXACT quoted phrase " "

with the search's session cookie, redirect: manual) 302s to the document's permanent, COOKIE-FREE path: /nxt/gateway.dll/statutes///.

1. Each hit's href is an f=hitdoc$hitdoc_bm=... link. Resolving it (GET,

1. That path is fetched directly for the actual statutory text.

This is a session-cookie flow across two ordinary GETs — not the ASP.NET __VIEWSTATE postback pattern (there is no postback form anywhere in it), and it carries no CAPTCHA or other anti-bot wall. It has been reachable from a Cloudflare Worker at the rate one caller generates; it has not been load tested.

Amendment history is free; a prior point-in-time version is not

Every amended section's text ends with a trailing amended 1979, c.178, s.21; ...; 2017, c.150. (or, for a section's original enactment, L., c., s..) line. njstatutesection parses that into amendmenthistory rather than leaving it buried in text — an original, never-amended section simply has none (null). This source does NOT expose a point-in-time/prior-version snapshot of a section; njstatutesection says so explicitly in its historicalversion field rather than silently omitting the capability.

Topic search quality

njstatutesearch ANDs every word in the query (this is the upstream engine's own behaviour, not something this pack adds) — a long sentence over-narrows; a few plain words ("landlord grounds for eviction") works better than a full question.

Quick Start

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

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

What this endpoint actually serves

Shortened. The full README is on GitHub.