How do I use avalanche-org-mcp-server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@avalanche-org-mcp-server What's the current avalanche danger at 40.58, -111.65?" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

avalanche-org-mcp-server

by haydenwade

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

avalanche-org-mcp-server

Publish npm package Publish container image

A minimal Model Context Protocol (MCP) server that wraps the Avalanche.org Public API map-layer endpoints. It lets LLMs look up avalanche danger ratings by location, retrieve raw forecast GeoJSON, and query historic conditions.

Features

Danger lookup by lat/lon — find the avalanche zone for any point and get its current danger rating
Historic danger lookup — same as above, but for a specific past date
Raw map-layer GeoJSON — full FeatureCollection for all avalanche centers, or scoped to one center

Data sourced from the Avalanche.org Public API. See the API docs for details.

Related MCP server: Weather MCP Server

Quick Start

Claude Desktop (npx — recommended)

Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "avalanche-org": {
      "command": "npx",
      "args": ["-y", "avalanche-org-mcp-server"]
    }
  }
}

No install required. Claude will download and run it automatically.

Global npm install

npm install -g avalanche-org-mcp-server

{
  "mcpServers": {
    "avalanche-org": {
      "command": "avalanche-org-mcp-server"
    }
  }
}

Docker

docker pull ghcr.io/haydenwade/avalanche-org-mcp-server:latest

{
  "mcpServers": {
    "avalanche-org": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "ghcr.io/haydenwade/avalanche-org-mcp-server:latest"]
    }
  }
}

From source

git clone https://github.com/haydenwade/avalanche-org-mcp-server.git
cd avalanche-org-mcp-server
npm install
npm run build

{
  "mcpServers": {
    "avalanche-org": {
      "command": "node",
      "args": ["/absolute/path/to/avalanche-org-mcp-server/dist/src/index.js"]
    }
  }
}

Tools

`avalanche_danger_rating_by_point`

Get the current avalanche danger rating for a lat/lon point. Returns the zone the point falls in, or the nearest zone if preferNearest is true.

Parameter	Type	Required	Description
`lat`	number	yes	Latitude in decimal degrees
`lon`	number	yes	Longitude in decimal degrees
`preferNearest`	boolean	no	Fall back to nearest zone if point is outside all polygons (default: `true`)
`centerId`	string	no	Scope search to a specific avalanche center (e.g. `"UAC"`, `"CBAC"`)

Example input:

{ "lat": 40.5763, "lon": -111.7522, "preferNearest": true, "centerId": "UAC" }

{
  "match": "inside_zone",
  "distance_km": 0,
  "distance_miles": 0,
  "zone": {
    "id": "zone-1",
    "name": "Salt Lake",
    "state": "UT"
  },
  "center": {
    "id": "UAC",
    "name": "Utah Avalanche Center",
    "timezone": "America/Denver",
    "link": "https://utahavalanchecenter.org"
  },
  "danger": {
    "level": 3,
    "label": "Considerable",
    "color": "#f1a302"
  },
  "travel_advice": "Dangerous avalanche conditions. Careful snowpack evaluation, cautious route-finding and conservative decision-making essential.",
  "forecast_url": "https://utahavalanchecenter.org/forecast/salt-lake",
  "validity": {
    "start_date": "2026-03-22",
    "end_date": "2026-03-23"
  },
  "warning": null
}

`historic_avalanche_danger_rating_by_point`

Same as above, but for a specific historic date. Returns all the same fields plus day.

Parameter	Type	Required	Description
`lat`	number	yes	Latitude in decimal degrees
`lon`	number	yes	Longitude in decimal degrees
`day`	string	yes	Date in `YYYY-MM-DD` format
`preferNearest`	boolean	no	Fall back to nearest zone (default: `true`)
`centerId`	string	no	Scope to an avalanche center

Example input:

{ "lat": 40.5763, "lon": -111.7522, "day": "2025-02-24", "preferNearest": true }

{
  "match": "inside_zone",
  "distance_km": 0,
  "distance_miles": 0,
  "zone": { "id": "zone-1", "name": "Salt Lake", "state": "UT" },
  "center": { "id": "UAC", "name": "Utah Avalanche Center", "..." : "..." },
  "danger": { "level": 3, "label": "Considerable", "color": "#f1a302" },
  "travel_advice": "Dangerous avalanche conditions. ...",
  "forecast_url": "https://utahavalanchecenter.org/forecast/salt-lake",
  "validity": { "start_date": "2025-02-24", "end_date": "2025-02-25" },
  "warning": null,
  "day": "2025-02-24"
}

`raw_map_layer`

Returns the raw Avalanche.org map-layer GeoJSON FeatureCollection for all avalanche centers.

Parameter	Type	Required	Description
`day`	string	no	Historic date in `YYYY-MM-DD` format

{
  "geojson": {
    "type": "FeatureCollection",
    "features": [ "... full GeoJSON features ..." ]
  }
}

`raw_map_layer_by_avalanche_center`

Returns the raw map-layer GeoJSON FeatureCollection for a single avalanche center.

Parameter	Type	Required	Description
`centerId`	string	yes	Avalanche center ID (e.g. `"CBAC"`, `"NWAC"`, `"UAC"`)
`day`	string	no	Historic date in `YYYY-MM-DD` format

{
  "geojson": {
    "type": "FeatureCollection",
    "features": [ "... full GeoJSON features ..." ]
  }
}

Development

Requires Node.js >= 18.

npm install
npm run build
npm test

To interactively test tools with the MCP Inspector:

npx @modelcontextprotocol/inspector node dist/src/index.js

Project structure

src/
  index.ts          # Entry point — server setup + stdio transport
  tools.ts          # Tool registration
  constants.ts      # API URLs and timeouts
  types.ts          # GeoJSON type definitions
  api/
    mapLayer.ts     # Map-layer fetch + GeoJSON normalization
  lib/
    geometry.ts     # Point-in-polygon, haversine distance, bounds
    dangerLookup.ts # Danger rating lookup logic
    validation.ts   # Date and coordinate validation
test/
  *.test.ts         # Tests (node:test)

Contributing

Fork the repo
Create a feature branch (git checkout -b my-feature)
Make your changes and add tests
Run npm test to make sure everything passes
Open a pull request

License

MIT

Available Tools

4 tools

avalanche_danger_rating_by_pointA

Get the current avalanche danger rating and forecast metadata for the avalanche zone containing a latitude/longitude point. Can fall back to the nearest zone.

Inputs: lat (required), lon (required), centerId, preferNearest.

historic_avalanche_danger_rating_by_pointA

Get the avalanche danger rating and forecast metadata for the avalanche zone containing a latitude/longitude point on a specific historic day (YYYY-MM-DD). Can fall back to the nearest zone.

Inputs: day (required), lat (required), lon (required), centerId, +1 more.

raw_map_layerA

Return the raw Avalanche.org map-layer GeoJSON FeatureCollection for all avalanche centers. Supports an optional historic day (YYYY-MM-DD).

Inputs: day.

raw_map_layer_by_avalanche_centerA

Return the raw Avalanche.org map-layer GeoJSON FeatureCollection for a specific avalanche center ID. Supports an optional historic day (YYYY-MM-DD).

Inputs: centerId (required), day.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored 2026-09-13 09:45 across 4 tools

Disambiguation4/5

The four tools split cleanly along two axes: current vs historic ratings (tools 1 vs 2) and all-centers vs single-center raw layers (tools 3 vs 4). The main potential confusion is between the point-based rating tools and the map-layer tools, since raw_map_layer also accepts a historic day, but their output intent (formatted rating vs raw GeoJSON) differs enough to keep them distinct.

Naming Consistency4/5

All names use consistent snake_case with descriptive suffixes (_by_point, _by_avalanche_center) and clear domain prefixes (avalanche_danger_rating, historic_, raw_map_layer). It is not a strict verb_noun convention, but the modifiers are applied predictably across the set, so an agent can infer related tools.

Tool Count4/5

Four tools is a tight, well-scoped surface for a narrow domain (avalanche danger lookups). Each tool covers a distinct query dimension, though the set sits at the low end and one could argue a couple more (e.g. by-center rating) would round it out.

Completeness3/5

The surface covers current/historic point ratings and raw map layers for all or a single center, but there is no direct way to query a formatted danger rating by avalanche center ID, nor to list available centers/zones. Raw GeoJSON partially compensates, but some lookup paths dead-end.

Maintenance

ActivityInactive

ResponsivenessOutdated data

Resources

Related MCP Connectors

Weather & Geo Intel MCPA
io.github.selflabbs
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
Weather Services Location Services
2
https://weather.selflabbs.com/mcp
Weather & Geo Intel MCPA
com.datakoot
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
Weather Services Location Services
61
https://weather.datakoot.com/mcp
weather-mcp-serverA
com.thenextgennexus
Current weather and forecast lookup as an agent tool.
Weather Services Location Services
2
https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/weather-mcp-server/mcp
WeatherA
io.github.Thx93
US NWS weather alerts and 5-day forecasts for AI agents. $0.01 per call.
Weather Services Government Data
311
https://agent-evidence.thx93.dev/weather/mcp

Related MCP Servers

Weather MCP Server
gaurigshankar
A
license
B
quality
D
maintenance
Enables AI assistants to access real-time US weather forecasts and alerts through the National Weather Service API.
Updated a year ago (2025-07-17 01:37 UTC)
2
8 npm
MIT
Weather MCP Server
Weather Services Search
aitiwari
F
license
B
quality
D
maintenance
Provides real-time US weather alerts and forecasts by integrating with the National Weather Service API. It enables AI assistants to fetch state-specific alerts and detailed local forecasts using geographic coordinates.
Updated 2 years ago (2025-03-23 17:08 UTC)
2
1
-
Aviation Weather MCP Server
Weather Services Travel & Transportation
zealoushacker
A
license
Not graded
quality
D
maintenance
Provides access to aviation weather data from aviationweather.gov, enabling LLMs to fetch and analyze METAR, TAF, PIREPs, AIRMETs, and other aviation weather information.
Updated a year ago (2025-06-16 01:03 UTC)
20 npm
7
MIT
avymcp
Weather Services Open Data
scott-brereton
A
license
Not graded
quality
D
maintenance
Provides avalanche forecasts, danger ratings, and field observations for US avalanche centers, Canadian regions, and Quebec's Chic-Chocs via natural language queries.
Updated 7 months ago (2026-04-10 12:37 UTC)
1
MIT

avalanche-org-mcp-server

Features

Quick Start

Claude Desktop (npx — recommended)

Global npm install

Docker

From source

Tools

avalanche_danger_rating_by_point

historic_avalanche_danger_rating_by_point

raw_map_layer

raw_map_layer_by_avalanche_center

Development

Project structure

Contributing

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Weather MCP Server

Weather MCP Server

Aviation Weather MCP Server

avymcp

`avalanche_danger_rating_by_point`

`historic_avalanche_danger_rating_by_point`

`raw_map_layer`

`raw_map_layer_by_avalanche_center`