Skip to main content
Glama

MCP Weather Project

A Model Context Protocol (MCP) server implementation that provides weather alerts via the National Weather Service (NWS) API. This project includes both a FastMCP server and a LangChain-based client with memory capabilities.

Features

  • Weather Alerts: Fetch active weather alerts for any US state using the NWS API.

  • Echo Resource: A simple resource that echoes back messages.

  • Greeting Prompt: A customizable greeting prompt generator.

  • Interactive Client: A CLI-based chat client powered by Groq's Llama 3.3 model with conversation memory.

Related MCP server: Weather MCP Server

Prerequisites

  • Python 3.12 or higher

  • uv (recommended for dependency management)

  • A Groq API Key for the client.

Installation

  1. Clone the repository:

    git clone <repository_url>
    cd mcpfile
  2. Install dependencies: Using uv (recommended):

    uv sync

    Or using pip:

    pip install -r requirements.txt

    (Note: You may need to generate a requirements.txt from pyproject.toml if not using uv)

  3. Set up Environment Variables: Create a .env file in the root directory and add your Groq API key:

    GROQ_API_KEY=your_groq_api_key_here

Usage

Running the Entry Point

The main.py is a simple entry point script that prints a welcome message.

uv run main.py
# OR
python main.py

Running the interactive Client

The client connects to the weather server and allows you to interact with it using natural language.

  1. Ensure the server configuration in server/weather.json is correct (it points to server/weather.py).

  2. Run the client:

    uv run server/client.py
    # OR if using a virtual environment directly:
    # python server/client.py
  3. Example Interaction:

    You: Check weather alerts for TX
    Assistant: Checking weather alerts for Texas...
    [Agent responds with alerts]

Running the MCP Server Standalone

You can run the MCP server directly using uv. This is useful for inspection or debugging with the MCP Inspector.

uv run --with mcp[cli] mcp run server/weather.py

Configuration Verification

Ensure that server/weather.json points to the correct absolute path of your server/weather.py file.

{
  "mcpServers": {
    "weather": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "mcp",
        "run",
        "/your/absolute/path/to/mcp/mcpfile/server/weather.py" 
      ]
    }
  }
}

Project Structure

  • server/weather.py: The main MCP server implementation using FastMCP. Defines tools (get_alerts), resources, and prompts.

  • server/client.py: An MCP client implementation using LangChain and ChatGroq. Handles the interactive chat session.

  • server/weather.json: Configuration file for the MCP client to locate the server.

  • main.py: Simple entry point script.

  • pyproject.toml: Project configuration and dependencies.

Tools Available

  • get_alerts(state: str): Get active weather alerts for a US state (e.g., "CA", "NY").

Resources

  • echo://{message}: Echoes a message.

Prompts

  • greet_user(name: str, style: str): Generates a greeting in a specified style ("friendly", "formal", or "casual").

Available Tools

1 tool
get_alertsB

Get weather alerts for a US state.

Args:
    state: Two-letter US state code (e.g. CA, NY)

Inputs: state (required). Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_alerts' has a clear and distinct purpose that cannot be confused with any other tool in this set.

    Naming Consistency5/5

    The naming pattern is trivially consistent as there is only one tool. The tool name 'get_alerts' follows a clear verb_noun convention (get + alerts), which would be consistent if more tools were added.

    Tool Count2/5

    A single tool is generally too few for a weather server's apparent scope, which typically includes forecasts, current conditions, and other weather data beyond just alerts. This feels thin and limited for the domain.

    Completeness2/5

    The tool surface is severely incomplete for a weather domain. It only provides alerts for US states, missing essential operations like getting forecasts, current weather, radar data, or international coverage, which will cause significant agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that provides weather information and alerts for US locations using the National Weather Service API, enabling retrieval of weather forecasts and active weather alerts.
      2
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to get real-time weather alerts for US states and echo messages through both MCP server tools and a modern web interface. Provides weather information access with multiple deployment options for different use cases.
      1
      -
    • F
      license
      C
      quality
      D
      maintenance
      An MCP server that provides weather alerts and forecasts using the National Weather Service API, with additional system tools for shell commands and process information.
      3
      1
      -