mcp-server-openmeteo
Provides an MCP server that exposes OpenMeteo weather capabilities as MCP tools: current weather, multi-day forecasts, historical daily weather, and global location search (geocoding) by delegating to OpenMeteo’s free public API.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Transport/auth for the MCP server is not described; if exposed beyond localhost, it may lack access control. Upstream OpenMeteo usage likely does not require API keys per README. TLS requirement for the MCP server is not specified; for OpenMeteo calls, HTTPS is expected but not guaranteed by the README. Secret handling appears minimal because no secrets are mentioned, but dependency/security posture is not verifiable from provided content.
⚡ Reliability
Best When
You want an easy-to-run local MCP server to enrich AI responses with weather and location data using OpenMeteo (no API key).
Avoid When
You need documented MCP server transport details, authentication/authorization, or strong guarantees about error semantics, rate limits, and uptime.
Use Cases
- • Chat-based weather assistants (current conditions, forecasts)
- • Weather lookups for apps/agents needing location-based meteorological context
- • Historical weather analysis for a date range at given coordinates
- • Geocoding support inside an AI workflow (convert city names to lat/long + timezone)
Not For
- • High-reliability, SLA-backed weather data without external dependency on OpenMeteo
- • Use cases requiring strict data governance/region constraints (not specified)
- • Production deployments needing strong access control/auth for the MCP server itself (not specified)
Interface
Authentication
README describes no auth mechanism for the MCP server itself. It also claims OpenMeteo access is free and requires no API key, so the integration likely relies on public OpenMeteo endpoints.
Pricing
Uses OpenMeteo free API (per README). No MCP server pricing described (repo likely distributed as code/binaries). Any costs would be downstream infrastructure and any OpenMeteo usage constraints.
Agent Metadata
Known Gotchas
- ⚠ No explicit MCP server deployment/transport details (e.g., whether it listens on a port, how errors are returned) in provided README
- ⚠ Rate limit behavior and headers from OpenMeteo are not documented here
- ⚠ Historical/forecast responses may be large; agents may need to summarize rather than fully ingest raw data
- ⚠ Tool parameter constraints are mentioned (e.g., days 1-16, coordinate ranges) but there’s no documented error-code mapping for invalid inputs
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-openmeteo.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
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
Scores are editorial opinions as of 2026-04-04.