# Colorado Code [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/pipeworx-io/mcp-colorado-code  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/colorado-code

## Description
Colorado Revised Statutes — state statutes by citation, topic, and title.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What Colorado Code MCP server does

The Colorado Code MCP server exposes Colorado Revised Statutes through three pack-specific tools: `co_statute`, `co_search`, and `co_titles`. It is intended for retrieving public statutory material rather than Lexis editorial content or case-law annotations.

`co_statute` looks up a section by citation, such as `18-3-102`, and can retrieve the current edition or supported historical editions. The returned section includes the statutory text, a `Source:` amendment-history line, and available `Cross references:` from the public statute files. Case-law annotations are excluded.

`co_search` searches the General Index for subjects such as landlord, security deposit, or concealed handgun. `co_titles` returns the title list with subject hints, which can help identify the relevant part of the code before requesting a section.

## How it works

The Colorado Code MCP server reads title-sized HTML files from the Colorado Office of Legislative Legal Services. Current statutes are stored one file per title, while archived editions are available by year. To extract a section, the implementation identifies the citation heading in the raw HTML and stops at the next section heading or the beginning of the annotations, whichever comes first.

Topic search uses the approximately 18 MB General Index for the current edition. Because the index is organized as a nested tree, matching includes a short window of lines before a citation-bearing entry. Short topics generally fit this approach better than long compound phrases.

The gateway endpoint also exposes shared Pipeworx meta-tools, including routing through `ask_pipeworx`. A local stdio installation exposes only the Colorado Code tools. Both use the same public source material.

## Setup and configuration

Connect an MCP client to `https://gateway.pipeworx.io/colorado-code/mcp` to use the scoped gateway endpoint. You can instead connect to `https://gateway.pipeworx.io/mcp`, which lists the broader Pipeworx gateway while still allowing `ask_pipeworx` to route questions across the catalog.

For local use, run `npx -y @pipeworx/mcp-colorado-code` as an stdio MCP server. This option does not require a Pipeworx account or a gateway round trip. The package can be added to an MCP client with a command-and-arguments configuration.

The tools can also be called over HTTP. For example, send a JSON request to `/v1/tools/co_statute` with a section such as `18-3-102`. The service is keyless, and the README states that the first calls do not require an account.

## Tools and capabilities

- `co_statute`: Retrieve a statute by citation and request supported historical editions.
- `co_search`: Find statute references through the General Index by topic.
- `co_titles`: Browse Colorado code titles and subject hints.
- Historical lookup: Use the current edition or editions from 2000 through 2024.
- Amendment context: Read the available `Source:` history returned with a section.

## Limitations and notes

The Colorado Code MCP server does not support the 2025 edition because its file format is explicitly declined rather than risk an incorrect parse. Current and 2000–2024 formats are supported, although future source-format changes could cause sections to stop matching until the parser is updated.

Historical `cross_references` are usually unavailable for 2000–2024 editions because those references occur inside the annotation area that the parser excludes. Topic search can also become noisy with long phrases because it relies on nearby index lines rather than full hierarchy reconstruction.

This is an independent, unofficial integration. The source files are public Colorado statutes, but the integration is not affiliated with, endorsed by, or published by the upstream provider. It belongs in the Legal category and should not be treated as a substitute for professional legal advice or an authoritative legal publisher.

_Full upstream README: https://allmcps.com/mcp/colorado-code/readme_