Chile Law
by pipeworx-io
README.md
# @pipeworx/chile-law
Chilean national legislation from the Library of the National Congress (Ley
Chile): search laws, codes, decrees with force of law, decrees and resolutions
by Spanish words or number, then read a norm's current consolidated text, whole
or one article at a time, with its Diario Oficial citation and in-force status.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1905+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `cl_law_search(query, sort?, exact?, page?)` — find norms by words or number
(for example `ley 19628`, `protección de la vida privada`). Returns id_norma,
type and number, title, issuing ministry, promulgation/publication dates, an
in-force flag and a link. Ten per page; sort by relevance (default), newest
or oldest. Relevance is the publisher's own and is loose for word queries; a
number query (`ley 19628`) puts that law first.
- `cl_law_get(id_norma | law_number, article?, transitory?, occurrence?, max_chars?)`
— one norm by id_norma (from search) or, for laws, by number. Returns type,
number, title, issuing body, dates, citation, repealed flag, subject terms
and the text. `article` (`"1"`, `"4 bis"`, `"1 transitorio"`) returns one
article with its own repeal flag and version date; codes that embed several
texts repeat article numbers, so `occurrence` picks among them. Unknown ids
return `found:false` with a reason.
## Auth
Keyless.
## Data sources
- Chile, Biblioteca del Congreso Nacional, Ley Chile legislation database —
norm records and consolidated texts.
Text is Spanish, as consolidated by the Library; the Diario Oficial text is the
authentic one. `data_as_of` is the date of the live read; `text_version_date`
is the date the consolidated version was last updated when the database gives
one (some codes carry no version date). Read live on each call; nothing is
copied. `in_force` in search reflects whether the database records a repeal
date; deferred-effect provisions are not modelled. A search with no match
returns `empty_reason`, not an empty success.
A whole code is large (the Civil Code is about 3 MB of XML), so prefer
`article` for codes; the unfiltered text is capped at `max_chars`.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"chile-law": {
"url": "https://gateway.pipeworx.io/chile-law/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/chile-law/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:
```json
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
```
Both URLs reach the same gateway and the same 1905+ 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
```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/cl_law_search \
-H 'Content-Type: application/json' \
-d '{"query":"ley 19628"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/cl_law_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-chile-law` 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/chile-law/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"chile-law": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-chile-law"]
}
}
}
```
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 Chile Law data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues