mcp-weather-server
Related Servers
Alternatives to mcp-weather-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Claude, Codex, and GitHub Copilot to query WHOOP recovery, sleep, HRV, strain, and workouts through read-only tools, including daily summaries, personal baselines, trends, and HYROX/triathlon performance insights.4 npmMIT
- AlicenseAqualityBmaintenanceEnables Claude, Cursor, or any MCP client to query your own recovery scores, sleep, strain cycles, workouts, profile, and body measurements through every WHOOP API v2 read endpoint. Tools return records exactly as WHOOP sends them, with paging and date-range filtering, and refresh tokens automatically after a one-time login.113 npm1MIT
- FlicenseNot gradedqualityCmaintenanceExposes five tools that let Claude query training data from the intervals.icu API directly, covering weekly volume, fitness/fatigue/form, recent activities with per-rep detail, wellness metrics, and pace-at-heart-rate trends, with in-memory caching of upstream responses.-
- FlicenseAqualityDmaintenanceExposes the Timely.mn v3 time-attendance API as MCP tools for Claude and other clients, allowing queries for company-wide attendance, employee profiles, and attendance reports.4-
- AlicenseNot gradedqualityCmaintenanceExposes the MyGeotab API as AI-callable tools, letting Claude query fleet data, device status, trips, tachograph files, fuel, diagnostics, faults, and driver information across multiple customer databases through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceExposes the Hevy workout API to Claude, enabling users to manage workouts, routines, exercise templates, body measurements, and user info via natural language.3,367 npmMIT
TDQS
Scored across 3 tools
Each tool targets a distinct temporal or comparative view (current, forecast, multi-city comparison), and descriptions make the boundaries explicit. compare_cities partially overlaps with get_current applied to several cities, but the added ranking output justifies its separate existence.
All three tools follow the same snake_case verb_noun pattern (get_current, get_forecast, compare_cities). The verbs are accurate and predictable, so an agent can guess a tool's intent from its name.
Three tools is on the lean side, but each covers a genuinely distinct weather-query pattern and nothing feels redundant. It sits at the low edge of a well-scoped surface rather than being thin to the point of uselessness.
The core weather workflows (current conditions, daily outlook, multi-city comparison) are covered with no dead ends. Gaps exist around hourly breakdowns, historical data, alerts, and city/geocoding lookup, but agents can work around these for typical queries.