windy-webcams
A Model Context Protocol (MCP) server that provides access to the Windy Webcam Public API, enabling AI agents to search and retrieve information about live webcams from around the world.
claude mcp add --transport stdio cyreslab-ai-windy-webcams-mcp-server npx windy-webcam-mcp-server \ --env WINDY_API_KEY="your-api-key-here"
How to use
The windy-webcam MCP server provides a REST-like set of tools to interact with the Windy Webcams Public API through the MCP (Model Context Protocol) framework. It exposes capabilities such as searching webcams, retrieving detailed webcam data, grouping webcams by location or category, and exporting webcam datasets. You can integrate these tools into your MCP client to build AI workflows that discover, filter, and fetch live webcam information for visualization, monitoring, or analysis. The server handles indexing, caching, rate limiting, and error handling to ensure reliable responses for agent-based tasks.
To use it, configure an MCP client to connect to the windy-webcam MCP server. A typical client setup uses npx to run the server package, and you’ll provide your Windy API key via environment variables. The available tools include search_webcams, get_webcam, get_webcams_by_location, get_webcams_by_category, get_nearby_webcams, get_map_clusters, get_categories, get_countries, get_regions, get_continents, and export_all_webcams. Each tool accepts filters and parameters described in the README, such as geographic constraints, categories, and ordering, enabling precise queries and bulk exports when needed.
How to install
Prerequisites:
- Node.js 18 or higher
- Windy API key (obtain at https://api.windy.com/keys)
Install from npm:
npm install windy-webcam-mcp-server
From source:
git clone <repository-url>
cd windy-webcam-mcp-server
npm install
npm run build
Configure environment variable (example):
export WINDY_API_KEY="your-api-key-here"
Or use a .env file with:
WINDY_API_KEY=your-api-key-here
Verify installation by starting locally (example):
npx windy-webcam-mcp-server
Additional notes
Tips and notes:
- You must supply a valid Windy API key (WINDY_API_KEY) to access the Windy Webcams data.
- The MCP client example uses npx to run the windy-webcam-mcp-server; you can also wire the server into a longer-running process or run it via your preferred MCP host.
- Be mindful of rate limits; the server includes rate limiting and exponential backoff logic to handle API quotas.
- You can export data via export_all_webcams for bulk retrieval; adjust format as needed (JSON is supported).
- If you encounter authentication or quota errors, verify that WINDY_API_KEY is correct and that your Windy account has the necessary permissions.
- For local development, you can run npm run dev to test in development mode if provided by the package, and npm test to run tests.
- The API supports a rich set of filters (country, region, continent, category, bbox,Nearby, etc.) and supports mapping/ clustering features for visualization applications.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.