Combine catchment boundaries, river networks and gauge metadata to scope a rainfall-runoff study. Compare listed sources, access requirements and evidence for catchment hydrology mcp.
4 sources · For ecologists, flood consultants, GIS analysts, hydrologists, drainage engineers, environmental consultants using AI-assisted workflows, planners. Enrichment describes potential applications; review source evidence and limitations.
Derived basin boundaries need checking against local drainage and artificial transfers.
Discover sources with MCP
Add this server to an HTTP-compatible MCP client, then call get_source to inspect the first source. The tool call is shown separately from the client configuration. Review upstream access details before requesting data.
streams, rivers and canals with stream order, drainage area, slope, elevation, modelled flow (qama, cfs) and velocity (vama, fps) · lakes, ponds, reservoirs, swamps and areal water features (wide rivers, bays, rapids, dams) · stream gages with NWIS linkage and drainage area · springs, waterfalls, dams/weirs, gates, levees, wells and other water features · HUC12 watershed name, code, downstream HUC, type, area and states
Free, no authentication (public service); underlying USGS data is public domain
Useful for
Use cases llm-inferred
FRA baseline flows: find gauges within a buffered site polygon with hydro_find_gages and read drainage area (dasqmi) and NWIS linkage · Drainage strategy context: identify the HUC12 watershed and its downstream HUC for a site with hydro_identify_watershed · Watercourse and waterbody constraint mapping for planning or ecological screening using hydro_find_waterways and hydro_find_waterbodies · Outfall and culvert screening using modelled EROM flow and velocity from flowline attributes
Each layer caps at 2000 records per request; results set truncated: true when the cap is hit · Feature geometry is not returned, so results are attributes only · Tools are geometry-intersection queries; routed upstream/downstream tracing is not yet implemented · Drainage-area units differ: gages use square miles (dasqmi), flowlines and watersheds use square km · Point and line layers need a Polygon or BoundingBox to reliably capture features · Covers the United States only
Hydrographic basins, rivers and drainage products derived from elevation data.
What's in it
Data offered docs-verified
catchment boundaries · river networks · lakes
Coverage docs-verified
Global
Formats docs-verified
standard GIS formats (not specified in DOCS)
Access docs-verified
Free and freely available; licence not stated in ENTRY or DOCS
Useful for
Use cases llm-inferred
FRA catchment context: delineate contributing catchment boundaries from HydroSHEDS basins · Drainage strategy: river network and lake layers for receiving-watercourse context · Ecology/BNG baseline: river and lake network mapping for habitat context
HydroSHEDS v2 is released for the Americas; the global v2 (TanDEM-X based) is still in development · Specific resolutions, update cadence and licence terms are not stated in DOCS
MCP server exposing Google Earth Engine as a set of MCP tools. These include: dataset discovery, metadata extraction, analysis primitives, and AI-assisted GEE Python code generation.
What's in it
Data offered docs-verified
Google Earth Engine dataset catalogue (list_datasets) · satellite image download · spectral indices (NDVI, NDWI, custom band math) · zonal statistics · temporal composites · area meeting a threshold condition · multi-period comparisons
Coverage llm-inferred
Global
Formats docs-verified
MCP stdio · Markdown (dataset info) · JSON-RPC · XML result shape · Mermaid graph · GEE Python code
Access docs-verified
Open source, MIT licence. Requires a Google Earth Engine project (GEE_PROJECT) with Earth Engine credentials, and an LLM provider API key (Anthropic, Google/Gemini or Vertex AI, or OpenAI) for the AI code-generation tools. Local install via Poetry. Cost not stated in docs.
Useful for
Use cases llm-inferred
Catchment land cover and forest cover percentage for flood risk assessment inputs · Flood extent area from imagery using threshold_area for post-event mapping · NDVI/NDWI change between periods via multi_period_analysis for ecological baselines · Zonal statistics of DEM or land cover over a catchment for morphometry
Requires Google Earth Engine authentication and a GEE project ID · AI code-generation tools need an LLM provider API key · Local install required (Poetry, clone repo); Python 3.11 to 3.14 · Catalogue auth field lists only LLM keys and omits GEE credentials · AI-generated GEE code and factuality outputs need expert verification · No rate limits, SLA or maintenance status stated in docs
Which listed sources support Catchment hydrology MCP?
Start with USGS National Map MCP, HydroSHEDS, NRFA API. Combine catchment boundaries, river networks and gauge metadata to scope a rainfall-runoff study.
What should I check before using these sources for catchment hydrology mcp?
Derived basin boundaries need checking against local drainage and artificial transfers.
How do I inspect USGS National Map MCP through MCP?
Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug usgs-national-map-mcp. Review its provenance, access requirements and limitations before contacting the upstream service. Discovery does not make every listed source directly executable through the router.
Are these sources free and independently verified?
Access and licence terms belong to each upstream provider; some products require registration or payment. Open each listing for evidence, health status and enrichment provenance. A wrapper and its underlying API can refer to the same dataset and are not independent observations.