AccuWeather Core Weather API + MCP vs Meteomatics Weather API

AccuWeather Core Weather API + MCP

Official hosted MCP server, 26 read-only tools, same key as the REST API. Terms forbid using the data to train, validate or otherwise inform any AI system.

Meteomatics Weather API

A public OpenAPI file, a hosted MCP server whose nine tools are all marked read-only, a published SLA with compensation and ISO 27001 certification suit company use. Access needs a sales contract, with no public price, free tier or self-serve signup found, no status page, and REST calls that authenticate with a username and password.

AccuWeather Core Weather API + MCP

1. Cache location keys. They don't change, and the lookup is the call worth saving
2. Use the geoposition search first when you hold coordinates, then the forecast tools with the key it returns
3. Send the key as a Bearer header, not in the MCP URL, so it stays out of logs
4. Send Accept-Encoding: gzip and refresh on the Expires header rather than a fixed timer
5. Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks

Meteomatics Weather API

1. Ask the account owner for credentials first. There is no signup, and both the REST API and the MCP server need a Meteomatics account with API access
2. Build REST URLs as validdatetime/parameters/location/format, for example 2026-10-08T00:00:00Z/t_2m:C/52.52,13.40/json. Parameter names carry their unit after a colon
3. Keep each query to 10 locations and 10 parameters unless the contract says otherwise, and use POST when a GET URL passes 2,000 characters
4. Send credentials or the token in the Authorization header. Avoid the documented access_token query parameter, which puts the token in URLs and logs
5. Read /user_stats_json before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent
6. Treat reserved values such as -888 and -999 as invalid or missing data, and shrink the request when a 408 arrives after the 300-second timeout