@pipeworx/canada-law
by pipeworx-io
README.md
# @pipeworx/canada-law
Canadian federal Acts and regulations from the Department of Justice Canada's
Consolidated Acts and Regulations, in English or French: search by title, then
read an Act or regulation, its stated status and citation, and its consolidated
text, whole or one section at a time. Federal law only; provincial and
territorial law is a different publisher.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1957+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `ca_law_search(query, lang?, type?, page?)` — find titles by words in the
name. `lang` is `en` (default) or `fr`. `type` is `act` (default),
`regulation` or `all` (`all` reads more title lists and is slower). Returns
id, title, type, citation and a link; 25 per page, `next_page` says whether
to continue. French titles are listed inverted ("Protection des
renseignements personnels, Loi sur la").
- `ca_law_get(id, lang?, section?, max_chars?)` — one Act or regulation:
title, citation, assent or registration date, the in-force status as the
source states it, last-amended date, the date the consolidation is current
to, and the text. `section` returns one section; otherwise the text is capped
at `max_chars` with a section list. Schedules are not addressable by section.
The source flags Acts as in force; it states no flag for regulations, so
their `status` is `null` with a `note` (nothing is derived).
## Auth
Keyless.
## Data sources
- Canada, Department of Justice, Consolidated Acts and Regulations (federal)
— the consolidated text of federal Acts and regulations, in both official
languages.
Consolidations are unofficial; the Statutes of Canada and the Canada Gazette
are the official texts. `data_as_of` is the date the consolidation is current
to when the call returns a text, otherwise the date of the live read. Read live
on each call; nothing is copied. A search or lookup that finds nothing returns
`empty_reason`, not an empty success.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"canada-law": {
"url": "https://gateway.pipeworx.io/canada-law/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/canada-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 1957+ 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/ca_law_search \
-H 'Content-Type: application/json' \
-d '{"query":"privacy","lang":"en"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/ca_law_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-canada-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/canada-law/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"canada-law": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-canada-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 Canada 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