weather-mcp-server

weather-mcp-server is a Model Context Protocol (MCP) server for Claude Desktop that provides weather data (current conditions, 5-day forecast, and query history) by integrating with OpenWeatherMap and using PostgreSQL and Redis for persistence and caching.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ Ai Ml mcp weather claude-desktop typescript openweathermap postgresql redis caching
⚙ Agent Friendliness
54
/ 100
Can an agent use this?
🔒 Security
50
/ 100
Is it safe for agents?
⚡ Reliability
36
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
70
Documentation
55
Error Messages
0
Auth Simplicity
85
Rate Limits
30

🔒 Security

TLS Enforcement
60
Auth Strength
45
Scope Granularity
20
Dep. Hygiene
60
Secret Handling
70

Uses environment variables for secrets (WEATHER_API_KEY, connection strings) and mentions a security CI step (Trivy + npm audit), but the provided content does not confirm TLS requirements, authorization model for MCP clients, or detailed secret-handling practices within logs/runtime.

⚡ Reliability

Uptime/SLA
0
Version Stability
55
Breaking Changes
50
Error Recovery
40
AF Security Reliability

Best When

You want Claude Desktop to answer weather questions with up-to-date information and you can provide OpenWeatherMap credentials plus PostgreSQL/Redis runtime dependencies.

Avoid When

You need a standalone API without MCP integration, or you cannot manage secrets and infrastructure dependencies (PostgreSQL/Redis).

Use Cases

  • Enable Claude Desktop to answer weather questions with real-time data
  • Provide weather forecasts for multiple days
  • Store and retrieve historical weather query records
  • Use Redis caching to speed up repeated weather lookups
  • Expose operational/cache statistics through MCP tools

Not For

  • A general-purpose weather REST API for external clients
  • Use cases requiring strict compliance guarantees without additional configuration/review
  • Environments where outbound calls to OpenWeatherMap are not allowed

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: OpenWeatherMap API key via environment variable (WEATHER_API_KEY)
OAuth: No Scopes: No

Authentication appears to be configuration via environment variables for upstream API access. MCP access/authentication for clients is not described in the provided content.

Pricing

Free tier: No
Requires CC: No

No pricing information provided. Upstream costs may apply from OpenWeatherMap plan/limits and your infrastructure (PostgreSQL/Redis).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Requires correct MCP server startup and Claude Desktop configuration (paths to dist/mcp-entry.js).
  • Requires environment variables for WEATHER_API_KEY, DATABASE_URL, and REDIS_URL; misconfiguration may cause tool failures.
  • Integration depends on external OpenWeatherMap API availability and rate limits; unexpected upstream errors may propagate.

Alternatives

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

$3

Score Monitoring

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

Continuous monitoring

$3/mo

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

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered