Andrea9293 MCP vs Storting No — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Andrea9293 MCP vs Storting No
In-depth architectural comparison of the Andrea9293 MCP 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
Andrea9293 MCP
Developer Tools · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Storting No
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Andrea9293 MCP if you need specialized Developer Tools tools running via a local process. Choose Storting No if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Andrea9293 MCP 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).
Andrea9293 MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Storting No belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Andrea9293 MCP when you need capabilities focused on developer tools and Storting No when you require tools for developer tools.
Lists files in the uploads folder with size and format info
get_ui_url
Returns the Web UI URL (e.g. http://localhost:3080) — useful to open the dashboard or to locate the uploads folder from the browser
search_documents
Semantic vector search within a specific document
search_all_documents
Hybrid (full-text + vector) cross-document search
get_context_window
Returns a window of chunks around a given chunk index
search_documents_with_ai
🤖 AI-powered search using Gemini (requires `GEMINI_API_KEY`)
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.