SnowSure Connector

Use SnowSure inside Claude, ChatGPT, Cursor & more

Name: SnowSure MCP Server
Author: SnowSure

One URL. No install. Real-time snow conditions and 14-day forecasts for 500+ resorts, available in any AI chat that supports the Model Context Protocol.

MCP server URL

https://www.snowsure.ai/mcp

Streamable HTTP · stateless · public · read-only

Now a ChatGPT App — Connect in one click

Live in the ChatGPT app directory. No connector setup — just hit Connect.

🏔️

500+ resorts

From the Alps to Niseko, Whistler, Aspen, the Andes, and beyond.

🌨️

7 weather models

ECMWF, GFS, GEM, JMA, ICON, Météo-France, Met Norway — averaged into one forecast.

⚡

40 tools, 12 resources

Grounded Q&A via ask_snowdata, powder rankings, insights, and destination hubs.

Add to Claude.ai

Available on Claude.ai (web) on the Pro, Max, Team, and Enterprise plans. Custom connectors are currently in beta.

Open claude.ai and go to Settings → Connectors.
Click Add custom connector.
Name it SnowSure and paste the URL: https://www.snowsure.ai/mcp.
Leave OAuth Client ID and Secret blank — SnowSure is public and read-only.
Click Add.

Claude.ai's Add custom connector dialog with SnowSure name and https://www.snowsure.ai/mcp filled in

Claude’s “Add custom connector” dialog. Leave the OAuth fields blank.

Then: in any chat, look for the tools / connectors menu near the composer (often a slider or wrench icon) and toggle SnowSure on for that conversation. You only need to do this once per chat.

Add to ChatGPT

SnowSure is now an official ChatGPT App. The fastest path is the app directory — no connector setup, no URL to paste. Open the listing and hit Connect. You’ll get the same inline snow cards (single-resort report, ranked powder list, deepest-base) right in the chat.

Open SnowSure in ChatGPT →

Prefer to add it manually as a connector? You can also point any recent ChatGPT build at the raw MCP URL. Look for “Connectors”, “Custom GPT connectors”, or “MCP servers” depending on the build.

Open ChatGPT → Settings → Connectors (or MCP servers).
Click Add HTTP server / Add custom connector.
Name it SnowSure, paste https://www.snowsure.ai/mcp, and save.
Authentication: None.
Enable Developer mode under Apps & Connectors → Advanced if Connectors are not visible yet.
After setup, ask for powder rankings or a resort report — SnowSure returns inline snow cards (ranked list + single-resort report) when ChatGPT renders Apps SDK widgets.

If you don’t see Connectors in your build yet, you can also use SnowSure through our existing Custom GPT. In the GPT builder, disable Web Browsing and paste instructions from gpt-instructions.md so answers come from the SnowSure Answer Engine, not J2Ski or other sites.

Add to Cursor

Cursor supports both HTTP and stdio MCP servers. We recommend HTTP (no install).

Open Cursor → Settings → Cursor Settings → MCP & Integrations.
Click Add new MCP server.
Choose URL / HTTP, name it snowsure, paste https://www.snowsure.ai/mcp.
Save and toggle the server on.

Or paste this directly into your .cursor/mcp.json:

{
  "mcpServers": {
    "snowsure": {
      "url": "https://www.snowsure.ai/mcp"
    }
  }
}

Try it: MCP Inspector & curl

Want to poke at the server before wiring it into a client? Two quick options:

MCP Inspector (visual)

npx @modelcontextprotocol/inspector
# then paste https://www.snowsure.ai/mcp into the URL field

curl (raw JSON-RPC)

curl -X POST https://www.snowsure.ai/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "find_best_powder",
      "arguments": { "minSnowfall": 10, "limit": 5 }
    }
  }'

Legacy: stdio package

For clients that don’t yet support remote MCP (older Claude Desktop builds, some self-hosted agents), the same tools are available as a local npm package.

{
  "mcpServers": {
    "snowsure": {
      "command": "npx",
      "args": ["-y", "snowsure-mcp-server"]
    }
  }
}

Source on GitHub. MIT-licensed.

What can I ask?

Once connected, just chat normally. The AI will pick the right tool automatically. Some ideas to get started:

Discovery

“Where’s the best snow right now?”
“Top 5 ski resorts in Europe by SnowSure score.”
“Which resorts in Japan got the most fresh snow in the last 24 hours?”
“Find me powder in the Alps with at least 15cm overnight.”

Specific resorts

“What are conditions at Niseko Hanazono?”
“Tell me about Jackson Hole — depth, recent snow, forecast.”
“How’s Val d’Isère looking for next week?”
“Show me the live webcams for Cervinia.”

Forecast confidence

“Compare the 14-day forecasts for Whistler and Aspen.”
“How reliable is the forecast for Zermatt? Show me model agreement.”
“Which model is most bullish on snow for St. Anton this week?”

Trip planning

“I’m an advanced skier looking at the Alps in late February. Where should I go?”
“Find resorts with at least 200cm base, 2,500m+ summit, and SnowSure score above 50.”
“Plan a powder week in Japan for an intermediate skier.”

Tip: if the AI doesn’t reach for the connector, prefix your question with “using SnowSure, …” and it’ll call a tool instead of guessing from training data.

Resort operators: update content via MCP

Partners with a SnowSure admin account can connect Claude to edit resort copy(descriptions, links, season dates, webcam page URL, apres-ski block) and publish to the live site. This uses a separate authenticated endpoint — not the public read-only connector above.

Each resort can request a unique connector URL (recommended for Claude — no token field):

Per-resort URL (issued on request)

https://www.snowsure.ai/mcp/c/…

Alternate shared endpoint with Bearer token: https://www.snowsure.ai/mcp/write

SnowSure issues credentials: npx tsx scripts/issue-mcp-api-key.ts your-resort-slug
Resort pastes their unique /mcp/c/… URL into Claude (Auth blank)
Ask Claude to read get_resort_editable_content, propose edits, then update_resort_content with publish: true

Full operator guide: docs/mcp-resort-content-write.md in the repo. Keys are scoped to one resort and cannot change weather scores or SnowSure ratings. Read the full resort operator handout →

Tools & resources exposed

The connector exposes 40 tools that the AI can call, plus 12 resources for raw data access. Use ask_snowdata for conversational Q&A.

Tools

get_destination

Multi-mountain hub with live data for each member resort (Niseko, Chamonix, Hakuba, etc.).

ask_snowdata ★

Primary Q&A — grounded natural-language answers via the SnowSure Answer Engine (prefer this for chat questions).

get_snow_report

Global rankings by SnowSure score, fresh snowfall, depth, or 14-day forecast totals.

get_resort

Full resort detail: live conditions, 7-model forecast, history, webcams.

get_resort_info

Resort guide card: hero image, elevation, lifts/runs, season dates, ski passes.

get_resort_photos

Resort photo gallery carousel (official hero + Sanity images).

search_resorts

Resolve a name to canonical resort slugs (use before get_resort when unsure).

find_best_powder

Resorts with the freshest 24-hour snowfall, filtered by region and minimum cm.

find_powder_trips

Bookable powder trips: ranks destinations by their 14-day forecast and pairs each with handpicked luxury ski hotels + booking links (optional vibe filter: lux/hip/family/budget).

compare_forecasts

Side-by-side 14-day forecast across all 7 weather models with confidence rating.

get_weather_forecast

Day-by-day weather for up to 14 days for any resort.

find_resorts_by_criteria

Filter by depth, elevation, runs, SnowSure score, country, region.

get_snow_history

Season-to-date totals plus 5-year and 30-year averages.

plan_ski_trip

Trip recommendations for a region, ability level, and date window.

get_webcam_status

Live webcam links and thumbnails.

get_regional_summary

Regional / country statistics and top resorts by score.

get_southern_hemisphere_report

In-season AU/NZ/AR/CL snow report (June–October NH off-season).

get_season_openings

Resorts whose season opening date is a specific day — "what opens today?" (not all open resorts).

list_insight_categories

Taxonomy of SnowSure intelligence card categories.

get_insights

Season norms, forecast trust, and other intelligence cards (filter by category).

get_ml_trends

SnowSure-unique ML/AI datasets: powder/bluebird leaderboards, score components, model accuracy, bluebird predictions, forecast trust, snow events.

get_pass

Ski-pass details: operator, season pricing tiers, destinations, regions, buy link (Epic, Ikon, Mountain Collective, …).

find_pass_resorts

List the resorts on a ski pass, optionally by region, with SnowSure slugs.

