Weather Alerts & Forecast

io.github.rsys-vtiwariPublished by GitHub account rsys-vtiwariv0.1.0Updated Nov 3, 2026

US NWS alerts by state and short-term (next 5 periods) point forecasts.

The publisher's own server: AlertsBar

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Local MCP server that gives an assistant US National Weather Service alerts by state and short-term point forecasts by coordinates.

What you can do
  • Fetch active NWS weather alerts for a US state by two-letter state code
  • Fetch a short-term point forecast for the next five periods from latitude and longitude
When to use it
Useful when you want an assistant to check current US weather alerts or a brief forecast for a location, for example while planning travel or outdoor work inside the United States.
Requirements
Runs locally as a Python process over stdio; the README installs it with pip and launches it with python -m weather.weather. Needs network access to the public NWS API. No accounts, API keys, environment variables or headers are declared.
Before you install
Coverage is limited to US National Weather Service data, so non-US locations are not supported. The README asks users to respect the public API's usage guidelines and rate limits. No write actions or credentials are involved.

Installation

In SourceWeft

  1. Open Weather Alerts & Forecast in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Weather MCP Server

An MCP server that provides:

  • Active US National Weather Service (NWS) alerts by two-letter state code
  • Short-term point forecasts (next 5 periods) for latitude/longitude coordinates

Data is sourced from the public NWS API at https://api.weather.gov.

Tools

ToolDescriptionInputs
get_alertsFetch active NWS alerts for a US statestate (string, two-letter code)
get_forecastFetch short-term forecast (next 5 periods) for coordinateslatitude (number), longitude (number)

Usage (Local)

Install dependencies:

powershell
pip install .

Run the MCP server (stdio transport):

powershell
python -m weather.weather

Your MCP client should be configured to launch the server via the package entrypoint or the above module path.

Server JSON Summary

See server.json for registry metadata including name, version, tools, and entrypoint configuration.

Publishing Steps (Overview)

  1. Authenticate with publisher (GitHub namespace):
    powershell
    mcp-publisher login github
  2. Create and push repo to GitHub (see steps below).
  3. (Optional) Publish to PyPI if distributing as a package.
  4. Publish to MCP registry:
    powershell
    mcp-publisher publish
  5. Verify:
    powershell
    curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.vtiwari/weather-mcp"

Create & Push GitHub Repository

If this directory is not yet a git repo:

powershell
git initgit add .git commit -m "Initial commit: Weather MCP server"

Create repo (GitHub CLI) and push:

powershell
gh repo create vtiwari/weather-mcp --public --source . --remote origin --push

If not using GitHub CLI, create the repo manually via the GitHub web UI, then:

powershell
git remote add origin https://github.com/vtiwari/weather-mcp.gitgit branch -M maingit push -u origin main

Tag version for release consistency:

powershell
git tag v0.1.0git push origin v0.1.0

PyPI Packaging (Optional)

To distribute via PyPI, ensure pyproject.toml includes build backend and metadata (authors, license). Then:

powershell
pip install build twinepython -m buildtwine upload dist/*

License

MIT (adjust if different).

Disclaimer

This server uses public NOAA/NWS endpoints. Respect API usage guidelines and rate limits.

Source: README.md at commit 70118b4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Alerts integrations