Ranks the best weather windows to climb any peak worldwide, on the sharpest regional model.
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).
This is an MCP App — it requires an MCP host that supports the Apps protocol to render its interactive UI. Compatible hosts include:
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.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"peak-window": {
"command": "npx",
"args": ["-y", "peak-window", "--stdio"]
}
}
}
Then ask Claude something like: "What's the best weather window to climb Großglockner this week?"
npx peak-window # starts on http://localhost:3001/mcp
git clone https://github.com/ByteOverDev/peak-window-mcp-app.git
cd peak-window-mcp-app
npm install
npm run dev # hot reload (UI + server)
npm run serve:stdio # stdio transport
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.
| Provider | Resolution | Coverage | Via |
|---|---|---|---|
| GeoSphere Austria | 2.5 km | Central Europe (5.5–22.1°E, 43–51.8°N) | Direct API |
| MeteoSwiss ICON-CH2 | 2 km | Alpine region (0.5–16.5°E, 43–49.9°N) | Open-Meteo |
| Météo-France AROME | 2.5 km | France & surrounds (-9–14°E, 38–55°N) | Open-Meteo |
| Open-Meteo | ~11 km | Global | Direct API |
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y peak-windowMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-byteoverdev-peak-window": {
"command": "npx",
"args": [
"-y",
"peak-window"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.ByteOverDev/peak-window works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.