About Folketinget Dk
Folketinget Dk exposes Danish parliamentary open data to users who need to query cases, actors, votes, meetings, and documents. Its keyless tools can also extract and page through the text of published documents, with provenance information.
Key features
- 01OData queries across parliamentary entities
- 02Fetch records by numeric ID with expansions
- 03Search cases by title substring
- 04Extract and page through document text
- 05Include source and data-as-of metadata
Use cases
- 01Look up cases or parliament actors
- 02Explore voting and meeting records
- 03Read ministerial answers or bill text
MCP support
As an MCP server, it provides tools for querying parliamentary data, retrieving records, searching cases, and extracting document text. It can connect through the Pipeworx gateway or run locally over stdio.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/folketinget-dk/mcpclaude mcp add --transport http pipeworx-io-folketinget-dk https://gateway.pipeworx.io/folketinget-dk/mcp{"mcpServers":{"pipeworx-io-folketinget-dk":{"type":"http","url":"https://gateway.pipeworx.io/folketinget-dk/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-folketinget-dk":{"type":"http","url":"https://gateway.pipeworx.io/folketinget-dk/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-folketinget-dk":{"type":"http","url":"https://gateway.pipeworx.io/folketinget-dk/mcp"}}}{"mcpServers":{"pipeworx-io-folketinget-dk":{"serverUrl":"https://gateway.pipeworx.io/folketinget-dk/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEfolketinget-dk
Danish Parliament (Folketinget) open data: cases, actors, votes, meetings and documents, plus the full text of a published document.
Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Source: Folketinget, parliamentary data service and document register. Keyless, live, public. Field names and values are Danish.
Tools
query_entity-- OData query over any entity (Sag,Aktør,Afstemning,Møde,Dokument, ...).get_entity_by_id-- one record by numeric id, with$expand.search_cases-- cases/bills whose title contains a substring.document_text-- the extracted TEXT of aDokumentby id (a minister's answer to a committee question, a bill text, ...). Returns title, date, question wording, who answered, the text, and areasonwhenever no text could be returned (no_file,file_blocked,no_extractable_text, ...), so an empty result is never ambiguous. The file format is detected from the bytes, not from the declared format. Long texts page withoffset/max_chars.
Provenance
Every document_text response carries source ("Folketinget, parliamentary
document register"), the document id and data_as_of.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"folketinget-dk": {
"url": "https://gateway.pipeworx.io/folketinget-dk/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/folketinget-dk/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 1879+ 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/query_entity \
-H 'Content-Type: application/json' \
-d '{"entity":"Sag","filter":"year(opdateringsdato) eq 2024","top":10,"orderby":"opdateringsdato desc"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/query_entity. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"folketinget-dk": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-folketinget-dk"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-folketinget-dk
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
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 Folketinget Dk data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.