Schema | weather-mcp

weather-mcp

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`WEATHER_IMG_TTL`	No	Card link lifetime in seconds.	600
`WEATHER_OUT_DIR`	No	Directory where card PNGs are written (served at /img/<token>, TTL-GC'd).	out
`WEATHER_LANGUAGE`	No	Geocoding language.	en
`WEATHER_MCP_TOKEN`	No	Bearer token required by clients on streamable-http when set.
`WEATHER_PUBLIC_URL`	No	Browser-reachable base URL; enables the image card link (HTTP only).
`WEATHER_DEFAULT_LAT`	No	Fallback latitude when a call gives neither place nor coords.
`WEATHER_DEFAULT_LON`	No	Fallback longitude when a call gives neither place nor coords.
`WEATHER_DEFAULT_NAME`	No	Fallback place name when a call gives neither place nor coords (default is Quito, city-level; not home coordinates).
`WEATHER_HTTP_TIMEOUT`	No	HTTP timeout in seconds.	15

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
get_forecastA	Current conditions + an N-day daily forecast for a place. Returns the structured DATA in the text block (for you to answer from) and a weather card as `card_markdown`: include that markdown in your reply, unchanged, so the user sees the card. Args: location: a place name ("Quito", "Berlin, DE"); geocoded via Open-Meteo. Ignored if latitude+longitude are given. With neither, the server's default location is used. latitude/longitude: exact coordinates (both required together) — overrides `location`. days: number of daily-forecast days, 1..16 (default 3). units: "metric" (°C, km/h, mm — default) or "imperial" (°F, mph, in). language: language for geocoding the place name (default from config, e.g. "en"/"es"). card: "auto" (default: an image link when this server can serve one, else a text card), "image" (image link; falls back to text when no link can be served), "text" (a monospace card in a ```text fence, for terminals or clients that don't show images) or "none".
geocodeA	Resolve a place name to candidate coordinates (name, admin region, country, lat/lon, timezone). Use it to disambiguate before get_forecast, or when a user names an ambiguous place. `Args: query: the place name to search for. count: max candidates to return (default 5). language: result language (default from config).`

get_forecastA

Current conditions + an N-day daily forecast for a place. Returns the structured DATA in the text block (for you to answer from) and a weather card as card_markdown: include that markdown in your reply, unchanged, so the user sees the card.

    Args:
        location: a place name ("Quito", "Berlin, DE"); geocoded via Open-Meteo. Ignored if
            latitude+longitude are given. With neither, the server's default location is used.
        latitude/longitude: exact coordinates (both required together) — overrides `location`.
        days: number of daily-forecast days, 1..16 (default 3).
        units: "metric" (°C, km/h, mm — default) or "imperial" (°F, mph, in).
        language: language for geocoding the place name (default from config, e.g. "en"/"es").
        card: "auto" (default: an image link when this server can serve one, else a text card),
            "image" (image link; falls back to text when no link can be served), "text" (a monospace
            card in a ```text fence, for terminals or clients that don't show images) or "none".

geocodeA

Resolve a place name to candidate coordinates (name, admin region, country, lat/lon, timezone). Use it to disambiguate before get_forecast, or when a user names an ambiguous place.

    Args:
        query: the place name to search for.
        count: max candidates to return (default 5).
        language: result language (default from config).

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored 2026-10-17 07:05 across 2 tools

Disambiguation5/5

get_forecast and geocode have clearly distinct purposes: one fetches weather data, the other resolves place names to coordinates. The get_forecast description even explains when to use geocode first to disambiguate, so there is no realistic misselection risk.

Naming Consistency4/5

get_forecast follows a verb_noun pattern, while geocode is a bare verb with no noun. Both are snake_case and readable, so the deviation is minor rather than confusing.

Tool Count3/5

Two tools is thin for a weather server; a full forecast surface typically warrants separate helpers (current conditions, hourly, alerts, history). The set is coherent but minimal, and geocode exists mainly as a support tool for get_forecast.

Completeness4/5

The forecast tool covers current conditions plus a configurable multi-day daily forecast with units, language, and card rendering, which is the core weather workflow. Gaps remain for hourly forecasts, historical/archive data, and severe-weather alerts, but agents can work around these.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers