Skip to main content
Glama
Context Weather

Context Weather

by tjguitar2025

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: Claude-NWS Protocol Bridge

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

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: get_alerts targets state-level weather alerts, while get_forecast targets point-based forecast. No overlap in purpose or arguments.

    Naming Consistency5/5

    Both tools follow a consistent get_verb_noun pattern (get_alerts, get_forecast), which is predictable and clear.

    Tool Count3/5

    With only 2 tools, the server feels minimal. While it serves a focused purpose, a typical weather API would offer more operations, making the count borderline.

    Completeness4/5

    The server covers alerts and forecast, but lacks current conditions or radar data. The gaps are minor given the server's 'context' focus.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers