Skip to main content
Glama
Claude-NWS Protocol Bridge

Claude-NWS Protocol Bridge

by shreyyzsh

Context Weather

A Model Context Protocol (MCP) server that integrates the US National Weather Service API with Claude Desktop, providing real-time weather data and forecasts directly within your Claude conversations.

Features

  • Real-time weather conditions and forecasts

  • Location-based weather queries using coordinates or place names

  • Seamless integration with Claude Desktop via MCP

  • Live data from the official US National Weather Service API

  • Detailed weather metrics including temperature, humidity, wind, and precipitation

Related MCP server: Weather MCP Server

Prerequisites

  • Claude Desktop App

  • Python (v3.12 or higher)

  • uv package manager

  • Internet connection for API access

Installation

  1. Clone this repository:

    git clone https://github.com/yourusername/claude-nws-protocol-bridge.git
    cd claude-nws-protocol-bridge
  2. Install dependencies:

    uv sync
  3. Configure the MCP server in your Claude Desktop settings:

    {
     "mcpServers": {
       "nws-weather": {
         "command": "uv",
         "args": ["run", "python", "weather.py"]
       }
     }
    }

Usage

Once configured, you can ask Claude weather-related questions such as:

  • "What's the current weather in San Francisco?"

  • "Give me a 7-day forecast for New York City"

  • "What's the temperature and humidity right now?"

  • "Is it going to rain today in Seattle?"

API Reference

The bridge provides the following MCP tools:

get-current-weather

Retrieves current weather conditions for a specified location.

Parameters:

  • location (string): City name, coordinates, or ZIP code

get-weather-forecast

Gets weather forecast data for a specified location.

Parameters:

  • location (string): City name, coordinates, or ZIP code

  • days (number, optional): Number of forecast days (default: 7)

Available Tools

2 tools
get_alertsA
Getting weather alerts for a US State.

Args:
    state: two-letter us state code (e.g CA, NY)

Inputs: state (required).

get_forecastC
Getting weather forecast for a location.

Args:
    latitude: latitude of the location
    longitude: longitude of the location

Inputs: latitude (required), longitude (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_alerts retrieves weather alerts for a US state, while get_forecast provides weather forecasts for a specific geographic location. There is no overlap in functionality or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern (get_alerts and get_forecast), using the same verb 'get' followed by a descriptive noun. This makes the tool set predictable and easy to understand.

    Tool Count2/5

    With only two tools, the server feels thin for a weather service domain. While the tools cover alerts and forecasts, there are likely missing operations such as current conditions, radar data, or historical data that would make the set more complete for typical weather-related tasks.

    Completeness2/5

    For a weather service, the tool set is significantly incomplete. It lacks core functionalities like getting current weather conditions, radar or satellite imagery, historical data, or air quality information. This limited coverage will likely cause agent failures when trying to perform comprehensive weather-related tasks.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      D
      quality
      D
      maintenance
      Provides real-time weather forecasts and alerts by fetching data from the National Weather Service API, allowing Claude to answer weather-related questions with up-to-date information.
      2
      -