
Peak Window
io.github.ByteOverDevPublished by GitHub account ByteOverDevv1.0.2Updated Oct 24, 2026
Ranks the best weather windows to climb any peak worldwide, on the sharpest regional model.
Overview
A local MCP server that ranks the best upcoming weather windows for climbing a peak, using the highest-resolution regional forecast available.
- What you can do
- Fetch hourly forecasts for coordinates: temperature, precipitation, wind, gusts, cloud cover and snow line, choosing the sharpest model for the region and falling back on provider failure to stay resilient. Correct temperatures to summit elevation using lapse rate and model terrain. Score each hour against alpine climbing thresholds and identify contiguous good-weather windows. Return scored hours, top windows and a full time-series payload, optionally rendered as an interactive chart UI in hosts that support the Apps protocol.
- When to use it
- Useful when planning an alpine climb or ascent and you want an assistant to compare forecast windows for a specific peak or trailhead, especially in Central Europe, the Alps or France where high-resolution models apply.
- Requirements
- Runs locally over stdio (or SSE/HTTP) via the npm package peak-window, so Node.js and npx are needed. Network access to the weather providers (GeoSphere Austria, Open-Meteo, MeteoSwiss and Météo-France data via Open-Meteo). The interactive UI needs an MCP host that supports the Apps protocol; otherwise text output is returned. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Peak Window in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
PeakWindow MCP App
An MCP App that analyzes upcoming weather at alpine peaks and trailheads worldwide, ranking the best windows for climbing and ascent. Uses the best available forecast model for each region: GeoSphere Austria AROME (2.5 km) for Central Europe, MeteoSwiss ICON-CH2 (2 km) for the Alpine region, Météo-France AROME (2.5 km) for France, and Open-Meteo globally (~11 km).
What it does
- Fetches hourly forecasts (temperature, precipitation, wind, gusts, cloud cover, snow line) from the best available provider for the requested coordinates
- Automatically selects the highest-resolution model: GeoSphere (2.5 km, Central Europe), MeteoSwiss (2 km, Alpine region), Météo-France (2.5 km, France), or Open-Meteo (~11 km, global)
- Falls through to the next provider on API failure for resilience
- Lapse-corrects temperatures to summit elevation using model terrain derived from surface pressure (-6.5 °C/km)
- Scores each hour against alpine climbing thresholds and identifies contiguous good-weather windows
- Serves an interactive UI (React, uPlot charts) as an MCP App resource with horizon tape, mountain profile, and Ventusky-style chart panels
Requirements
This is an MCP App — it requires an MCP host that supports the Apps protocol to render its interactive UI. Compatible hosts include:
- Claude Desktop (macOS / Windows)
- ChatGPT (via OpenAI Apps SDK)
- Any chat client implementing the MCP Apps spec
The server runs as a standard MCP server over stdio or SSE. The rich UI (charts, horizon tape, mountain profile) renders inline in any compliant host. Without one you still get the scored text output.
Live UI demo — fetches real forecasts in the browser; pick any peak to see its scored windows and real DEM silhouette.
Setup
Claude Desktop
Add to your claude_desktop_config.json:
Then ask Claude something like: "What's the best weather window to climb Großglockner this week?"
HTTP server
Development
MCP tool
peak-window — provide lat, lon, and optionally peakName and summitElevationM. Returns scored hours, top weather windows, and a full time-series payload rendered by the embedded UI.
Data sources
Source: README.md at commit e24dcb0
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts