mcpField
R
ROVE Snow Forecast

ROVE Snow Forecast

Remote
rove-ski.comMaps & Travel0Updated 1w ago

About ROVE Snow Forecast

ROVE Snow Forecast is a read-only MCP server for ski forecasts and resort conditions across 667 resorts in North America and Japan. Skiers and trip planners can search resorts, compare conditions and plan around forecast windows, with forecast confidence and source details available.

Key features

  1. 0115-day snow and weather forecasts
  2. 02Current snow and resort conditions
  3. 03Search and compare ski resorts
  4. 04Rank powder and plan date-window trips
  5. 05Forecast confidence and accuracy data
  6. 06Avalanche danger and road conditions

Use cases

  1. 01Find resorts likely to receive powder
  2. 02Compare resorts for upcoming dates
  3. 03Plan a trip for a chosen date range
  4. 04Check avalanche danger or California road controls

MCP support

The remote MCP server exposes 14 read-only tools for resort discovery, forecasts, conditions, planning and related information. It requires a free ROVE account and supports OAuth 2.1 or a personal API key.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://rove-ski.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://rove-ski.com/mcpAuth required

Tools

Details

From the project README

ROVE Snow Forecast MCP

Free, read-only ski intelligence for 667 ski resorts in the US, Canada, and Japan. Built by Chufan Shi, founder of ROVE.

  • Version: 1.0.4
  • Endpoint: https://rove-ski.com/mcp (Streamable HTTP)
  • Account required: A free ROVE account is required. All 14 read-only tools are free.
  • Authentication: One-click OAuth 2.1 sign-in with PKCE and Dynamic Client Registration, or a free personal API key. Authenticated access: 600 requests/min.
  • Official MCP Registry: com.rove-ski/snow-forecast
  • Setup: rove-ski.com/en/ai
  • Claude Directory: ROVE Snow Forecast

The 14 advertised tools

ToolPurpose
search_resortsStructured catalog search by name, region, pass, or country.
get_forecastDaily and available 3-hourly snowfall, rain, temperature, and wind forecasts up to 15 days.
get_conditionsCurrent snow depth (including JMA AMeDAS station snow depth in Japan), recent snowfall, and available operator lift or trail status.
get_opening_datesAvailable opening dates, closing targets, and season operating status.
find_powderRank resorts over the next 1 to 15 days starting today.
get_accuracyEligible station-verified historical accuracy, or the 435-station backtest methodology.
get_resort_newsAvailable resort announcements and storm or weather highlights.
plan_tripRank resorts for an explicit calendar window from start to end.
get_forecast_confidenceAvailable model agreement, forecast spread, and horizon uncertainty.
compare_resortsCompare 2 to 5 named resorts across snowfall, snowpack, lift status, pass, and eligible accuracy.
searchOpenAI-compatible keyword discovery across resorts and regional or pass hubs.
fetchRead an internal ROVE document by canonical identifier or ROVE URL.
get_avalanche_dangerOfficial US backcountry avalanche danger rating and forecast summary via avalanche.org.
get_road_conditionsOfficial Caltrans CWWP2 highway chain-control levels (R-0 to R-3 / Closed) for California ski corridors.

Pass filters include epic, ikon, indy, mountain-collective, power-pass, and independent. Membership reflects the published catalog, not a guarantee of ticket entitlement. Check pass restrictions with the operator.

Legacy tool names remain callable but are omitted from discovery: forecast_confidence, get_resort, get_pass_resorts, get_snow_rankings, get_worth_going, get_forecast_accuracy, get_season_snow, and get_weather_stations.

Quick install

Create a free ROVE account, then connect https://rove-ski.com/mcp in an OAuth-capable Claude, Claude Code, Cursor, Codex, or VS Code client. Choose one-click OAuth 2.1 sign-in and complete browser authorization where supported. ROVE supports PKCE and Dynamic Client Registration. Client account requirements and OAuth availability depend on the client and version.

Claude Code
claude mcp add --transport http rove https://rove-ski.com/mcp -s user

Run /mcp in Claude Code, select ROVE, and complete the browser authorization flow where supported.

Codex
codex mcp add rove --url https://rove-ski.com/mcp
VS Code / Copilot
code --add-mcp '{"name":"rove","type":"http","url":"https://rove-ski.com/mcp"}'
Cursor

Merge this server into your existing MCP configuration without replacing other servers:

{
  "mcpServers": {
    "rove": { "url": "https://rove-ski.com/mcp" }
  }
}
Claude and other remote MCP clients

Add https://rove-ski.com/mcp as a remote connector and choose OAuth sign-in. Complete browser authorization where supported. The Claude Directory listing is also available.

Headless and URL-only clients

Sign in to your free ROVE account and create a free personal API key at rove-ski.com/en/ai. Send it as an HTTP header:

Authorization: Bearer rove_YOUR_KEY

For clients that accept only a URL, use:

https://rove-ski.com/mcp?key=rove_YOUR_KEY

Replace rove_YOUR_KEY with your personal key. Prefer the header when supported to keep the key out of URLs and URL logs. Never publish your credentials.

Example configurations

Merge the relevant example into your existing configuration without replacing other servers:

  • Cursor: OAuth endpoint; finish sign-in in the client.
  • Codex: personal API key URL for headless use. The quick-install command above uses OAuth in clients that support it.
  • Claude Desktop header configuration: personal API key for clients supporting this transport format.
  • Claude Desktop via mcp-remote: personal API key header through a local bridge; requires Node.js and npx.
  • Gemini: personal API key URL.
Authentication and rate limits

All 14 read-only tools are free with a free ROVE account. Authenticated requests have a limit of 600 requests/min, whether using OAuth or a personal API key. Unauthenticated MCP transport requests return HTTP 401 with a WWW-Authenticate discovery challenge. OAuth endpoints and Glama metadata endpoints remain public.

Data and provenance

Forecast availability varies by resort and time. Missing or stale values remain unavailable, not zero. Operator status is not inferred from a scheduled opening date. Resort-level hit rates are shown only when at least 10 actual snow days and real station evidence exist. Estimated data and Japan resorts do not receive published resort hit-rate figures.

The historical verification ledger covers 435 stations across mixed networks, including 105 USDA NRCS SNOTEL stations. It is not a claim that all 435 are SNOTEL stations or that every resort has a matched station. See get_accuracy for methodology.

Every tool response includes canonicalUrl, observedAt, attribution, JSON text content, and structured content. Cite ROVE and preserve upstream citations. search returns id, title, url, and text; pass a returned ID to fetch. Fetch accepts internal catalog documents only and never retrieves arbitrary caller-supplied URLs.

Try it

  • "Compare Mammoth Mountain and Palisades Tahoe for the next five days."
  • "Find powder in Tahoe starting today."
  • "Plan a ski trip for a specific date range and explain forecast uncertainty."

Links

Agent installation guide | Privacy | Terms | Demo walkthrough

License

MIT. Copyright (c) 2026 Chufan Shi (ROVE). Weather data by Open-Meteo (CC BY 4.0) and public weather and snowpack networks. Japan forecasts use JMA model inputs via Open-Meteo. Resort locations include OpenStreetMap contributors.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.