big-sky — PeakCam Snow MCP Resource
big-sky
is one of 148 resources on the
PeakCam Snow
MCP server. Connect the server and your client can attach it as context.
by client
How to attach big-sky from your client
- Claude Code PeakCam Snow Resource/big-sky run in your project directory
- Claude Desktop PeakCam Snow Resource/big-sky ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PeakCam Snow Resource/big-sky ~/.cursor/mcp.json
- VS Code PeakCam Snow Resource/big-sky .vscode/mcp.json
- Zed PeakCam Snow Resource/big-sky ~/.config/zed/settings.json
- Windsurf PeakCam Snow Resource/big-sky ~/.codeium/windsurf/mcp_config.json
- Cline PeakCam Snow Resource/big-sky ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PeakCam Snow Resource/big-sky ~/.gemini/settings.json
- Grok PeakCam Snow Resource/big-sky .mcp.json (in your project root)
- ChatGPT PeakCam Snow Resource/big-sky Settings → Connectors → Advanced → Developer mode
- Claude.ai PeakCam Snow Resource/big-sky Settings → Connectors → Add custom connector
- LangChain PeakCam Snow Resource/big-sky pip install langchain-mcp-adapters
Other resources on this server
- 49-degrees-north
- alta
- angel-fire
- antillanca
- arapahoe-basin
- arizona-snowbowl
- aspen-snowmass
- attitash
- batea-mahuida
- bear-mountain
- bear-valley
- beaver-creek
- belleayre
- big-white
- bogus-basin
- bolton-valley
- boreal
- boyne-mountain
- breckenridge
- bretton-woods
- brian-head
- bridger-bowl
- brighton
- brundage
- burke-mountain
- camelback
- cannon
- caviahue
- cerro-bayo
- cerro-castor
- cerro-catedral
- cerro-mirador
- cerro-perito-moreno
- chapelco
- china-peak
- copper-mountain
- corralco
- cranmore
- crested-butte
- crystal-mountain
Read from the server itself, by connecting to it and calling resources/list on 18 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.