Skip to main content
Glama
Weather MCP Server

Weather MCP Server

We’ll build a server that exposes two tools: get_alerts and get_forecast. Then we’ll connect the server to an MCP host (in this case, Claude for Desktop): Core MCP Concepts MCP servers can provide three main types of capabilities: Resources: File-like data that can be read by clients (like API responses or file contents) Tools: Functions that can be called by the LLM (with user approval) Prompts: Pre-written templates that help users accomplish specific tasks

Prerequisite knowledge This quickstart assumes you have familiarity with: Python LLMs like Claude ​ Logging in MCP Servers When implementing MCP servers, be careful about how you handle logging: For STDIO-based servers: Never write to standard output (stdout). This includes: print() statements in Python console.log() in JavaScript fmt.Println() in Go Similar stdout functions in other languages Writing to stdout will corrupt the JSON-RPC messages and break your server. For HTTP-based servers: Standard output logging is fine since it doesn’t interfere with HTTP responses. ​ Best Practices Use a logging library that writes to stderr or files.

Available Tools

2 tools
get_alertsA

Get weather alerts for a US state.

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

Inputs: state (required). Returns: result

get_forecastC

Get weather forecast for a location.

Args: latitude: Latitude of the location longitude: Longitude of the location

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

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

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

    Naming Consistency5/5

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

    Tool Count2/5

    With only two tools, the server feels thin for a weather domain. It lacks basic operations like current conditions, historical data, or location search, making it incomplete for typical weather-related tasks.

    Completeness2/5

    The tool set is severely incomplete for a weather server. It misses core functionalities such as current weather, radar data, air quality, or unit conversions, leaving significant gaps that will hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides weather forecast data from the US National Weather Service API through MCP tools. Enables users to get detailed weather forecasts by ZIP code or coordinates using natural language queries.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Provides weather forecasts and alerts for US locations using the National Weather Service API. Enables users to retrieve active alerts by state and detailed forecasts by coordinates via MCP tools.
      12
      2
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides current weather conditions and 5-day/3-hour forecasts for any location using OpenWeatherMap, accessible through natural language in MCP clients.
      28 npm
      1
      ISC