get_cities
Get list of all available cities/locations with Aare data
LABSCO SUMMARY
A thin wrapper over one river's data, with the version knob left in the caller's hands.
The split between get_current_conditions and get_today_summary is the part that earns its place: one returns temperature, flow and forecasts, the other returns the temperature and the swimming recommendation, so an agent answering whether it is worth swimming does not have to carry a forecast payload to do it. The cost of the design is that app, values and version ride on every request including get_cities, so a client that hardcodes them once is pinned to that upstream version until someone edits the code.
What it is
A client for the Aare.guru data with 5 tools: the list of locations that carry Aare data, current conditions for one of them, a minimal reading for today, one response covering all locations, and historical time series.
What you get
- The location list as its own call: get_cities returns the cities and locations that have Aare data, so a client never has to guess a city string before asking for conditions.
- Two depths on the same question: get_current_conditions returns current data for one city including temperature, flow and forecasts, while get_today_summary returns the minimal current temperature and the swimming recommendation for that location and nothing else.
- Every location in a single response: get_widget_data returns current Aare data for all locations at once, which is the shape a dashboard or a widget actually wants.
- History with an explicit window: get_historical_data takes start and end and returns time series for water temperature, flow and air temperature.
- Payload and API version decided at the call: get_cities, get_current_conditions, get_today_summary, get_widget_data and get_historical_data each take app, values and version, so the upstream version and the fields requested are chosen per request rather than fixed at install.
Requirements
No account and no key. Every call carries app, values and version, so what you need on hand is the app identifier the request should be attributed to, the field set you want back in values, and the upstream API version — plus a city name from get_cities for the location-specific tools. Distributed under GPL-3.0, so a modified copy passed on carries the same terms.
Setup effort
One command — npx aareguru-mcp
USE CASES
01
Deciding whether to swim this afternoon
Find the location name the data is published under, then ask for the current temperature and the swimming recommendation without pulling a forecast.
02
Building a board that shows every location
Take all locations in one response instead of looping the per-city call, in the shape a widget or dashboard consumes.
03
Comparing this week against an earlier stretch
Ask for water temperature, flow and air temperature across a start and end window, and read the current conditions alongside for context.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_current_conditions
Get comprehensive current Aare data for a specific location including temperature, flow, forecasts
get_historical_data
Get historical time series data for water temperature, flow, and air temperature
get_today_summary
Get minimal current Aare temperature and swimming recommendation for a location
get_widget_data
Get current Aare data for all locations at once, suitable for widgets/dashboards
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected.
Requires
- npx on PATH
- Node.js 18 or later
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"aareguru-mcp": {
"command": "npx",
"args": [
"aareguru-mcp"
]
}
}
}npx
TERMINAL
npx aareguru-mcp
