Meteoprog API MCP Server lets ChatGPT, Codex, Claude Desktop, and other MCP clients work with weather data through natural language. Ask for a forecast, compare locations, check an alert, or look up air quality — the server selects the right Meteoprog operation and returns a compact, useful answer.
Need the complete method list? See the Meteoprog API MCP Server Full Reference for all 65 smart, OpenAPI, and weather-alert tools.
Start with one of the smart tools
For normal requests, you do not need to know the underlying Meteoprog endpoint. The MCP client can start with one of these tools:
Weather data for AI assistants
The server can provide current observations, date- and hour-specific forecasts, seven-day and two-week summaries, calendar-month models, weather comparisons, active alerts, alert explanations, air quality, astronomy, climate history, geomagnetic activity, water temperature, location lookup, supported languages, and service status.
Responses include units, the relevant local time period, resolved location details, data availability, and usage information. This helps an AI assistant distinguish an exact hourly forecast from a broader daily or monthly model summary.
Ask in plain language
Use MCP Meteoprog to show the current weather in Miami in English.Use MCP Meteoprog: what will the temperature be in Warsaw tomorrow at 1:00 PM? Will it rain?Use MCP Meteoprog to compare tomorrow's weather in Miami, New York, and Los Angeles.Use MCP Meteoprog to check active severe-weather alerts in the United States.Use MCP Meteoprog to show air quality in Miami for the next five days and identify the worst day.Specify a response language — for example, “show the forecast in Spanish” — and add a country code or coordinates when a city name could be ambiguous.
Connect an MCP client
An API key is required to use the Meteoprog MCP server. For a remote MCP connection, use the server URL and send your Meteoprog API key as a Bearer token. The key belongs in the client connection settings, never in a question or tool argument.
Free Developer Access for testing
Developer Access is a free development environment for API exploration, integration work, schema validation, and MCP testing before production. No credit card is required. It provides a real API key, 5,000 requests per day, a 5 requests per second limit, and access to the API Sandbox.
Developer Access is not a free production tier. Weather data is limited to a fixed, representative set of populated locations: Brisbane, Malaga, Oujda, Santiago, Amarillo, Cuttack, Espoo, Himeji, Samut Prakan, and Aktobe. The set covers six continents, UTC−6 to UTC+10, and representative tropical, Mediterranean, subtropical, continental, and semi-arid climate zones.
The API endpoints, schemas, response formats, and localization remain the same as production. Historical and forecast depth, location coverage, and usage limits differ. Production plans unlock more than 2,150,000 populated locations worldwide without requiring endpoint or code changes.
MCP server endpoint: https://api.meteoprog.com/mcp
[mcp_servers.meteoprog]
url = "https://api.meteoprog.com/mcp/"
bearer_token_env_var = "METEOPROG_API_KEY"Set the environment variable before starting the client:
export METEOPROG_API_KEY="your_meteoprog_api_key"Claude Desktop and other JSON-configured clients use the same remote URL and Bearer authentication pattern. The exact settings screen depends on the client.
Recommended smart tools
| Tool | Best for |
|---|---|
get_weather |
Current weather and forecasts |
compare_weather |
Comparing 2–10 locations |
resolve_location |
Finding a canonical city and ID |
get_weather_alerts |
Active alerts by city, coordinates, or country |
explain_weather_alert |
Explaining an alert against current conditions |
get_air_quality |
Five-day AQI and pollutant summaries |
get_astronomy |
Sunrise, sunset, Moon, and daylight |
get_climate_history |
Historical extremes and climate summaries |
get_geomagnetic_activity |
Kp and G-index observations and forecasts |
get_water_temperature |
Water-temperature searches |
get_service_status |
Meteoprog service health |
The server also exposes low-level OpenAPI tools for exact endpoints, raw responses, geometry, historical data, and advanced integrations. Use those when direct control is required; for ordinary questions, smart tools produce clearer and smaller results.
Accuracy, usage, and expected behavior
Exact hourly forecasts are available within the next seven days. Farther dates may use a daily monthly-model summary and are marked as less precise. Monthly values are useful for broad planning and trend analysis, not exact hourly decisions.
Each upstream Meteoprog API request is accounted for separately. The MCP server does not cache weather responses, so results reflect the data available at request time. If a known city ID or coordinates are supplied, the server can avoid a separate city-name search.
Operations that could require more than 100 upstream requests require confirmation from the user. This is most relevant to large historical comparisons and bulk requests.
Write better weather questions
- Include the city and country when a name may be ambiguous.
- Add a date and local hour for a precise forecast.
- List multiple locations in one comparison request.
- Include the month and year for a monthly forecast.
- Specify a city, country, or coordinates for alerts.
- State the preferred response language.
- Ask for a summary or table when you want a concise result.
The full MCP server exposes 13 user-oriented smart tools and 52 low-level tools generated from the Meteoprog API, for 65 tools in total.