WEATHER MCP / PUBLIC BETA

Weather, directly
in your AI agent.

Connect ProjectEOL Weather MCP to any Model Context Protocol client. Your agent can find a place by name or fetch a forecast for precise coordinates.

QUICK START

Three steps to the first forecast

1

Add the server

In your MCP client's settings, add a remote server using the URL below. No authentication is needed.

2

Name the place

Ask your agent to find a city. For an exact spot, provide latitude and longitude directly.

3

Get the forecast

The agent chooses the tool and returns available times, values, units, and data provenance.

MCP SERVER URL
https://weatherapi.projecteol.ru/mcp/
TOOLS

Three clear tools

The service follows Model Context Protocol: clients normally expose these tools to the agent automatically, and they can also be invoked explicitly.

SEARCHsearch_locations

Searches the local geographic index and returns a name, country, coordinates, and time zone. Use it before a forecast when you only know a city.

READget_forecast_metadata

Shows the current published dataset: available period, coverage, parameters, model, and source attribution.

READget_weather_forecast

Returns an hourly forecast for latitude and longitude. This is the primary tool: coordinates work for any point on a map, not only cities.

FORECAST ARGUMENTS

What you can refine in a forecast

ArgumentRequiredDescription
latitudeyesLatitude from −90 to 90.
longitudeyesLongitude from −180 to 180.
hoursnoNumber of hourly steps: from 1 to 168. Default: 24.
startnoUTC start time in ISO 8601. If omitted, the nearest available time is used.
parametersnoA list of weather parameter codes. If omitted, the service selects a compact useful set.
interpolationnonearest (default) or linear.
IMPORTANT

Open access, with a careful limit

No key

MCP is public: no account, token, or secret needs to be given to your agent.

60 / minute

The limit applies to the request source and protects the service from accidental loops and overload. On a 429 response, wait a minute.

UTC + units

Forecast times are returned in UTC. Units and data provenance are included in the response—do not guess them.

Need a key, REST requests, or application integration?

For programmatic integration without MCP, use Weather API and its interactive specification.