Oklahoma Code

What the Oklahoma Code MCP server does

The Oklahoma Code MCP server exposes Oklahoma statutes as MCP tools for citation lookup, topic research, title discovery, amendment review, and historical-version retrieval. Its source is the Oklahoma State Courts Network (OSCN), which publishes the Oklahoma Statutes Citationized as server-rendered HTML.

The Oklahoma Code MCP server is keyless and does not require an account for its documented hosted requests. It is an independent, unofficial integration and is not affiliated with, endorsed by, or published by the upstream provider.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/oklahoma-code/mcp. A local package is also available through npm and communicates over stdin and stdout. The hosted endpoint includes the Oklahoma-specific tools plus shared Pipeworx gateway tools; the local process exposes only this pack's tools.

The integration resolves citations through OSCN title directories, then retrieves the requested section. Supported citation forms include formats such as 21-701.7, 21 O.S. § 701.7, and Title 21, Section 701.7. Lettered titles must retain their suffix, such as 10A-1.

OSCN's full-text search examines statutory body text rather than headings alone. This allows a query such as “landlord” to find relevant provisions even when the term is absent from a section heading. Amended sections include amendment history and links to superseded documents. A historical version can be requested by passing its OSCN citeid to the statute tool.

Setup and configuration

For an MCP client, add the hosted endpoint as a remote server:

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

For local stdio use, configure the npm package with npx:

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

No API key or environment variable is documented. The hosted service can also be called over HTTP, for example by posting a tool request to https://gateway.pipeworx.io/v1/tools/ok_statute.

Tools and capabilities

The Oklahoma Code MCP server defines three primary tools:

• ok_statute(citation, version_citeid?) returns a section's full text, chapter breadcrumb, “Cite as” line, amendment history, and available historical versions. Supplying version_citeid retrieves that specific prior text.
• ok_search(query, limit?) searches statutory body text and returns matching citations, headings, effective dates, and relevance information.
• ok_titles() lists all 94 titles with their official names, helping route a subject to an appropriate title.

The Oklahoma Code MCP server is therefore suited to legal research workflows that need both current statutory language and the text that applied before an amendment. It can also help agents identify the relevant title before performing a more focused lookup.

Limitations and notes

This integration exposes Oklahoma statutes, not a general legal database. The README identifies OSCN as the underlying source and notes that the integration is unofficial. Hosted connections include shared Pipeworx meta-tools, so their tool list is larger than the three Oklahoma-specific tools. The local stdio mode does not include those shared tools or cross-catalog routing.

The source pages are plain HTML and keyless, but the server depends on OSCN's published structure and availability. The README reports currency through the 2025 legislative session and at least one 2026-effective amendment; users should verify the source and applicable law for matters requiring authoritative or current legal advice.