Skip to content
Open Snotel home
MCP

MCP overview

What the MCP server at /mcp gives an agent: thirteen read-only tools over the same data as the REST API, and what it deliberately does not expose.

https://opensnotel.com/mcp

The MCP server lets an agent read public SNOTEL data directly: search for a station, read its latest conditions and history, find the stations nearest a point, see how a station's snowpack compares with its own history, read the weather around it, and find a ski resort and the SNOTEL stations that relate to it. It is a remote server over Streamable HTTP at a path on this site, public and read-only, with no account or key.

Not a second dataset

MCP and the REST API are two doors to the same thing. Both call the same domain functions and the same cache, so a tool call and the equivalent API request return the same answer, with the same limits. Nothing in MCP is stored, computed or filtered differently.

What it exposes

Thirteen tools, all read-only:

  • stations_search and stations_nearest find a station.
  • station_get, station_latest and station_observations read one, and station_data_quality says whether its readings can be trusted right now: freshness, recent plausibility flags and known gaps per core element.
  • station_context, station_climatology and snow_rankings read Snowpack Context: recent change, comparison with the station's WY1991–2020 history, and stations ranked by one defined measure. Those values are derived from the observations and labeled so.
  • station_weather reads the stored weather around a station: its observed air temperature, nearby National Weather Service observations, the NWS forecast for its point and NWS alerts in effect. Every value says whether it is a SNOTEL observation, an NWS observation or an NWS forecast.
  • resorts_search, resort_get and resort_stations read the ski resort registry and which SNOTEL stations relate to a resort. Each station is labeled as a reviewed (curated) mapping or a candidate computed from distance alone, which is never presented as representing the resort. Resort results carry the registry's ODbL attribution.

Every result carries its source and units, the source's flags, null for a missing reading (never zero), and, for latest conditions, a verdict on whether the data is fresh. The tools page has the arguments, limits and result shapes.

What it does not expose

There are no ski recommendation tools, nothing that says which resort has the best snow, and no separate forecast or alert tools: the NWS forecast and alerts come only with a station's weather, labeled as forecast and as NWS products. There is no estimated snowfall, and no tools that write anything. Because everything is public, there is no sign-in.

Usage & pricing

The MCP server is free, without a key, for personal, non-commercial, educational, research, journalistic and nonprofit use, and for evaluating or prototyping a commercial product, within the rate limits (Terms, section 3).

Commercial use needs a commercial plan or a written agreement (section 4). That covers a paid, subscription or ad-supported product, internal use by a for-profit business, AI or agent products that call the MCP server for their users, reselling, redistributing, bulk downloading, caching or mirroring responses as a dataset or service, and any use above the free rate limits. Until self-serve plans are available, Pricing has the contact.

Clients also agree to the API and MCP rules. The Terms of Use and Privacy Policy cover the rest.

Where to go next

Connect a client, read the tools, or see worked examples.