Skip to main content
Glama
EdgeworthHitbox

Colorado DWR MCP Server

by EdgeworthHitbox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Colorado DWR MCP Server

No user-submitted related servers found.

    Related Servers

    • usgswater

      pipeworx-io
      A
      license
      Not graded
      quality
      F
      maintenance
      Wraps USGS NWIS REST services to query water data such as streamflow, groundwater levels, and water quality.
      3 npm
      MIT

    • SNOTEL MCP Server

      jymmyt
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to real-time and historical snow conditions, weather data, and snowpack analysis from over 800 SNOTEL stations across the western United States through the USDA Air and Water Database API.
      2
      MIT

    • mcp-usgs-water-data

      higherpass
      A
      license
      A
      quality
      C
      maintenance
      Enables querying USGS water data including real-time and historical streamflow, gage height, and water temperature from USGS gauges across the United States.
      3
      MIT

    • water-quality-portal

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying and retrieving US water-chemistry data, including station metadata, sample results, and controlled vocabularies from the Water Quality Portal.
      18 npm
      MIT

    • cdec-ca

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying California hydrology data including reservoir storage, snow water content, stream gauges, and historical/real-time station data from CDEC via MCP tools.
      41 npm
      MIT

    • mcp-data-colorado

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Access Colorado government open data via Socrata SoQL API. Enables searching datasets, running queries, and retrieving metadata without an API key.
      23 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources