About Bundestag De
Bundestag De is an MCP server for Germany's Bundestag DIP API. It is intended for users researching parliamentary activity, with searchable records for proceedings, printed documents, and people.
Key features
- 01Search parliamentary activities
- 02Search bills and printed documents
- 03Retrieve printed-document details
- 04Search plenary transcripts
- 05Search people referenced in DIP
Use cases
- 01Research bills and parliamentary questions
- 02Find plenary meeting transcripts
- 03Look up people referenced in DIP
MCP support
Exposes search and detail tools for the Bundestag DIP API to MCP clients. It runs locally over stdio or can be accessed through the Pipeworx gateway.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/bundestag-de/mcpclaude mcp add --transport http pipeworx-io-bundestag-de https://gateway.pipeworx.io/bundestag-de/mcp{"mcpServers":{"pipeworx-io-bundestag-de":{"type":"http","url":"https://gateway.pipeworx.io/bundestag-de/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-bundestag-de":{"type":"http","url":"https://gateway.pipeworx.io/bundestag-de/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-bundestag-de":{"type":"http","url":"https://gateway.pipeworx.io/bundestag-de/mcp"}}}{"mcpServers":{"pipeworx-io-bundestag-de":{"serverUrl":"https://gateway.pipeworx.io/bundestag-de/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 README@pipeworx/bundestag-de
German Bundestag MCP — DIP (Documentation and Information System) API. Plenary minutes, bills, parliamentary questions, members.
Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
search_activities(query?, ressort?, descriptor?, date_from?, date_to?, format?, cursor?, num?)— combined activity feedsearch_drucksachen(query?, drucksachentyp?, date_from?, date_to?, cursor?, num?)— Bundestag/Bundesrat printed documents (bills, motions, ...)get_drucksache(id)— printed document detailsearch_plenarprotokolle(query?, date_from?, date_to?, cursor?, num?)— plenary meeting transcriptsget_plenarprotokoll(id)— plenary protocol detailsearch_persons(query?, cursor?, num?)— people referenced in DIP
Auth
- Platform key: gateway env
PLATFORM_BUNDESTAG_KEY - BYO:
?_apiKey=<key>after registering at https://dip.bundestag.de/über-dip/hilfe/api
A widely-known public demo key (rgsaY4U.oZRQKUHdJhF9qguHMkwCGIoLaSc3Bdgwod) works on the production API and is acceptable for read-only experimentation per Bundestag guidance.
Data source
https://search.dip.bundestag.de/api/v1/ — JSON, apikey= query param.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bundestag-de": {
"url": "https://gateway.pipeworx.io/bundestag-de/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/bundestag-de/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 1875+ 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/search_activities \
-H 'Content-Type: application/json' \
-d '{"query":"Klimawandel","ressort":"BMU","date_from":"2024-01-01","date_to":"2024-12-31","num":50}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_activities. 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": {
"bundestag-de": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-bundestag-de"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-bundestag-de
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 Bundestag De 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.