Weathersight

What weathersight does

The weathersight MCP server exposes Weathersight’s weather and climate APIs as MCP tools. Its data includes more than a century of station observations, typical-weather distributions, historical baselines, extremes, degree-day indicators, forecast results, and climate trend series for locations around the world.

The toolset supports both focused analysis and broad discovery. You can scan regions for unusual conditions, compare a city’s recent or historical period with a 1991–2020 baseline, inspect daily heat or cold sequences, identify records and return periods, or rank locations by weather criteria. Seasonal tools also provide monthly forecast anomalies for the next six months.

How it works

This is a remote server rather than a package that runs locally. MCP clients connect to https://weathersight.io/api/mcp using Streamable HTTP. Authentication uses OAuth 2.0 authorization-code flow with PKCE and dynamic client registration, so clients can complete authorization without manually entering a token.

Many workflows use location first to resolve a city, station, name, or coordinate into a canonical locid. That identifier can then be reused with tools such as anom, compare, dailycomp, events, extremes, timeseries, and typicalweather. The countries and metrics tools provide reusable lookup data for country filters and metric identifiers.

Some tools operate directly on coordinates, names, countries, or geographic areas. anomalies, breaking, dailyweather, seasonal, and forecast-evaluation tools can therefore support regional or global queries without first selecting a single location.

Setup and configuration

Add the remote endpoint to an MCP client:

https://weathersight.io/api/mcp

In Claude Desktop or Claude web, open Settings, choose Connectors, select Add custom connector, enter the URL, and connect. Sign-in creates or reuses a Weathersight API token and starts a free trial. Other MCP clients can use the same endpoint if they support the server’s Streamable HTTP transport and OAuth authorization flow.

Subscription and token management are handled at https://weathersight.io/subscription. If access stops working, sign in again or reactivate the plan there. No local environment variables or installation steps are required for the remote connector.

Tools and capabilities

• Discover locations, canonical country IDs, and supported weather metrics.
• Compare observed periods with historical baselines using percentiles, z-scores, and anomaly series.
• Search for breaking conditions, recent extremes, compound weather events, and record-period context.
• Analyze climatology, monthly distributions, seasonal forecasts, degree days, and multi-decade trends.
• Rank the best locations for specified criteria or the best historical weeks and months to visit a location.
• Evaluate forecast accuracy by location, region, model, lead time, and recent verification window.

Limitations and notes

Date formats and supported time windows vary by tool. Daily comparisons and weather maps usually use YYYYMMDD, while annual, monthly, and seasonal queries use shorter forms. Several computed tools recommend short ranges for response speed; for example, dailycomp works best for ranges up to 30 days, degreedays accepts intervals of up to 14 days, and recentextremes recommends windows no longer than three months.

Forecast and observation coverage are distinct. Observations generally extend through yesterday, while daily forecasts cover the next seven days. bestplace uses forecasts for daily scope but historical baselines for weekly and monthly scope. Seasonal forecasts are monthly and use ECMWF SEAS5 anomalies against that system’s 1991–2020 model climatology.

Large-area and multi-year queries can be slower or sampled. Check returned coverage fields such as base_N, obs_N, num_years, avg_N, or days_with_data before drawing conclusions from sparse records. Forecast evaluation scores can be null when too few verified days are available.