CanLII

io.github.Vaquill-AIv0.1.0更新於 Oct 9, 2026

MCP for CanLII: Canadian case law and legislation metadata (federal, provincial, territorial).

已驗證Streamable HTTP可網頁執行Web Search & Scraping Knowledge & Memory

概覽

AI 產生的概覽

讓助理透過 CanLII API 依法院、法庭或法規資料庫查詢加拿大判例法與立法中介資料。

功能: 封裝 CanLII 加拿大法律資訊 API，提供列出法院與法庭、瀏覽指定資料庫中的判決，以及取得特定案件中介資料（標題、引註、日期、關鍵字）的工具。也可列出法規與條例資料庫、瀏覽立法，並回傳引註關係，例如某案引用的案件、引用該案的案件及其引用的立法。此 API 僅提供中介資料，不提供全文。
適用情境: 當助理需要查找或引用加拿大聯邦、省或地區的判例法與立法時適用，例如定位某判決、核對其引註，或追蹤哪些案件引用了它。若需要判決或法規全文，則不適用。
執行需求: 可使用託管的 streamable HTTP 端點，也可自行部署（Node.js 22+、Docker 或 Cloudflare Workers）。需要 CanLII API 金鑰，依請求透過 X-CanLII-Token 標頭或 token URL 參數提供，或在 stdio 與自架單租戶模式下透過 CANLII_API 環境變數提供。選用的 MCP_AUTH_TOKEN 承載權杖僅用於自架部署。

安裝前請注意

CanLII API 金鑰屬於機密；URL 參數形式會把金鑰放入 URL，因此優先使用標頭形式。每次呼叫都計入你自己的 CanLII 配額，限制為每金鑰同時 1 個請求、每秒 2 個、每天 5,000 個。伺服器聲明不儲存金鑰，僅為限流保留雜湊。公開託管端點不需要承載權杖，任何知道該 URL 的人都能存取。

安裝

在 SourceWeft 中

開啟儀表板中的 CanLII，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "canlii-mcp": {
      "type": "http",
      "url": "https://canlii-mcp.vaquill.ai/mcp"
    }
  }
}

README

canlii-mcp

An MCP (Model Context Protocol) server for the CanLII Canadian legal information API. Gives AI assistants access to Canadian case law and legislation metadata across all federal, provincial, and territorial jurisdictions.

Forked from tomilashy/canlii-mcp. This fork adds bring-your-own-key (BYOK) auth, a /health route, and a hosted endpoint at canlii-mcp.vaquill.ai. Tools are unchanged.

Note: The CanLII API provides metadata only — titles, citations, dates, keywords, and citation relationships. Full document text is not available through the API.

[Discord]

Use the hosted endpoint (no install)

The hosted instance is public. No Vaquill token is required. Provide your own CanLII key one of two ways:

Header (recommended, keeps the key out of the URL): X-CanLII-Token: <your_canlii_api_key>
URL parameter (simplest; works in header-less clients like the Claude Desktop connector UI and claude.ai web): append ?token=<your_canlii_api_key> to the URL:
```
https://canlii-mcp.vaquill.ai/mcp?token=YOUR_CANLII_API_KEY
```
```
https://canlii-mcp.vaquill.ai/mcp?token=YOUR_CANLII_API_KEY
```

Apply for a key via the CanLII API request form. The server never stores your key, and there is no server-side fallback key, so every call counts against your own CanLII quota.

Claude Desktop / Claude Code

json

{  "mcpServers": {    "canlii": {      "url": "https://canlii-mcp.vaquill.ai/mcp",      "headers": {        "X-CanLII-Token": "YOUR_CANLII_API_KEY"      }    }  }}

{  "mcpServers": {    "canlii": {      "url": "https://canlii-mcp.vaquill.ai/mcp",      "headers": {        "X-CanLII-Token": "YOUR_CANLII_API_KEY"      }    }  }}

Cursor / VS Code / Windsurf

Same pattern: any client supporting MCP streamable HTTP with custom headers works. For stdio-only clients use mcp-remote to proxy.

Authentication

Mode	Header	When
BYOK header (preferred)	`X-CanLII-Token: <key>`	Hosted / shared deployments
BYOK URL param	`?token=<key>` (or `?canlii_token=`)	Header-less clients: Claude Desktop connector UI, claude.ai web
Server fallback	(env `CANLII_API`)	Self-hosted single-tenant. Required for stdio.
MCP gate	`Authorization: Bearer <MCP_AUTH_TOKEN>`	Optional, self-host only. The public hosted endpoint at `canlii-mcp.vaquill.ai` does not use it, so no bearer token is required.

Tools

Tool	Description
`list_case_databases`	List all courts and tribunals in the CanLII collection
`list_cases`	Browse decisions from a specific court/tribunal database
`get_case`	Get metadata for a specific case (title, citation, date, keywords)
`get_case_citations`	Get cases cited by a case, cases citing it, or legislation it references
`list_legislation_databases`	List all statute and regulation databases
`list_legislation`	Browse statutes or regulations from a specific database
`get_legislation`	Get metadata for a specific piece of legislation

Requirements

Node.js 22+
A CanLII API key — apply here

Usage

