WEATHER LOOKUP / Model Context Protocol a Series of LF Projects, LLC
MCP quickstart weather server
Looks up US National Weather Service alerts and a five-period forecast over stdio.
“A simple MCP weather server”
01 / THE REASONING
Why this made the selection.
- The server speaks stdio and registers get_alerts and get_forecast. get_alerts requests only api.weather.gov. An empty feature list becomes an empty array.
- Missing alert fields are rewritten to placeholder sentences. The file writes no local file and contains no credential.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- weather-server-python/weather.py
- weather-server-python/pyproject.toml
- weather-server-python/README.md
- LICENSE
- README.md (repository root)
Our findings
- pyproject.toml names version 0.1.0, requires Python 3.10 or later, and depends on httpx2, mcp[cli], and pydantic. The script entry is weather:main. weather.py calls mcp.run with transport stdio.
- The root LICENSE describes a transition from MIT to Apache-2.0, CC-BY-4.0 for documentation other than specifications, and then the MIT text. The MIT copyright line is Copyright (c) 2024-2025 Model Context Protocol a Series of LF Projects, LLC. Apache-2.0 is not the only licence in that file.
- The server README says both tools declare an output schema and return structured_content, and that get_alerts returns a top-level JSON array, which protocol revision 2026-07-28 is the first to allow. weather.py builds that array as a RootModel over a list.
- Neither the server README nor the root README at this commit contains a JSON client-configuration block, so no configExample is recorded. The README runs the server with uv run weather.py or through the repository's client examples.
- Health on 2026-10-13: the repository is not archived. GitHub reports its licence as NOASSERTION; the root LICENSE at this commit describes a licensing transition from the MIT License to the Apache License.
Not established by this review
- The server was not started.
- No request was sent to api.weather.gov.
- uv.lock was not audited. uv run was not executed.
- The protocol and SDK URLs named in the comments were not opened.
- Sibling language servers and the client examples were not opened.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Read the server at the reviewed commit. No install command is published for this record.
- The README shows uv run weather.py. That command was not executed.
Before you start
- Python 3.10 or later
- An MCP client that can launch a stdio process you choose
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Quickstart weather server ↗Checked
https://github.com/modelcontextprotocol/quickstart-resources/blob/2912bb30785c7702a2f9abfab783e9140aa7246b/weather-server-python/weather.py
Supports: stdio transport, alert placeholders, five-period forecast
- Weather server manifest ↗Checked
https://github.com/modelcontextprotocol/quickstart-resources/blob/2912bb30785c7702a2f9abfab783e9140aa7246b/weather-server-python/pyproject.toml
Supports: version 0.1.0, Python 3.10, declared dependencies
- Weather server README ↗Checked
https://github.com/modelcontextprotocol/quickstart-resources/blob/2912bb30785c7702a2f9abfab783e9140aa7246b/weather-server-python/README.md
Supports: two tools, stdio transport, structured content and protocol revision 2026-07-28, uv run weather.py
- Licence file ↗Checked
https://github.com/modelcontextprotocol/quickstart-resources/blob/2912bb30785c7702a2f9abfab783e9140aa7246b/LICENSE
Supports: MIT terms, Apache-2.0 transition, CC-BY-4.0 documentation note