Summary
Connects Claude to Norway's parliamentary open data API at data.stortinget.no, giving you programmatic access to Stortinget proceedings, votes, representatives, and legislative documents. Part of the Pipeworx gateway ecosystem, which means you can either use this standalone endpoint or tap into their broader collection of 250+ data sources through a unified interface. The ask_pipeworx wrapper lets you query in natural language instead of calling specific tools directly. Useful if you're building political analysis tools, researching Norwegian legislation, tracking parliamentary activity, or need structured access to official government records without scraping HTML pages.
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →
Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →mcp-storting-no
Stortinget (Norwegian Parliament) open data MCP — data.stortinget.no.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
| Tool | Description |
|---|---|
get_sessions | List Norwegian Parliament (Stortinget) sessions. A session ("sesjon") runs ~Oct–Sep with an id like "2023-2024". Use the returned ids as sesjonid for other tools. |
get_cases | List parliamentary cases/bills ("saker") for a session. Returns saker_liste with numeric case ids (sakid), titles, topics (emne_liste) and status. |
get_representatives | List members of parliament (MPs, "representanter") for a 4-year electoral period. Returns fornavn (first), etternavn (last), parti (party), fylke (county), kjoenn (gender). |
get_parties | List all political parties ("partier") known to Stortinget. Returns id (e.g. "A", "H", "FrP"), navn (full name), and representert_parti (currently represented). |
get_votes | List the votes ("voteringer") held on a single case. Returns sak_votering_liste; each has a votering id. Pass that id to get_vote_result for per-MP breakdown. |
get_vote_result | Per-MP results ("voteringsresultat") for one vote: how each representative voted (for/against/absent). Pass a votering id from get_votes. |
export | Generic fallback to any data.stortinget.no/eksport resource. Use for endpoints without a dedicated tool, e.g. resource "moter" (meetings), "komiteer" (committees) with params {sesjonid}. ?format=json is added automatically. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"storting-no": {
"url": "https://gateway.pipeworx.io/storting-no/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/storting-no/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Storting No data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Featured
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →