mcpField
W
water-conditions

water-conditions

Local
github.com/aybeeareMaps & Travel0Updated 15w ago
Repository

About water-conditions

water-conditions provides real-time water temperatures and tide predictions for lakes, rivers, bays, oceans, and beaches. It supports place names or coordinates and combines data from NOAA, USGS, and seatemperature.info for travel and water-condition lookups.

Key features

  1. 01Retrieve real-time water temperatures and tide predictions
  2. 02Query by place name or coordinates
  3. 03Match coordinates to nearby stations automatically
  4. 04Cover North America and major international waters

Use cases

  1. 01Check beach temperature and tides before a trip
  2. 02Look up water conditions near given coordinates

MCP support

It exposes the get_water_conditions tool to MCP clients for water temperature and tide prediction queries.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "aybeeare-water-conditions": {
      "command": "uvx",
      "args": [
        "water-conditions-mcp"
      ]
    }
  }
}
Run commanduvx water-conditions-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiwater-conditions-mcp1.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Get real-time water temperature and tide prediction data for any lake, river, ocean, bay, or beach by name or latitude/longitude coordinates. Data sourced live from NOAA CO-OPS, USGS, and seatemperature.info, with automatic nearest-station matching for coordinate inputs. Coverage includes 8,000+ named locations across North America and major international bodies, with string to coordinate geocoding for fallback.

mcp-name: io.github.aybeeare/water-conditions

Roadmap: national sensor network expansion

Today's accuracy hierarchy is USGS/NOAA (real government sensors, ground-truth for the exact station) > seatemperature.info (best-guess aggregator, no known dedicated sensor network, used for everywhere else via geocoding). The plan is to extend the first tier — real sensor networks, wired in the same way as USGS/NOAA — country by country, rather than leaning on the aggregator fallback long-term. Goal: a genuine "super API" blending national sensor networks the way this project already blends USGS + NOAA.

Confirmed and ready to integrate (free, open, no API key required):

  • UK Environment Agency — best next candidate. Hydrology API (river flows/levels/groundwater, ~8,000 stations, 15-min resolution) + Flood Monitoring API (river/tide levels) — same openness and simplicity as USGS/NOAA, Open Government Licence.
  • France SHOM/REFMAR — ~100 real-time tide gauges, Licence Etalab 2.0.

Investigated, more complex integration:

  • Copernicus Marine Service (EU/global sea surface temperature, satellite + in-situ) — free and authoritative, but the bulk data products are scientific-grade (NetCDF via a Python toolbox) rather than simple per-station JSON. Has a REST "In Situ Dashboard" worth a closer look.

Investigated, unclear near-term path:

  • East Asia (Japan JMA/JODC, Korea KMA) — both have relevant agencies, but access looked more fragmented/licensed than the UK case in an initial search (Japan's tide data appears to route through an authorized distributor, not a clean open endpoint). Needs real investigation before committing — not a near-term target.

North America (USGS/NOAA) + Europe (UK EA, France SHOM) covers the current priority footprint well. Everything else stays on the geocoding + seatemperature.info fallback until/unless a specific region's sensor network turns out to be worth the integration effort.

Checking MCP activity (owner only)

Every call to the get_water_conditions tool is logged in the database. To pull a summary from the live server:

1. One-time setup — set ACTIVITY_API_KEY in Railway (already done). Note the value somewhere safe.

2. Run the activity script — open a terminal in this project folder and run these two commands:

$env:ACTIVITY_API_KEY="your-secret-here"
python scripts/activity.py

This prints total calls, unique locations queried, success rate, and the last 50 individual calls with timestamps and temperatures.

The $env: line only needs to be run once per terminal session. After that you can re-run python scripts/activity.py as many times as you like.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.