iris-weather-mcp
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-mcpget 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.
iris-weather-mcp
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 (officialmcpSDK, 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 intests/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.
Running the tests
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
License and contributing
Apache-2.0, the same license as iris-harness (see LICENSE). Contributions follow
CONTRIBUTING.md.
This server cannot be deployed
Maintenance
Related MCP Connectors
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.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides weather forecasts and active alerts for US locations using the National Weather Service API. It supports both local stdio and remote HTTP/SSE transport modes for flexible integration with MCP clients.91 npmGPL 3.0
- AlicenseNot gradedqualityBmaintenanceExposes weather data from the free Open-Meteo API via decorator-driven MCP tools with Zod schemas, supporting stdio and HTTP transports.17 npmMIT
- AlicenseAqualityCmaintenanceMCP server for weather forecasts via Open-Meteo (no API key needed), providing current weather, hourly, and daily forecasts with geocoding support.3MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server providing worldwide weather via the free Open-Meteo APIs (no API key needed). Runs fully self-contained in Docker as a streamable-HTTP MCP service.-