Usgs Water vs Filesystem

A side-by-side look at the Usgs Water and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Usgs Water logoUsgs WaterEnvironment & Nature · Local subprocess (stdio)USGS Water Services (NWIS) MCP.52GoodAuth: not declaredFilesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth required

Verdict: choose Usgs Water for environment & nature work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Usgs Water logoChoose Usgs Water when

  • You need dedicated capabilities in the Environment & Nature domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like current_conditions, daily_values, find_sites.
Explore Usgs Water

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like path, head, tail.
Explore Filesystem

Feature & specification comparison

Rows where the two servers differ are marked.

SpecUsgs Water logoUsgs WaterFilesystem logoFilesystem
CategoryEnvironment & NatureFile Systems
Quality signal52/100 · Good85/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars091,512
Directory activity 1 views 0 installs 0 upvotes 9 views 0 installs 0 upvotes
Tools317

Tools & capabilities

Usgs Water tools 3

  • current_conditionsLatest instantaneous (real-time) readings for one or more USGS gauge sites. Returns the most recent value per site × parameter — e.g. current streamflow and gage height for a river. Common parameter codes: 00060 = discharge/streamflow (ft³/s), 00065 = gage height (ft), 00010 = water temperature (°C…
  • daily_valuesDaily-values time series for a single USGS site + parameter over a date range. Returns one statistic per day (default mean). Useful for trends, hydrographs, and historical comparison. Common statCd: 00003 = mean, 00001 = max, 00002 = min. Common parameter codes: 00060 = discharge (ft³/s), 00065 = g…
  • find_sitesDiscover active USGS gauge sites in a US state that are currently reporting a given parameter (real-time). Returns sites with their latest reading; useful for finding which gauges are live in a region. Can match many sites, so results are capped. Keyless.

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Usgs Water

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "usgs-water": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usgs-water"
      ]
    }
  }
}

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

Frequently asked questions

Usgs Water is categorized under Environment & Nature and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Usgs Water for environment & nature work and Filesystem for file systems.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Usgs Water has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add usgs-water and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Usgs Water has a quality signal of 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Filesystem has 85/100 (Excellent) with 9 views, 0 installs and 91,512 GitHub stars.