Query point/time-series weather parameters from the Meteomatics API using OAuth token authentication
domain: api.meteomatics.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request an OAuth access token via GET https://login.meteomatics.com/api/v1/token using HTTP Basic auth with your account username/password.
Attach the returned bearer token to subsequent requests to api.meteomatics.com instead of sending credentials on every call.
Build a request URL combining ISO 8601 datetime (or range/step), parameter names (e.g. t_2m:C), and location (lat,lon or postal code) per Meteomatics' path-based query syntax.
Choose a response format (JSON, CSV, netCDF, PNG) via the request path or Accept header.
Refresh the OAuth token before it expires rather than re-authenticating on every request.
Known gotchas
The OAuth token is short-lived (on the order of a few hours) — long-running services must implement token refresh logic, not just a one-time fetch.
Parameter names encode both the measurement and unit (e.g. t_2m:C vs t_2m:F) — an incorrect unit suffix silently returns differently scaled values, not an error.
Basic-auth-per-request and OAuth-token approaches are both supported; mixing them inconsistently across a codebase can cause confusing auth failures.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?