Meltema Weather
Server Details
Multi-model weather forecasts: point series, model scoreboard, and gridded fields. No auth.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
5 toolscompare_modelsCompare models at a point (scoreboard)Inspect
Sample one variable at a point across many models and summarize per-time cross-model spread (min/max/mean/spread). Sources default to every live source carrying the variable; pass a comma-separated sources to pin the set. Canonical variable ids: t2m = 2 m air temperature (K), u10 = 10 m U wind component (m/s), v10 = 10 m V wind component (m/s), wind_speed = 10 m wind speed, derived hypot(u10, v10) (m/s), tp = total precipitation over the step (kg m-2, mm-equivalent), tcc = total cloud cover (fraction 0-1), ssrd = surface downward shortwave radiation (W m-2), msl = mean sea level pressure (Pa) (availability varies by source — see GET /v1/sources). Common aliases are accepted case-insensitively and normalized to these ids: temperature/temperature_2m/temp -> t2m, wind/windspeed/wind_speed_10m -> wind_speed, u10m/v10m -> u10/v10, precip/precipitation/rain -> tp, cloud/clouds/cloud_cover -> tcc, solar/radiation/shortwave -> ssrd, pressure/mslp/sea_level_pressure -> msl. The output series always carries the canonical id.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | Latitude, degrees north. | |
| lon | Yes | Longitude, degrees east. | |
| sources | No | Comma-separated `source_id`s; omit to use every live source with the variable. | |
| variable | Yes | A single variable id, e.g. t2m, tp, tcc, ssrd (or an alias like temperature_2m/precipitation — normalized to the canonical id). | |
| init_time | No | Run init (UTC ISO 8601); omit for each source's latest run. |
Output Schema
| Name | Required | Description |
|---|---|---|
| lat | Yes | |
| lon | Yes | |
| models | Yes | |
| missing | Yes | Requested/eligible sources with no data for this variable. |
| variable | Yes | |
| consensus | Yes | Per-valid_time cross-model spread, ascending. |
describe_gridDescribe a gridded fieldInspect
Geometry (grid spec + available leads + units) of a gridded field, plus the exact /v1/grid URL and the recipe to decode the raw uint16 bytes. Omit init_time for the latest run.
| Name | Required | Description | Default |
|---|---|---|---|
| variable | No | Variable id, e.g. `t2m` or composite `wind10m`. | t2m |
| init_time | No | Run init (UTC ISO 8601); omit for the latest run. | |
| source_id | Yes | A `source_id` from list_sources. |
Output Schema
| Name | Required | Description |
|---|---|---|
| grid | Yes | |
| kind | Yes | 'scalar' or 'vector' (vector = u plane then v plane). |
| units | Yes | |
| decode | Yes | How to turn the uint16 body into physical values. |
| variable | Yes | |
| fetch_url | Yes | GET this for the raw uint16 field (add ?lead_hours=&stride=). |
| init_time | Yes | |
| source_id | Yes | |
| lead_hours | Yes | Every available lead of this run. |
list_runsList stored runsInspect
Stored run init times for a source, newest first (UTC ISO 8601). Pass one to pin a tool to that run.
| Name | Required | Description | Default |
|---|---|---|---|
| source_id | Yes | A `source_id` from list_sources, e.g. `gfs`. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_sourcesList forecast sourcesInspect
Every public forecast source with live-data status, servable variables, cadence and licensing attribution. This is the live enum of source_id accepted by the other tools.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
point_forecastPoint forecastInspect
Full forecast horizon of one model at a single point (bilinear grid sample). source_id is OPTIONAL: omit it and a sensible live source is chosen (prefers gfs, then ifs_open) and returned as source_id. Omit init_time for the latest run; omit variables for all stored variables plus derived wind_speed. Canonical variable ids: t2m = 2 m air temperature (K), u10 = 10 m U wind component (m/s), v10 = 10 m V wind component (m/s), wind_speed = 10 m wind speed, derived hypot(u10, v10) (m/s), tp = total precipitation over the step (kg m-2, mm-equivalent), tcc = total cloud cover (fraction 0-1), ssrd = surface downward shortwave radiation (W m-2), msl = mean sea level pressure (Pa) (availability varies by source — see GET /v1/sources). Common aliases are accepted case-insensitively and normalized to these ids: temperature/temperature_2m/temp -> t2m, wind/windspeed/wind_speed_10m -> wind_speed, u10m/v10m -> u10/v10, precip/precipitation/rain -> tp, cloud/clouds/cloud_cover -> tcc, solar/radiation/shortwave -> ssrd, pressure/mslp/sea_level_pressure -> msl. The output series always carries the canonical id.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | Latitude, degrees north. | |
| lon | Yes | Longitude, degrees east (normalized to [-180,180)). | |
| init_time | No | Run init (UTC ISO 8601); omit for the latest run. | |
| source_id | No | A `source_id` from list_sources. OPTIONAL — omit to use a sensible live default (prefers gfs, then ifs_open); the chosen source is echoed as the result's `source_id`. | |
| variables | No | Comma-separated variable ids (t2m, u10, v10, wind_speed, tp, tcc, ssrd, msl); omit for all + wind_speed. Common aliases like temperature_2m/windspeed/precipitation/cloud/solar/pressure are accepted (case-insensitive) and normalized to the canonical id. |
Output Schema
| Name | Required | Description |
|---|---|---|
| lat | Yes | |
| lon | Yes | Longitude normalized into [-180, 180). |
| series | Yes | |
| init_time | Yes | Run init time (UTC ISO 8601) actually sampled. |
| source_id | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!