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., "@Colorado DWR MCP Server show me streamflow data for the South Platte River near Denver"
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.
This is a Model Context Protocol (MCP) server that interfaces with the Colorado Division of Water Resources (DWR) REST API. It allows AI models to retrieve water data, rights, permits, and administrative calls.
Surface Water Stations: Search for stations by name, location, etc.
Surface Water Time Series: Get daily time series data (streamflow, etc.).
Water Rights: Query net amounts and transactions.
Well Permits: Search for well permits.
Administrative Calls: Get active administrative calls.
Generic Query: Flexible tool to query any DWR API endpoint.
Related MCP server: mcp-data-colorado
Clone this repository.
Install dependencies:
npm installBuild the server:
npm run buildnode build/index.jsnode build/sse.jsThis will start a server at http://localhost:3000.
SSE Endpoint: http://localhost:3000/sse
No API key is strictly required for basic usage, but if you have one, you can set it via the DWR_API_KEY environment variable.
get_surface_water_stations
get_surface_water_ts_day
get_water_rights_net_amount
get_well_permits
get_active_admin_calls
query_dwr_api
Run the test client to verify functionality:
npx tsx test_client.tsGet active administrative calls
Inputs: division.
Search for surface water stations in Colorado
Inputs: stationName, division, county, waterDistrict, +1 more.
Get daily time series data for a surface water station
Inputs: abbrev (required), startDate (required), endDate (required).
Get net amounts for water rights
Inputs: waterRightName, division, pageSize.
Search for well permits
Inputs: wellName, receipt, pageSize.
Generic tool to query any Colorado DWR REST API endpoint
Inputs: endpoint (required), params.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Most tools have distinct purposes targeting different DWR resources like administrative calls, surface water stations, water rights, and well permits. However, 'get_surface_water_stations' and 'get_surface_water_ts_day' could potentially be confused as both relate to surface water stations, though their actions (search vs. get time series) differ. The 'query_dwr_api' tool is clearly distinct as a generic fallback.
All tools follow a consistent 'get_' or 'query_' verb prefix with snake_case naming, making them predictable and readable. The pattern is uniform across all six tools, with no deviations in style or convention.
With 6 tools, the count is reasonable for a DWR data server, covering key resources like water stations, rights, and permits. It's slightly lean but not inadequate, as the generic 'query_dwr_api' tool can extend functionality. A few more specialized tools might enhance coverage, but this is well-scoped.
The tools cover read operations for major DWR data types, but there are notable gaps in lifecycle coverage. For example, there are no tools for creating, updating, or deleting records, which might be expected in a full administrative system. The generic query tool helps mitigate this, but the surface is incomplete for CRUD workflows.
Query real-time and historical USGS water data from ~8,000 stream gages and groundwater wells.
USGS Water MCP — wraps USGS National Water Information System (NWIS) REST services (free, no auth)
Real-time water levels and flow rates from USGS stream gauges
USGS Water Services (NWIS) MCP.