Skip to main content
Glama
charley-forey

MCP Weather Server

MCP Weather Server

A simple MCP server that provides hourly weather forecasts using the AccuWeather API.

Setup

  1. Install dependencies using uv:

uv venv
uv sync
  1. Create a .env file with your AccuWeather API key:

ACCUWEATHER_API_KEY=your_api_key_here

You can get an API key by registering at AccuWeather API.

Related MCP server: Weather MCP Server

Running the Server

STDIO Mode (Default)

For local MCP client connections via stdio:

{
    "mcpServers": {
        "weather": {
            "command": "uvx",
            "args": ["--from", "git+https://github.com/adhikasp/mcp-weather.git", "mcp-weather"],
            "env": {
                "ACCUWEATHER_API_KEY": "your_api_key_here"
            }
        }
    }
}

HTTP Streaming Mode

To run the server as a streamable HTTP server:

Option 1: Using the command line

python -m mcp_weather.weather --http

Option 2: Using the entry point

mcp-weather-http

Option 3: Using environment variables

export MCP_HOST=0.0.0.0
export MCP_PORT=8000
python -m mcp_weather.weather --http

The server will start on http://0.0.0.0:8000 (or your specified host/port) and expose the MCP endpoint at /mcp. The streamable-http transport supports:

  • JSON responses for standard requests

  • Server-Sent Events (SSE) for streaming long-running operations

  • Remote access via HTTP endpoints

  • Horizontal scaling with load balancing

Connecting to HTTP Server:

For MCP clients that support HTTP transport, configure the connection URL:

http://localhost:8000/mcp

Agent UI Configuration:

When configuring your MCP server in the Agent UI (e.g., Cursor, Claude Desktop, etc.):

  • URL: Provide the full endpoint URL (e.g., http://localhost:8000/mcp or https://your-ngrok-url.ngrok.io/mcp)

  • Authentication: Not required by default - No API keys, tokens, or scopes need to be configured in the Agent UI

  • Headers: No custom headers needed for basic operation

The MCP protocol handles communication automatically. Your AccuWeather API key is stored server-side and never needs to be shared with the client.

Note: If you implement custom authentication (API keys, tokens) at the HTTP layer for production use, you would configure those in your server code, not in the Agent UI. The Agent UI would then need to include those credentials in HTTP requests, but this is not needed for basic operation.

Production Deployment:

For production, you can use environment variables or configure a reverse proxy:

# Set custom host and port
export MCP_HOST=0.0.0.0
export MCP_PORT=8080
mcp-weather-http

Exposing via Public URL (Tunneling)

To make your local server accessible via a public URL, use a tunneling service:

  1. Install ngrok on Windows:

    Option A: Using winget (Windows 10/11 - Recommended)

    winget install ngrok.ngrok

    Option B: Using Chocolatey (if you have Chocolatey installed)

    choco install ngrok

    Option C: Manual Download

    • Go to ngrok.com/download

    • Download the Windows ZIP file

    • Extract ngrok.exe to a folder (e.g., C:\ngrok)

    • Add that folder to your PATH, or run ngrok from that folder

    • Or simply run: .\ngrok.exe http 8000 from the extracted folder

    Option D: Using Scoop (if you have Scoop installed)

    scoop install ngrok

    After installation, verify it works:

    ngrok version
  2. Start your MCP server:

    python -m mcp_weather.weather --http
  3. Create a tunnel (in a separate terminal):

    ngrok http 8000
  4. Use the public URL: ngrok will provide a public URL like https://abc123.ngrok-free.dev.

    Important: The MCP endpoint is at /mcp, not the root URL. Use:

    https://abc123.ngrok-free.dev/mcp

    Note about ngrok warning page: Free ngrok accounts show a warning page when visiting the root URL. This is normal and expected. The /mcp endpoint will work correctly for MCP clients. To remove the warning page, you can:

    • Upgrade to a paid ngrok account

    • Set the ngrok-skip-browser-warning header in your MCP client (if supported)

    • Use a custom domain with a paid account

    For a custom domain (requires paid ngrok account):

    ngrok http 8000 --domain=your-custom-domain.ngrok.io

Option 2: Cloudflare Tunnel (cloudflared)

  1. Install cloudflared: Download from developers.cloudflare.com

  2. Start your MCP server:

    python -m mcp_weather.weather --http
  3. Create a tunnel (in a separate terminal):

    cloudflared tunnel --url http://localhost:8000
  4. Use the public URL: Cloudflare will provide a public URL like https://random-subdomain.trycloudflare.com. Your MCP endpoint will be:

    https://random-subdomain.trycloudflare.com/mcp

Option 3: localtunnel

  1. Install localtunnel:

    npm install -g localtunnel
  2. Start your MCP server:

    python -m mcp_weather.weather --http
  3. Create a tunnel (in a separate terminal):

    lt --port 8000
  4. Use the public URL: localtunnel will provide a public URL like https://random-name.loca.lt. Your MCP endpoint will be:

    https://random-name.loca.lt/mcp

Security Note: When exposing your server publicly, consider:

  • Adding authentication/API keys if your MCP server handles sensitive data

  • Using HTTPS (all tunneling services above provide HTTPS)

  • Limiting access to specific IPs if possible

  • Monitoring usage and rate limiting

API Usage

Get Hourly Weather Forecast

Response:

{
    "location": "Jakarta",
    "location_key": "208971",
    "country": "Indonesia",
    "current_conditions": {
        "temperature": {
            "value": 32.2,
            "unit": "C"
        },
        "weather_text": "Partly sunny",
        "relative_humidity": 75,
        "precipitation": false,
        "observation_time": "2024-01-01T12:00:00+07:00"
    },
    "hourly_forecast": [
        {
            "relative_time": "+1 hour",
            "temperature": {
                "value": 32.2,
                "unit": "C"
            },
            "weather_text": "Partly sunny",
            "precipitation_probability": 40,
            "precipitation_type": "Rain",
            "precipitation_intensity": "Light"
        }
    ]
}

The API provides:

  • Current weather conditions including temperature, weather description, humidity, and precipitation status

  • 12-hour forecast with hourly data including:

    • Relative time from current time

    • Temperature in Celsius

    • Weather description

    • Precipitation probability, type, and intensity

Available Tools

1 tool
get_hourly_weatherA

Get hourly weather forecast for a location.

Args: location: The city or location name (e.g., "Chicago", "New York") unit: Temperature unit - "C" for Celsius (default) or "F" for Fahrenheit

ParametersJSON Schema
NameRequiredDescriptionDefault
unitNoC
locationYes

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states 'Get hourly weather forecast' but does not describe the response format, potential limitations (e.g., number of hours returned, timezone handling), or any side effects. The description is essentially a restatement of the tool's name with no added behavioral context.

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

Conciseness5/5

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

The description is concise and well-structured: a one-sentence purpose followed by clearly labeled arguments. Every sentence is essential, and the Args section is formatted for easy parsing. No filler or redundancy.

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

Completeness2/5

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

The tool has no output schema and no annotations, so the description should explain what the tool returns to be fully complete. It only states 'hourly weather forecast' without detailing the response fields (e.g., temperature, precipitation, wind). For an AI agent, this lack of return-value information leaves a significant gap in understanding the tool's full output.

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

Parameters4/5

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

The input schema provides only parameter names and types, with no descriptions (0% coverage). The description compensates by explaining 'location' as a city or location name with examples, and 'unit' with its default and allowed values ('C' for Celsius, 'F' for Fahrenheit). This adds meaningful semantics beyond the schema, though it could be more comprehensive (e.g., supporting zip codes or other formats).

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

Purpose5/5

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

The description clearly states the tool's function: 'Get hourly weather forecast for a location.' This is a specific verb (get) and resource (hourly weather forecast), and it is distinct from any potential siblings. No ambiguity in purpose.

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

Usage Guidelines4/5

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

The description does not explicitly state when to use this tool versus alternatives, but with no sibling tools listed, the context is clear. It provides the required input (location) and optional unit, implying the tool is for any location's hourly forecast. It lacks explicit exclusions or alternative recommendations, but this is acceptable given no alternatives exist.

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.

  1. 1 tool updatev0.1.0
    • First observedget_hourly_weather

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clear and distinct.

Naming Consistency5/5

The tool name 'get_hourly_weather' follows a clear verb_noun pattern, which is consistent even though it is the only tool. Naming conventions are not violated.

Tool Count2/5

A single tool is too few for a server that claims to be a weather server. The apparent scope is broader than just hourly forecasts, so the tool count feels inadequate.

Completeness2/5

The tool surface only covers hourly forecasts, missing standard weather operations like current conditions, daily forecasts, or alerts. This leaves significant gaps for agents expecting comprehensive weather data.

Maintenance

ActivityStale
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    Provides hourly weather forecasts using the AccuWeather API, enabling users to access current weather conditions and detailed 12-hour forecasts tailored to specific locations.
    1
    36
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables users to get current weather information for any city using the Open-Meteo API. Provides detailed meteorological data including temperature, precipitation, day/night status, and hourly forecasts through natural language queries.
    -