Skip to main content
Glama

@pipeworx/slovenia-law

Slovenian national legislation from the official register of regulations: search acts, decrees, rules and ordinances by title or abbreviation, then read the record and its text, whole or one article at a time. Original Slovenian text, with each regulation's Official Gazette citation and amendments.

Part of Pipeworx — an MCP gateway connecting AI agents to 1882+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

  • si_law_search(query, in_content?, in_force_only?, cursor?) — find regulations by title or abbreviation (for example ZVOP-2), or by Slovenian words in the text with in_content. Returns id, title, status (in force or not), adoption and publication dates, issuing and drafting bodies and a link. Ten per page; pass next_cursor for the next page.

  • si_law_get(id, article?, version?, max_chars?) — one regulation by id (for example ZAKO7959) or by gazette record number (2022-01-4187): title, abbreviation, type, status, Official Gazette citation with amendments, in-force date, text versions and the text. Default text is the newest unofficial consolidated version; article returns one article; version selects another text (Osnovni is the text as originally published). Long texts are capped at max_chars with a contents list.

Related MCP server: Slov-Lex MCP Server

Auth

Keyless.

Data sources

  • Slovenia, Legal Information System (PISRS), register of regulations — regulation records, Official Gazette citations and text versions.

The consolidated text (NPB) is an unofficial working text; the Official Gazette text prevails, and each response says which version it returns. data_as_of is the date of the live read. The register is read live on each call; nothing is copied. A search that finds nothing returns empty_reason, not an empty success. EU law is not in this pack (see the EUR-Lex pack).

Quick Start

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

{
  "mcpServers": {
    "slovenia-law": {
      "url": "https://gateway.pipeworx.io/slovenia-law/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/slovenia-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:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1882+ 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

curl -X POST https://gateway.pipeworx.io/v1/tools/si_law_search \
  -H 'Content-Type: application/json' \
  -d '{"query":"ZVOP-2"}'

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

Run it from npm

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

{
  "mcpServers": {
    "slovenia-law": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-slovenia-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 Slovenia Law data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers