Avalanche Org MCP Server

MCP server for the Avalanche.org Public API map-layer endpoints. That is what the avalanche org mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

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

• 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

The tools it exposes

The server publishes 4 tools. What each one is for:

• 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
• historic_avalanche_danger_rating_by_point — Same as above, but for a specific historic date. Returns all the same fields plus day
• raw_map_layer — Returns the raw Avalanche.org map-layer GeoJSON FeatureCollection for all avalanche centers
• raw_map_layer_by_avalanche_center — Returns the raw map-layer GeoJSON FeatureCollection for a single avalanche center

Getting it running

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Avalanche Org's toolset — avalanche_danger_rating_by_point, historic_avalanche_danger_rating_by_point, raw_map_layer and 1 more — is a fair guide to whether it matches your workflow. It is maintained by haydenwade; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Avalanche Org's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.