Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@iris-weather-mcp get the 5-day forecast for Austin, Texas"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The weather plugin's forecast tool as a standalone MCP server process, run through the
harness's signed MCP bridge, with no import of iris_harness in the plugin process.
This is the experiment of
iris-harness#82: comparison data for
the trust-ladder / isolation question, not a production proposal. The server itself is
standalone; the comparison tests are built against iris_harness's stable tier where possible and
record in docs/GAPS.md (GAP-M1) the places where they had to import non-stable modules (the
MCP bridge and its signing package), because the stable tier offers no MCP surface.
src/iris_weather_mcp/: the server (official mcp SDK, stdio). Dependencies: mcp, httpx.
tests/: the comparison suite. It runs in a SECOND venv that holds the harness wheel and
spawns the server with the first venv's interpreter. Fault fixtures are stdlib-only servers
in tests/servers/; the upstream is a loopback stub.
docs/COMPARISON.md: in-process vs MCP, per graduation property, with evidence.
docs/GAPS.md: what the bridge and SDK could not do, as precise findings.
scripts/ci_local.sh: the local gate (two fresh venvs, lint, isolation proof, tests).
The in-process plugin (../iris-weather-plugin) is the control arm and is not modified.
iris-harness is not on a package index yet (iris-harness#108). scripts/ci_local.sh is the
gate: it builds two throwaway venvs (the server's, with no harness; the test host's, with an
iris-harness wheel built from the clone given by IRIS_HARNESS_CLONE, default
../iris-harness, or a prebuilt wheel in IRIS_WHEEL_DIR), lints, scans the server source,
and runs the suite. The control arm (tests/test_compare.py) imports a sibling checkout of
iris-weather-plugin at
../iris-weather-plugin; it is skipped, loudly, when that is absent. There is no hosted CI for
this repository.
Related MCP server: weather-mcp
Apache-2.0, the same license as iris-harness (see LICENSE). Contributions follow
CONTRIBUTING.md.
Explain a WMO weather code in words. Args: {"code": int}.
Inputs: code (required). Returns: result
Get the daily weather forecast for a place from Open-Meteo. Args: location (str), days (int 1-16, default 3).
Inputs: location (required), days. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: one decodes a WMO weather code, while the other retrieves a daily forecast. There is no overlap or ambiguity in what each tool does.
Both names use consistent snake_case with a shared `weather_` prefix, which makes them predictable. The pattern is noun-based rather than verb_noun (e.g., `weather_code_meaning` is a bit noun-heavy), so it is slightly less action-oriented than ideal, but still consistent.
Two tools is on the thin side for a weather server; it covers forecast and code interpretation but lacks surface area for common weather queries. The count is borderline rather than clearly appropriate or excessive.
The surface covers daily forecasting and WMO code explanation, but missing current conditions, hourly data, historical weather, or alerts means common weather requests cannot be fulfilled. These are notable gaps for an agent expecting a general-purpose weather service.
Hosted MCP server for Xweather weather data: conditions, forecasts, alerts, and more.
Open-Meteo MCP — weather forecast + historical reanalysis + sister APIs
MCP server for weather with reasoning — umbrella advice, outdoor checks, city comparisons.
Open-Meteo tabanlı anahtarsız hava durumu tahmin MCP sunucusu.