weather-mcp-server

Weather API MCP server that exposes an MCP tool (e.g., current_weather) to fetch current weather data for a specified city, using WeatherAPI via an API key. Intended for use with AI assistants through MCP over stdio (local) or SSE (remote).

Evaluated Mar 30, 2026 (21d ago)

Homepage ↗ Repo ↗ Ai Ml mcp weather go sse stdio tooling self-hosted

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Security posture is partially dependent on deployment: TLS usage and MCP-server authentication are not described. The server uses an upstream API key provided via env var (better than hardcoding), but there is no evidence of fine-grained access control or secrets redaction in logs from the provided README.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want a lightweight, self-hosted MCP tool for weather retrieval that can be plugged into an agent via Claude Desktop MCP configuration.

Avoid When

You require strong built-in security controls (auth, scoped access) at the MCP server layer or you need documented reliability/SLA guarantees.

Use Cases

• Ask an AI assistant for current weather by city
• Build assistant workflows that need real-time weather context
• Prototype location-aware conversational experiences using an MCP tool

Not For

• High-volume production weather querying without considering upstream rate limits
• Use where strict data residency/compliance guarantees are required (not stated)
• Use without protecting the WeatherAPI key (server expects WEATHER_API_KEY)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

Methods: API key via environment variable WEATHER_API_KEY

OAuth: No Scopes: No

No MCP-server user auth is described; the only documented credential is the upstream WeatherAPI key passed via env var.

Pricing

Free tier: No

Requires CC: No

The repo documentation does not describe pricing for the MCP server itself; it relies on WeatherAPI (which typically has its own billing/rate limits).

Agent Metadata

Pagination

none

Idempotent

True

Retry Guidance

Not documented

Known Gotchas

⚠ Upstream WeatherAPI failures/rate limits may surface as tool errors; README does not describe retry/backoff behavior.
⚠ Remote mode uses SSE URL; ensure network/proxy supports long-lived connections/timeouts.
⚠ Server requires WEATHER_API_KEY; missing/invalid key will likely cause tool failures.

Alternatives

Other MCP/weather connectors (if available) Direct WeatherAPI client integration in your application Agent-side tool calling using WeatherAPI SDKs without an MCP server layer

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for weather-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.