Skip to main content
Glama
README.md
# @pipeworx/ch-bger

Swiss Federal Supreme Court (Bundesgericht, Lausanne): search the published decisions from 2000 onward and read a decision's text.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1964+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Tools

- `ch_bger_search(query, department?, date_from?, date_to?, page?, limit?)` -- free-text search over decisions. Returns file number, decision date, deciding department, subject area, the topic line the court publishes, relevance score and the id for `ch_bger_get`. Exact and partial match counts are reported separately.
- `ch_bger_get(id, max_chars?, offset?)` -- the published decision text, paged, with `data_as_of`.

## Auth

Keyless.

## Data sources

- Swiss Federal Supreme Court, published decisions from 2000 (free public database). Live per request; nothing is stored.

Things to know:

- Decisions are in the language they were decided in (German, French or Italian). Search words match in that language, so query in it (`Persönlichkeitsschutz`, `protection des données`).
- Leading decisions (BGE) are a separate collection and are not searched here.
- Names are as the court publishes them (parties are anonymised).
- The court's search page is HTML; the pack parses it and fails with an explicit error if the page is not a result list, rather than returning an empty list.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "ch-bger": {
      "url": "https://gateway.pipeworx.io/ch-bger/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/ch-bger/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 1964+ 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/ch_bger_search \
  -H 'Content-Type: application/json' \
  -d '{"query":"Datenschutz Auskunft","department":"public_law","limit":3}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/ch_bger_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-ch-bger` 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/ch-bger/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "ch-bger": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-ch-bger"]
    }
  }
}
```

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 Ch Bger 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