wsl-envidat-mcp
Related Servers
Alternatives to wsl-envidat-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Swiss federal geodata -- maps, elevation, geocoding, cadastral extracts, and downloadable datasets via Swisstopo APIs.2028 PyPI9MIT
- AlicenseAqualityDmaintenanceSwiss open data MCP server — transport, weather, geodata, companies, etc,. Zero API keys.76275 npm22MIT
- AlicenseAqualityAmaintenanceMCP server for Switzerland's national metadata catalogue, enabling AI agents to discover datasets, APIs, public services, and publishers through free-text search and structured queries.13MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for querying MeteoSwiss open weather data, providing access to station data, forecasts, radar composites, and more via natural language.45 PyPI44MIT
- AlicenseAqualityFmaintenanceMCP server that connects AI models to Swiss federal geodata, offering tools for spatial queries like layer discovery, coordinate identification, building zones, and terrain heights.9MIT
- AlicenseAqualityAmaintenanceMCP server for Swiss electricity data from three official sources — production mix, consumption forecast, storage-lake fill, consumer price index, tariffs per municipality, and dataset discovery. Zero authentication.1219 PyPIMIT
TDQS
Scored across 10 tools
The general search and domain-specific data tools (wsl_get_avalanche_data, wsl_get_forest_data, wsl_get_naturgefahren_data) overlap with wsl_search, since they all return datasets filtered by topic. However, the domain-specific tools are clearly labeled and serve as convenient shortcuts, while wsl_search is the flexible unified search.
Most tools follow a consistent wsl_<verb>_<object> pattern (wsl_search, wsl_get_dataset, wsl_list_organizations, wsl_get_organization, wsl_list_tags, wsl_get_recent_datasets, wsl_catalog_stats). The domain-specific data tools (wsl_get_avalanche_data, wsl_get_forest_data, wsl_get_naturgefahren_data) deviate slightly by using topic nouns instead of a consistent object type, but the pattern remains readable and predictable.
10 tools is a reasonable size for a catalog search and retrieval server. The count is well within the typical range, though the three domain-specific data tools could arguably be consolidated into one parameterized tool without losing functionality.
The server covers the core EnviDat catalog workflow: search, get details, list organizations, get organization, list tags, recent datasets, and catalog stats. Minor gaps exist, such as no direct dataset download tool or no ability to filter by domain in a dedicated way, but the search tool with domain parameter covers most needs.