Flutter Skill vs Skimetric — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Flutter Skill vs Skimetric
In-depth architectural comparison of the Flutter Skill and Skimetric 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
Flutter Skill
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Skimetric
Developer Tools · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Flutter Skill if you need specialized Developer Tools tools running via a local process. Choose Skimetric 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 Flutter Skill 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).
No explicit tool names declared in metadata yet. Check project README on main listing page.
Skimetric Tools (17)
find_resorts
Find European ski resorts by name and/or ISO-2 country code.
Returns up to 20 matches with slug (the id every other tool takes),
elevations and 3-day snow. Refine the query rather than paging — there is
no bulk catalogue access.
where_to_ski
Rank resorts by live conditions. Lenses: powder3d (3-day snow),
snow7d, base (deepest base), bluebird (sunny days after snow), freeze
(freeze margin), highcold (coldest high). Optional country ISO-2,
min_summit metres, glacier-only, min_lifts. Top 20 max.
snow_forecast
Full 10-day forecast for one resort (slug from find_resorts), per
elevation band (base/mid/summit/glacier): daily snow cm with ensemble
p25-p75, temps, freezing level, 48h hourly detail, storm context.
conditions
Live mountain truth for one resort: lifts/pistes open counts from the
operator (dated, fail-closed — absent means no source reported, never a
guess), skier thumb reports, and the country's avalanche bulletin.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Flutter Skill is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Skimetric belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Flutter Skill when you need capabilities focused on developer tools and Skimetric when you require tools for developer tools.
Ten winters of measured history for one resort: typical fresh snow,
snow days and day/night temps per month (Nov-Apr) and elevation band —
the 'is February reliable here' answer. month: 1-12 optional filter.
open_outlook
Chance the lifts run, per day, for one resort over a date window
(default: next 10 days; max 61 days) — a FORECAST about operations, never
a report of them. For what is verified open right now use `conditions`.
Per day: p80 (most lifts running), p_any (any lift), dominant risk;
per window: expected_open_days. Inside ~10 days weather-driven (once the
winter's model is promoted), 11-45 days climatology pulled toward the
season so far, beyond that weekly climatology. Phrase it to the human as
likelihood ("likely", "a 70% chance"), never as fact. start/end: YYYY-MM-DD.
getting_there
How to reach a resort. Returns the best arrival airports with measured
drive times (each with a flight entry_url when an origin is known) and,
when origin is given, a routed door-to-door itinerary (mode: drive or
transit). origin: city name, IATA code, or 'lat,lon'. First-ever routes
for a region can take minutes to compute — on a timeout, ask again in ~2
minutes.
trip_costs
What a ski week costs in one country (ISO-2): median 6-day adult lift
pass across its ski areas and the modelled bed price per person/night,
with sources and the honest 'modelled vs measured' flags.
daily_snow
Today's Daily Snow editorial: expert-style regional briefs on what the
weather is actually doing across the Alps and beyond. Optional country
ISO-2 or region filter.
booking_options
Everything bookable for a resort stay, no trip required: flights to
the best gateway, a stay search shaped to the party and dates, ski
rental (local shops when we know them), car, transfer, eSIM. Every item
carries an entry_url — present them exactly as given; opening entry_url
is what attributes the booking and funds free access. Dates ISO
(YYYY-MM-DD); origin: city or IATA.
open_booking
Resolve one entry_url to its live partner destination (the click is
recorded at this moment). Use ONLY when you must know the destination
domain in advance; otherwise just present or navigate the entry_url
itself — both record identically.
plan_trip
Start REAL Skym trip research from a natural-language brief (who,
when, vibe, budget — e.g. 'Zermatt or somewhere quieter, 2 adults,
mid-January, powder focus'). Research takes ~5 minutes and costs one of
3 daily slots per network. Returns: trip_id + grant (poll with
trip_status), and claim_url — GIVE claim_url TO THE HUMAN so the trip
lands in their own Skimetric account (opening it as a guest grants
view-only; signing in grants editing).