npm peak-windowstdioMITupdated 3mo ago
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 can you do with peak window?
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:
{
"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?"
HTTP server
npx peak-window # starts on http://localhost:3001/mcp
Development
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
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
| 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 |
Install
Add peak window to your client. Pick the one you use.
claude mcp add peak-window -- npx -y peak-windowcodex mcp add peak-window -- npx -y peak-windowamp mcp add peak-window -- npx -y peak-window{
"mcpServers": {
"peak-window": {
"command": "npx",
"args": [
"-y",
"peak-window"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"peak-window": {
"command": "npx",
"args": [
"-y",
"peak-window"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"peak-window","command":"npx","args":["-y","peak-window"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"peak-window": {
"command": "npx",
"args": [
"-y",
"peak-window"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"peak-window": {
"command": "npx",
"args": [
"-y",
"peak-window"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"peak-window": {
"command": "npx",
"args": [
"-y",
"peak-window"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"peak-window": {
"type": "local",
"command": "npx",
"args": [
"-y",
"peak-window"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"peak-window": {
"command": {
"path": "npx",
"args": [
"-y",
"peak-window"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y peak-windowRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation18/25
- Maintenance13/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 93 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.0.2Latest | May 29, 2026 |