compare_passes

Compare ski passes on price, resort coverage, and value vs window lift tickets for a planned trip.

compare_resorts

Compare 2–4 resorts side by side across snow, terrain, and live conditions (all values from the conditions resolver).

get_avalanche

Official avalanche danger bulletin for a resort’s forecast zone (US/Canada/Switzerland), relayed with issuer + link.

get_operating_risk

Will the lifts run? 48h wind-hold / visibility / cold / heavy-snow risk from the Open-Meteo forecast.

get_road_access

Driving access: chain-control / mountain-pass / road-surface conditions on nearby highways (California, Washington, Colorado, Utah via Caltrans/WSDOT/CDOT/UDOT).

get_road_cameras

Live roadside DOT/CCTV camera stills on highways near a resort (California via Caltrans, Washington via WSDOT, Utah via UDOT) — what the drive looks like now.

get_road_weather

Measured roadside weather (RWIS) near a resort — surface/air temp, visibility, wind, precip (Colorado via CDOT, Washington via WSDOT, Utah via UDOT).

plan_ski_road_trip

Plan a multi-stop ski road trip: top resorts in a region ordered into a drivable route with day allocation, drive legs, conditions, and chain-control.

find_flights_to_powder

The "get there" leg: nearest gateway airport(s) for a resort plus flight-search links (Google Flights / Skyscanner / Kayak) from your home airport.

save_resort

Save a resort to your favorites (requires a signed-in SnowSure account).

remove_saved_resort

Remove a resort from your saved list (requires sign-in).

list_saved_resorts

List your saved resorts (requires sign-in).

subscribe_alerts

Subscribe to powder / opening / bluebird snow alerts (requires sign-in).

list_alerts

List your alert subscriptions (requires sign-in).

unsubscribe_alerts

Remove an alert subscription by id (requires sign-in).

book_lodging

Find lodging near a resort and get a booking link to confirm — never auto-books (requires sign-in).

get_my_snow_report

Personalized snow report for your saved resorts, ranked best-first by live conditions (requires sign-in).

Resources

ui://widget/powder-list.html

ChatGPT inline card — ranked powder / snow report list (Apps SDK).

ui://widget/snow-report-card.html

ChatGPT inline card — single-resort snow report (Apps SDK).

ui://widget/resort-info-card.html

ChatGPT inline card — resort guide / mountain stats (Apps SDK).

ui://widget/resort-gallery-card.html

ChatGPT inline card — resort photo gallery carousel (Apps SDK).

snowsure://snow-report

Current global snow report (top 50 resorts).

snowsure://resorts

All 500+ resorts with current conditions.

snowsure://regions

Region and country breakdown with resort counts.

snowsure://destinations

Multi-mountain destination hubs (Niseko, Chamonix, Aspen, etc.) with member resort slugs.

snowsure://insights/catalog

Intelligence card taxonomy (categories and card ids).

snowsure://trends/catalog

ML/AI trend REST endpoint index (powder/bluebird leaderboards, score components, model accuracy).

snowsure://faq/index

Seed FAQ index (identity, culture, gear, passes) in all locales.

snowsure://api-docs

OpenAPI-style endpoint index.

Troubleshooting

›Claude says “Couldn’t reach the MCP server”

Make sure the URL has no trailing slash or extra characters. Our endpoint is exactly https://www.snowsure.ai/mcp. If the error persists, try removing the connector and re-adding it — Claude caches the failure state.

›The AI ignores my SnowSure question and uses training data

In Claude.ai, make sure SnowSure is toggled on in the per-chat tools menu. Prefixing your prompt with “using SnowSure…” also works.

›Resort search returns nothing

Resort names sometimes differ from common spelling (e.g. “matterhorn-ski-paradise” for Zermatt). Ask the AI to search first — it'll return the correct slug to use for follow-ups.

›Is there an authentication option?

Not currently. The connector is intentionally public and read-only, mirroring our public REST API at /api/v1. If you need authenticated / write access for an integration, email api@snowsure.ai.

›What about rate limits?

No hard limits today; please be reasonable. We log usage and may add per-IP throttling if abuse becomes an issue. For high-volume use cases, talk to us.

Building something with SnowSure?

We’d love to hear about it. Whether you’re an AI agent author, a ski-trip planner, or a resort partner — tell us how the connector is showing up.