stdio via npx (quickest)

json

{  "mcpServers": {    "canlii": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@tomilashy/canlii-mcp"],      "env": {        "CANLII_API": "your_api_key"      }    }  }}

{  "mcpServers": {    "canlii": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@tomilashy/canlii-mcp"],      "env": {        "CANLII_API": "your_api_key"      }    }  }}

stdio (from source)

Add to your MCP config:

json

{  "mcpServers": {    "canlii": {      "command": "node",      "args": ["/path/to/canlii-mcp/dist/index.js"],      "env": {        "CANLII_API": "your_api_key"      }    }  }}

{  "mcpServers": {    "canlii": {      "command": "node",      "args": ["/path/to/canlii-mcp/dist/index.js"],      "env": {        "CANLII_API": "your_api_key"      }    }  }}

HTTP server

The MCP endpoint is available at http://localhost:3000/mcp. The server runs in stateless mode — each request is self-contained, no session ID or initialize handshake required. Clients can call tools directly:

bash

curl -X POST http://localhost:3000/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_case_databases","arguments":{"language":"en"}}}'

curl -X POST http://localhost:3000/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_case_databases","arguments":{"language":"en"}}}'

Docker

bash

docker run -e CANLII_API=your_api_key -e MCP_AUTH_TOKEN=your_secret -p 3000:3000 ghcr.io/tomilashy/canlii-mcp

docker run -e CANLII_API=your_api_key -e MCP_AUTH_TOKEN=your_secret -p 3000:3000 ghcr.io/tomilashy/canlii-mcp

Or with Docker Compose:

yaml

services:  canlii-mcp:    image: ghcr.io/tomilashy/canlii-mcp    environment:      CANLII_API: your_api_key      MCP_AUTH_TOKEN: your_secret  # optional    ports:      - "3000:3000"

services:  canlii-mcp:    image: ghcr.io/tomilashy/canlii-mcp    environment:      CANLII_API: your_api_key      MCP_AUTH_TOKEN: your_secret  # optional    ports:      - "3000:3000"

Cloudflare Workers

The server includes a Workers-compatible entry point (src/worker.ts).

CLI deploy

bash

npx wrangler secret put CANLII_APInpx wrangler secret put MCP_AUTH_TOKEN  # optionalnpx wrangler deploy

npx wrangler secret put CANLII_APInpx wrangler secret put MCP_AUTH_TOKEN  # optionalnpx wrangler deploy

Dashboard deploy (Connect to Git)

Go to Cloudflare Dashboard → Workers & Pages → Create → Connect to Git
Select your tomilashy/canlii-mcp repository
On the Set up your application page:
- Project name: canlii-mcp
- Build command: npm install && npm run build
- Deploy command: npx wrangler deploy (pre-filled)
Expand Advanced settings:
- Variable name: CANLII_API
- Variable value: your CanLII API key
- Check Encrypt to store it as a secret
Click Deploy

The MCP endpoint will be at https://canlii-mcp.<your-subdomain>.workers.dev/mcp.

Configuration

Environment Variable	Required	Default	Description
`CANLII_API`	Only for stdio and self-hosted single-tenant	—	Your CanLII API key. Not needed in HTTP mode, where clients bring their own key per request.
`PORT`	No	`3000`	HTTP server port (HTTP mode only)
`MCP_AUTH_TOKEN`	No	—	Bearer token for HTTP authentication. If set, all HTTP requests must include `Authorization: Bearer <token>`. If not set, the server runs without authentication.

Rate Limits

The server enforces CanLII's API limits automatically, per CanLII key, so one caller's usage never throttles another's:

1 request at a time
2 requests per second
5,000 requests per day

These mirror CanLII's own per-key limits. Each X-CanLII-Token gets its own independent budget (keyed by a hash of the key; raw keys are never retained). Requests that exceed the daily limit return an error rather than hitting the API.

Development

Release

This project uses Semantic Versioning via semantic-release. Commit messages follow the Conventional Commits spec:

Pushing to main triggers the release workflow. If a release is cut, the Docker image is automatically built and published to ghcr.io.

License

MIT

Community

Questions, ideas, or want to contribute? Join the Vaquill community on Discord.

來源：README.md，提交 fad5aa1

工具

工具後設資料尚未被收錄。

版本歷史

v0.1.0最新Sep 16, 2026

Commit prefix	Release type
`fix:`	Patch (`1.0.0` → `1.0.1`)
`feat:`	Minor (`1.0.0` → `1.1.0`)
`feat!:` or `BREAKING CHANGE`	Major (`1.0.0` → `2.0.0`)

CanLII

概覽

安裝

在 SourceWeft 中

其他 MCP 客戶端

README

canlii-mcp

Use the hosted endpoint (no install)

Claude Desktop / Claude Code

Cursor / VS Code / Windsurf

Authentication

Tools

Requirements

Usage

stdio via npx (quickest)

stdio (from source)

HTTP server

Docker

Cloudflare Workers

CLI deploy

Dashboard deploy (Connect to Git)

Configuration

Rate Limits

Development

Release

License

Community

工具

版本歷史

更多類似 CanLII 的服務

Lochless

Search Memory

Kariwood Product Knowledge