colombia-law
by pipeworx-io
README.md
# @pipeworx/colombia-law
Colombian national legislation as compiled by the Senate of the Republic
("Leyes desde 1992"): search laws, decrees, codes and the Constitution, and the
Constitutional Court rulings that review them, then read a document's text,
whole or one article at a time, with the validity notes the compilation records
(repealed, amended, declared constitutional).
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
- `co_law_search(query?, type?, number?, year?)` — find documents by Spanish
words, by type + number + year, or both (for example `ley` 1581 2012, or
"datos personales"). Returns doc_id, kind (law, decree, code, or a
Constitutional Court ruling), relevance score and a snippet; the first ten by
relevance, with the total found.
- `co_law_get(doc_id | type+number+year, article?, max_chars?)` — one document
(`ley_1581_2012`; `type` is `ley` or `decreto`): title, date, Diario Oficial
citation, issuing body, subject line, the validity notes, a derived repeal
status and the text. `article` (`"15"`) returns one article with its own
validity notes and a repealed flag; large laws are split into parts and the
lookup follows them. Unknown ids return `found:false` with a reason.
## Auth
Keyless.
## Data sources
- Colombia, Senado de la República, "Leyes desde 1992" compilation (validity
notes and constitutional-review rulings) — law, decree and code text.
Status is derived from the compilation's own notes written in angle brackets (for example
"Artículo derogado por ..."): `repealed`, `partially_repealed_or_amended` or
`no_repeal_noted`, with `articles_noted_repealed` out of the articles read. It is
a reading aid, not legal advice, and `no_repeal_noted` means the compilation
records no repeal, not that none exists. `data_as_of` is the date of the live
read. The documents are served over plain HTTP by the publisher (its HTTPS
endpoint does not answer reliably). The search needs a session cookie, which
the pack obtains per call; nothing is stored. A search with no match returns
`empty_reason`, not an empty success. Coverage is laws from 1992 plus the
codes and the Constitution; earlier laws and most ministerial acts are not
included.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"colombia-law": {
"url": "https://gateway.pipeworx.io/colombia-law/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/colombia-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/co_law_search \
-H 'Content-Type: application/json' \
-d '{"query":"datos personales","type":"ley"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/co_law_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-colombia-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/colombia-law/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"colombia-law": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-colombia-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 Colombia 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