UI5 MCP Server vs Storting No — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
UI5 MCP Server vs Storting No
In-depth architectural comparison of the UI5 MCP Server and Storting No MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
UI5 MCP Server
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Storting No
Developer Tools · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Verdict Summary: Choose UI5 MCP Server if you need specialized Developer Tools tools running via a local process. Choose Storting No if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose UI5 MCP Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
UI5 MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Storting No belongs to Developer Tools using local stdio subprocess. Select UI5 MCP Server when you need capabilities focused on developer tools and Storting No when you require tools for developer tools.
Extracts metadata and configuration from a UI5 project.
get_typescript_conversion_guidelines
Provides guidelines for converting UI5 applications and controls from JavaScript to TypeScript.
get_version_info
Retrieves version information for the UI5 framework.
run_manifest_validation
Validates the manifest against the UI5 Manifest schema.
run_ui5_linter
Integrates with [`@ui5/linter`](https://github.com/UI5/linter) to analyze and report issues in the UI5 code.
Storting No Tools (7)
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.