How do I use Weather MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Weather MCP Server Get active weather alerts for Texas" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Weather MCP Server

by dinuka-kasun-medis

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Weather MCP Server for Claude

This repository implements a Model Context Protocol (MCP) server for Claude. It exposes weather-related tools via FastMCP over stdio, using the National Weather Service (NWS) API for data.

Project Structure

weather/
├── clients/
│   ├── __init__.py
│   └── nws_client.py
├── formatters/
│   ├── __init__.py
│   └── alert_formatter.py
├── services/
│   ├── __init__.py
│   └── weather_service.py
├── tools/
│   ├── __init__.py
│   └── weather_tools.py
├── models/
│   ├── __init__.py
│   └── responses.py
├── config.py
├── logging_config.py
├── main.py
├── pyproject.toml
└── README.md

Related MCP server: Weather MCP Server

Features

MCP server for Claude using FastMCP
get_alerts(state) tool for active weather alerts
get_forecast(latitude, longitude) tool for forecast data
Simple, maintainable service and client separation

Requirements

Python 3.10 or higher
uv installed and available at the full path used by Claude
mcp and httpx dependencies installed in the Python environment

Running the Server Locally

From the repository root:

cd /Users/dinukakasun/Documents/MCP/weather
/Users/dinukakasun/.local/bin/uv --directory /Users/dinukakasun/Documents/MCP/weather run main.py

or using the virtual environment Python if preferred:

/Users/dinukakasun/Documents/MCP/weather/.venv/bin/python main.py

The server should start and expose MCP tools on stdio.

Claude Desktop MCP Configuration

Update ~/Library/Application Support/Claude/claude_desktop_config.json so Claude launches this server with the correct executable path and working directory.

Example configuration:

{
  "mcpServers": {
    "weather": {
      "command": "/Users/dinukakasun/.local/bin/uv",
      "args": [
        "--directory",
        "/Users/dinukakasun/Documents/MCP/weather",
        "run",
        "main.py"
      ]
    }
  }
}

Why absolute paths matter

Claude desktop may not inherit your interactive shell PATH. Using the absolute uv path avoids startup failures caused by missing commands.

Example Claude Questions

Use these example prompts to exercise the MCP server:

Get the current weather alerts for CA using get_alerts.
Call get_forecast with latitude 37.7749 and longitude -122.4194.
What are active alerts for NY?
Provide a 5-period weather forecast for 40.7128, -74.0060.

Local Test Client

You can verify the MCP tools locally with a small Python client that starts the server and sends a request over stdio.

import asyncio
import json
import subprocess

async def run_request():
    proc = await asyncio.create_subprocess_exec(
        "/Users/dinukakasun/.local/bin/uv",
        "--directory",
        "/Users/dinukakasun/Documents/MCP/weather",
        "run",
        "main.py",
        stdin=subprocess.PIPE,
        stdout=subprocess.PIPE,
        stderr=subprocess.PIPE,
    )

    request = {
        "jsonrpc": "2.0",
        "id": 1,
        "method": "initialize",
        "params": {
            "protocolVersion": "2024-11-05",
            "capabilities": {},
            "clientInfo": {"name": "local-test", "version": "1.0.0"}
        }
    }

    stdout, stderr = await proc.communicate((json.dumps(request) + "\n").encode())
    print(stdout.decode())
    print(stderr.decode())

asyncio.run(run_request())

This confirms the server accepts MCP requests. For tool-specific tests, replace method with a valid tool name and pass params matching the tool signature.

Verifying the MCP Server

Start the server manually.
Confirm the process is running:

ps aux | grep "main.py" | grep -v grep

Confirm Claude is configured to use the same command and working directory.
If Claude still does not connect, use the absolute uv path in claude_desktop_config.json.

Notes

The MCP server uses stdio transport, not a network HTTP endpoint.
The entrypoint is main.py, not weather.py.
The tools are registered in tools/weather_tools.py.

Reference

Model Context Protocol Python server docs: https://modelcontextprotocol.io/docs/develop/build-server#python

Available Tools

2 tools

get_alertsD

ParametersJSON Schema

Name	Required	Description	Default
`state`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_forecastD

ParametersJSON Schema

Name	Required	Description	Default
`latitude`	Yes
`longitude`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

2 tool updatesv0.1.0Jun 20, 2026
- First observedget_alerts
- First observedget_forecast

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.9/5.0

Scored 2026-06-20 18:25 across 2 tools

Disambiguation5/5

The two tools, get_alerts and get_forecast, have clearly distinct purposes. An agent can easily differentiate between retrieving weather alerts and obtaining a forecast, with no overlap in functionality.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern using snake_case (get_alerts, get_forecast), ensuring predictable and uniform naming.

Tool Count3/5

With only two tools, the server's scope feels somewhat thin for a weather-related service. While it covers the basics, a typical weather server would benefit from additional tools like current conditions or location search.

Completeness3/5

The tool set covers alerts and forecasts, but lacks common operations such as current conditions or historical data. This represents a notable gap that may hinder comprehensive weather queries.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

nws-weather-mcp-server A
io.github.cyanheads
Get US weather forecasts, active alerts, and current observations.
Weather Services Government Data Open Data
721
Weather & Geo Intel MCP A
io.github.selflabbs
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
Weather Services Location Services
2
Weather & Geo Intel MCP A
com.datakoot
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
Weather Services Location Services
61
smithery-ai-national-weather-service AOAuth
ai.smithery
Provide real-time and forecast weather information for locations in the United States using natura…
Weather Services Search Location Services
6295

Related MCP Servers

Weather MCP Server
Weather Services
Danii2020
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.
Updated a year ago (2025-05-28 04:04 UTC)
2
-
Weather MCP Server
Weather Services Search
aitiwari
F
license
B
quality
D
maintenance
Provides real-time US weather alerts and forecasts by integrating with the National Weather Service API. It enables AI assistants to fetch state-specific alerts and detailed local forecasts using geographic coordinates.
Updated a year ago (2025-03-23 17:08 UTC)
2
1
-
mcp-weather-api
Weather Services Location Services
devgrunge
F
license
Not graded
quality
D
maintenance
Provides weather forecasts and alerts for US locations via the National Weather Service API, enabling AI assistants to deliver real-time weather information.
Updated a year ago (2025-09-25 18:48 UTC)
8 npm
-
Spring AI MCP Weather Server
Weather Services Government Data
AmanHogan
F
license
Not graded
quality
D
maintenance
Exposes tools for retrieving weather forecasts and alerts using the National Weather Service API.
Updated 5 months ago (2026-04-06 01:00 UTC)
-

Weather MCP Server for Claude

Project Structure

Features

Requirements

Running the Server Locally

Claude Desktop MCP Configuration

Why absolute paths matter

Example Claude Questions

Local Test Client

Verifying the MCP Server

Notes

Reference

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Weather MCP Server

Weather MCP Server

mcp-weather-api

Spring AI MCP Weather Server