F
licenseB
qualityD
maintenanceProvides weather forecast and alert information for US locations using the National Weather Service API. Enables users to get detailed weather forecasts by coordinates and retrieve active weather alerts by state.
2
weather-mcp-server
by elmopps
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@weather-mcp-serverare there any weather alerts in Florida?"
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
An MCP (Model Context Protocol) server that gives Claude real-time weather data from the US National Weather Service API — no API key needed.
What it does
get_alerts— fetches active weather alerts for any US stateget_forecast— fetches a 5-period forecast for any lat/long location
Related MCP server: Weather MCP Server
Requirements
Python 3.12+
uv
Setup
Clone the repo and install dependencies:
git clone https://github.com/YOUR_USERNAME/weather-mcp-server
cd weather-mcp-server
uv venv --python 3.12
source .venv/bin/activate
uv add "mcp[cli]" httpxConnect to Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"weather": {
"command": "uv",
"args": ["--directory", "/path/to/weather-mcp-server", "run", "weather.py"]
}
}
}Restart Claude Desktop. Look for the hammer icon in the chat input.
Built with
MCP Python SDK (https://github.com/modelcontextprotocol/python-sdk)
National Weather Service API (https://api.weather.gov)
Available Tools
2 toolsget_alertsA
Get weather alerts for a US state.
Args:
state: Two-letter US state code (e.g. CA, NY)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It does not disclose behavioral traits like read-only status, rate limits, authentication requirements, or behavior for invalid state codes. Only states it gets alerts, leaving agent uninformed about important behaviors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with the main purpose. The 'Args:' section is efficiently formatted. It contains no fluff, but could be more concise by integrating the parameter format into the main sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool (1 param, output schema present), the description is adequate but minimal. It does not mention that alerts are only for US states or provide any usage examples. The output schema reduces the need to describe return values, but additional context like geographical scope could improve completeness.
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?
Schema description coverage is 0%, so description must compensate. It adds meaning by specifying the exact format 'Two-letter US state code' and provides examples ('CA, NY'), which goes beyond the schema's mere type definition.
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 uses a specific verb 'Get' and resource 'weather alerts' with clear scope 'for a US state'. It distinguishes from sibling tool 'get_forecast' which presumably provides forecasts instead of alerts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when alerts are needed for a US state, but provides no explicit guidance on when to use this tool over 'get_forecast' or any exclusions. No alternatives or when-not-to-use are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_forecastC
Get weather forecast for a location.
Args:
latitude: Latitude of the location
longitude: Longitude of the location
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| latitude | Yes | ||
| longitude | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
C2.9/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It only states it gets a forecast, with no mention of data sources, limitations, latency, or side effects. This is insufficient for a data-fetching tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (two sentences) and front-loads the purpose. However, the 'Args' section is redundant with the input schema, slightly reducing efficiency.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the existence of an output schema and no nested objects, the description is minimally adequate. It conveys the basic function but lacks context on usage conditions or what the forecast includes. More details would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must add meaning. It merely repeats parameter names and descriptions (e.g., 'Latitude of the location') that are already clear from the schema. No additional semantics like valid ranges, units, or defaults are provided.
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 'Get weather forecast for a location', using a specific verb and resource. It also distinguishes from the sibling tool 'get_alerts', which would provide alerts rather than forecasts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, such as 'get_alerts'. It does not mention any prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
B3.4/5.0
Disambiguation5/5
The two tools have clearly distinct purposes: one for weather alerts by state, another for forecast by coordinates. No overlap in functionality.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern (get_alerts, get_forecast), making the naming predictable and easy to understand.
Tool Count3/5
With only two tools, the server feels minimal for a weather domain. While it covers two core functions, 2 tools is on the lower end of reasonable scope.
Completeness3/5
The server provides alerts and forecast but lacks current conditions, radar, or marine data, leaving notable gaps for a typical weather information service.
Maintenance
ActivityStale
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Get US weather forecasts, active alerts, and current observations.
Provide real-time and forecast weather information for locations in the United States using natura…
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
US weather alerts from NWS: warnings, watches, advisories by state. $0.01/query.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides weather information and alerts from the National Weather Service, including active weather alerts for US states and location-based forecasts using latitude/longitude coordinates.2MIT
- FlicenseBqualityDmaintenanceProvides real-time weather forecasts and alerts for US locations using the National Weather Service API. Supports querying forecasts by coordinates and retrieving active weather alerts by state.2
- AlicenseNot gradedqualityDmaintenanceProvides weather information using the US National Weather Service API, including active weather alerts for US states and location-specific forecasts based on latitude and longitude coordinates.80MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/elmopps/weather-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server