Inspect model metadata and select terrain and regional gauge evidence for a HEC-RAS data handover. Compare listed sources, access requirements and evidence for hec-ras terrain and flow inputs.
4 sources · For flood consultants, hydrologists, GIS analysts, civils engineers, drainage engineers, environmental scientists, hydraulic modellers, water quality specialists. Enrichment describes potential applications; review source evidence and limitations.
UK and US gauge sources are alternatives by jurisdiction; neither replaces local channel or structure surveys.
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.
MCP Server to Access HEC-RAS Project Data via Claude Desktop, Claude Code and other LLMs
What's in it
Data offered docs-verified
server/version information · project length units · plan descriptions · selected project/plan metadata · bounded read-only HEC-RAS project and plan text
Formats docs-verified
MCP stdio
Access docs-verified
Open-source, MIT licence (per registry metadata). Free local install from PyPI with python -m pip install --upgrade ras-commander-mcp. Requires Python 3.10+. No HEC-RAS executable needed. No auth listed in entry.
Useful for
Use cases llm-inferred
Check project length units and plan descriptions in existing HEC-RAS models during flood model QA · Pull selected plan metadata from HEC-RAS text files into a bounded review note for a model handover · Confirm ras-commander and ras-commander-mcp versions in a managed environment before starting modelling work
Read-only: does not modify projects, compute, read HDF/DSS, inspect geometry, extract gridded data, export files or download into projects · Project metadata and plan configuration need ras-commander 0.104.0; on 0.103.0 those tools return an availability error · Project tools are meant only for bounded informational subagents; other hosts need a scoped Python workflow · Only project roots listed in RAS_MCP_ALLOWED_ROOTS are readable; no roots are trusted by default · Claude Code plugin is forthcoming and its repository is not yet published · Version 0.4 replaces the 0.3 tool set and needs migration · Windows: other tools in a workflow may still fail on paths over 260 characters · Independent project, not affiliated with or endorsed by USACE HEC
Environment Agency survey portal for LiDAR terrain and surface models and other survey data.
What's in it
Data offered llm-inferred
LiDAR terrain model · LiDAR surface model · other survey data
Coverage llm-inferred
England
Useful for
Use cases llm-inferred
Flood risk assessment: ground-level inputs for hydraulic model topography · Drainage strategy: surface levels for catchment and overland flow delineation · Civils design: existing ground model for earthworks and levels
USGS water observations and monitoring-location metadata through modern water-data APIs.
What's in it
Data offered docs-verified
continuous sensor measurements · daily values · time series metadata · monitoring-location metadata · water quality samples · discrete water-quality data (Water Quality Portal) · gaging-station imagery (NIMS) · daily, monthly and annual statistics
Coverage llm-inferred
United States
Formats docs-verified
OGC API · STAC
Access docs-verified
Free to use; API key optional for higher rate limits. Licence not stated.
Useful for
Use cases llm-inferred
Baseline river flow and gauge record review for FRA inputs from nearest USGS gauge (US sites only) · Flood event analysis from continuous sensor records at gauged catchments · Water quality baseline sampling review for environmental assessment (US sites only) · Gauge camera imagery for site visit verification and condition checks
Covers United States monitoring locations only; not applicable to UK sites · Rate limits apply without an API key · Licence not specified in catalogue metadata · Multiple API families (OGC, STAC, legacy Water Services, NIMS) may require different query patterns · NIMS imagery requires constructing full image URLs from camera base paths and returned filenames
Which listed sources support HEC-RAS terrain and flow inputs?
Start with RAS Commander MCP, Defra Data Services Platform LiDAR, USGS Water Data API. Inspect model metadata and select terrain and regional gauge evidence for a HEC-RAS data handover.
What should I check before using these sources for hec-ras terrain and flow inputs?
UK and US gauge sources are alternatives by jurisdiction; neither replaces local channel or structure surveys.
How do I inspect RAS Commander MCP through MCP?
Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug ras-commander-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.