
Connects Claude to the UK Parliament's official data through a streamable HTTP gateway. You get seven tools covering the main parliamentary APIs: search and retrieve MPs and Lords by party or constituency, query bills by session or sponsor, track legislative stages from introduction to royal assent, search Hansard debate records, and pull recent division votes. Runs through Pipeworx's gateway, so you can either use it standalone or as part of their larger catalog. Useful when you need to answer questions about current legislation, look up voting records, or pull historical debate transcripts without writing API clients yourself.
UK Parliament MCP — official Westminster APIs: Members, Bills, Hansard (debates). No auth.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
search_members(name?, location?, party?, house?, is_current?, take?, skip?) — MPs and Lordsget_member(id, includes?) — member detailsearch_bills(query?, session?, stage?, member_id?, current_house?, take?, skip?) — billsget_bill(bill_id) — bill detailbill_stages(bill_id) — all stages of a billsearch_hansard(query, house?, date_from?, date_to?, member_id?, take?, skip?) — debates / contributionsrecent_divisions(house?, date_from?, take?) — recent voteshttps://members-api.parliament.uk/api/https://bills-api.parliament.uk/api/v1/https://hansard-api.parliament.uk/Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"uk-parliament": {
"url": "https://gateway.pipeworx.io/uk-parliament/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/uk-parliament/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.
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 Uk Parliament data" })
The gateway picks the right tool and fills the arguments automatically.
MIT