Brazil Law
by pipeworx-io
README.md
# @pipeworx/brazil-law
Brazilian federal legislation (leis, leis complementares, decretos-lei,
decretos, medidas provisórias, emendas constitucionais, decretos legislativos):
find a norm, then read its metadata, the later norms recorded as revoking or
amending it, and its consolidated text, whole or one article at a time.
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
- `br_law_search(query?, type?, number?, year?, year_from?, year_to?)` — find a
norm by type + number + year (for example `LEI` 13709 2018), or by a
Portuguese keyword matched against the title line, summary and popular name
over a window of years (default: the last 8; at most 15 per call; the
response says which years were scanned). Returns the norm id, title, summary
line and signature date.
- `br_law_get(norm | type+number+year, article?, max_chars?)` — one norm
(`LEI-13709-2018-08-14`, or the numeric code): title, summary, Diário Oficial
publication, the source's status marker, the later norms it records as
revoking, amending or regulating the norm, and the consolidated text.
`article` (`"52"`) returns one article with all its paragraphs and items as
currently in force. Unknown norms return `found:false` with a reason.
## Auth
Keyless.
## Data sources
- Brazil, Federal Senate and National Congress, federal legislation database
and consolidated norms portal — norm metadata, amendment and revocation
records, and consolidated text.
Status is reported as the source states it: `situacao` (`R` when the source
marks the whole norm revoked, absent otherwise), `portal_legal_force` where the
portal gives one, and the list of later norms recorded as revoking, amending or
regulating the norm. Nothing is derived from those notes, and absence of a
marker is not proof a provision is in force. `data_as_of` is the date of the
live read. Text comes from the portal's structured consolidated version; older
acts and many decrees have none, and then `text` is null with an
`empty_reason`. Keyword search scans a window of years because the source
lists norms by identification, not by words; widen the window to look earlier.
Constitution of 1988 text is not included. Nothing is stored; every call reads
the publisher live.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"brazil-law": {
"url": "https://gateway.pipeworx.io/brazil-law/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/brazil-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/br_law_search \
-H 'Content-Type: application/json' \
-d '{"query":"proteção de dados pessoais","year_from":2016,"year_to":2020}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/br_law_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-brazil-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/brazil-law/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"brazil-law": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-brazil-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 Brazil 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