MCP server · REST API · feeds · no key
https://www.peakcam.io/api/mcp1 · What you get
The server is io.peakcam/snow, speaking stateless Streamable HTTP with no authentication and no legacy SSE endpoint; it negotiates protocol revisions 2026-07-28, 2025-11-25 and 2025-06-18, and a plain browser GET on the URL returns a small JSON description of itself. Every tool is annotated read-only and returns a short, dated markdown answer plus a structured document that matches the public API wire types. Each snow number carries its source and time, so the assistant can say “6 in in 24 h, SNOTEL-measured, 05:00 MST” instead of a bare figure.
| Tool | What it answers |
|---|---|
| search_resorts | Find a resort by name, fragment or region and get its slug with a one-line snow summary. |
| get_resort_conditions | The latest snow report for one resort, every number labelled with its source and time, plus the page URL to cite. |
| get_resort_cams | The resort's webcams as links with live, down or unchecked health. Frames are never returned inline. |
| find_powder | Rank resorts by new snow in the last 24 or 48 hours, by state, with a measured-only option. |
| compare_resorts | Side-by-side snow, season status and cam counts for two to six resorts. |
| get_forecast | Five-day National Weather Service forecast for US resorts; Canada and the Andes return available: false. |
| get_snow_history | Daily depth, snow water equivalent, precipitation and temperatures for the last 1 to 30 days at the resort's station. |
| get_opening_dates | Season opening and closing dates with open, closed or unknown status, soonest first. |
| peakcam://resorts/{slug} | Resource: each resort as markdown, the same document as its /index.md page. Listed and completable by slug. |
2 · Set it up
Paid plans can add a custom connector. The link below opens the dialog with the name and URL filled in.
Add PeakCam to ClaudeOne command registers the server for the current project, or add --scope user for everywhere.
claude mcp add --transport http peakcam https://www.peakcam.io/api/mcpCheck with claude mcp list; the tools appear as mcp__peakcam__*.
Add the server to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"peakcam": {
"url": "https://www.peakcam.io/api/mcp"
}
}
}The same object works in Windsurf, Zed, VS Code and any client that reads an mcpServers map with a url entry.
Both expose a custom connector field on some plans: paste the endpoint as the server URL and leave authentication empty. Where the field is missing, the markdown and REST alternates below work as plain web fetches.
An agent that should wake up when it snows does not need MCP. Register a webhook on manage alerts and webhooks: each powder alert is POSTed as JSON, signed per Standard Webhooks (webhook-id, webhook-timestamp, webhook-signature; the secret shown once starts with whsec_).
hermes webhook subscribe --name peakcam-powder \
--secret "$PEAKCAM_WEBHOOK_SECRET" \
--on powder.alert "notify 'Powder: {{resort.name}} {{inches}}\" ({{kind}}) {{url}}'"Hermes prints the URL it listens on; paste it into the webhook field. The payload:
{
"type": "powder.alert",
"resort": {
"slug": "alta",
"name": "Alta Ski Area",
"url": "https://www.peakcam.io/resorts/alta"
},
"inches": 11,
"kind": "measured",
"measuredAt": "2026-12-01T12:30:00.000Z",
"url": "https://www.peakcam.io/resorts/alta",
"threshold": 8
}For agents that poll instead (a Grok routine, a cron job), read the per-resort Atom feed below; no token needed. Receivers wanting exactly-once should key on resort.slug + measuredAt.
3 · Try it
“Where did it snow most in the last 24 hours, measured only?”
“Which Colorado resorts picked up more than 6 inches over the weekend?”
“What are conditions like at Alta right now, and is the base deeper than last week?”
“Show me Breckenridge's webcams.”
“Compare Vail, Breckenridge and Keystone for a trip this weekend.”
“When does Mammoth open this season? What about the rest of California?”
4 · Provenance
Where a resort has an assigned NRCS SNOTEL or SCAN station (most of the western United States), snow numbers are that station’s telemetry, quality-controlled and synced every six hours. Resorts without one (Canada, most of the East, the Andes) carry Open-Meteo model estimates and say so in every response. Forecasts are the National Weather Service for US resorts. Webcams belong to their operators; PeakCam links to them and reports whether the last probe found them live. Season dates come from the resort when confirmed and from third-party projections otherwise. The methodology page has the quality-control rules and the freshness guarantees.
5 · Without MCP
Every surface is anonymous, CORS-open, cached fifteen minutes and carries X-Attribution and Link author and license headers. Swap breckenridge for any slug from the resort list.