parlament-mcp
Related Servers
Alternatives to parlament-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that connects AI models to the Lobbywatch.ch database, providing access to Swiss parliamentarians' conflicts of interest, lobby groups, access badges, and transparency scores.825 PyPIMIT
- AlicenseBqualityDmaintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.342 npmMIT

@openar/mcpofficial
AlicenseAqualityDmaintenanceMCP server for Portuguese Parliament open data, enabling AI agents to access legislative initiatives, deputies, plenary votes, petitions, and parliamentary committees.127 npmMIT- AlicenseBqualityAmaintenanceAn MCP server providing AI-powered access to Open Data from the City of Zurich, enabling queries to 900+ datasets, real-time environmental and mobility data, geodata, parliamentary proceedings, and more.26126 PyPI8MIT
- AlicenseAqualityAmaintenanceMCP server connecting AI models to Swiss Federal Food Safety and Veterinary Office open data, enabling queries about food recalls, animal disease surveillance, food control results, and more.1120 PyPIMIT
- AlicenseAqualityAmaintenanceMCP server for Switzerland's national metadata catalogue, enabling AI agents to discover datasets, APIs, public services, and publishers through free-text search and structured queries.13MIT
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: search vs. get, and business/transcripts/members/votes/sessions are clearly separated. The two search tools return different entity types, and the two get tools are distinguished by ID and purpose.
All tool names follow a consistent verb_noun pattern with 'search_' for queries and 'get_' for retrievals. No mixed conventions or vague verbs.
Seven tools cover the core parliamentary data domain without bloat. Each tool has a clear, non-redundant role, and the count is within the ideal 3-15 range.
The set covers search and retrieval for proposals, transcripts, members, votes, and sessions, which are the main entities. Minor gaps include no direct get_member by ID and no committee data, but agents can work around these with search_members and get_votes.