4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
USGS Water Services MCP Server

Bring Hydrology
to CrewAI

Learn how to connect USGS Water Services to CrewAI and start using 5 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Daily ValuesGet Groundwater LevelsGet Instantaneous ValuesGet SitesGet Statistics

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
USGS Water Services

What is the USGS Water Services MCP Server?

Connect to the USGS Water Services to retrieve comprehensive hydrological data directly from the United States Geological Survey. Monitor environmental conditions, analyze historical trends, and discover monitoring stations through natural language.

What you can do

  • Real-time Monitoring — Use get_instantaneous_values to fetch near real-time data (15-minute intervals) for streamflow, water levels, and quality.
  • Historical Analysis — Retrieve daily summaries (mean, median, max, min) using get_daily_values for long-term trend analysis.
  • Site Discovery — Search for monitoring stations using get_sites filtered by state, county, hydrologic unit (HUC), or geographic bounding box.
  • Statistical Reports — Generate daily, monthly, or annual statistics with get_statistics to understand hydrological patterns.
  • Groundwater Tracking — Access specialized groundwater level data using get_groundwater_levels for aquifer monitoring.

How it works

  1. Subscribe to this server
  2. This service accesses public USGS data; simply enter 'PUBLIC' as your access key to initialize
  3. Start querying water data from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Environmental Scientists — quickly gather field data and historical records for research and reporting
  • Engineers & Hydrologists — monitor streamflow and groundwater levels for infrastructure and flood planning
  • Outdoor Enthusiasts — check real-time river conditions for fishing, boating, or safety before heading out

Built-in capabilities (5)

get_daily_values

You MUST provide at least one major filter. Retrieve historical summarized daily data (mean, median, max, min)

get_groundwater_levels

You MUST provide at least one major filter. Retrieve historical manually-recorded groundwater levels

get_instantaneous_values

You MUST provide at least one major filter: sites, stateCd, huc, bBox, or countyCd. Retrieve near real-time water data (usually 15-minute intervals)

get_sites

Multiple major filters can be combined (AND logic). Search for USGS sites and metadata

get_statistics

Retrieve daily, monthly, or annual statistics based on approved data

Why CrewAI?

When paired with CrewAI, USGS Water Services becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call USGS Water Services tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

USGS Water Services in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

USGS Water Services and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect USGS Water Services to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for USGS Water Services in CrewAI

The USGS Water Services MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 5 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

USGS Water Services
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures USGS Water Services for CrewAI

Every tool call from CrewAI to the USGS Water Services MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I find all water monitoring sites in a specific state?

Use the get_sites tool and provide the 2-digit USPS state code (e.g., 'CA' for California) in the stateCd parameter. This will return a list of sites and their metadata for that state.

02

Can I get real-time streamflow data for a specific river station?

Yes! Use get_instantaneous_values with the specific USGS site number in the sites parameter. You can also specify parameterCd as '00060' for discharge (streamflow).

03

Is it possible to retrieve long-term monthly averages for a site?

Absolutely. Use the get_statistics tool with the statReportType set to 'monthly'. This will provide approved statistical summaries based on the historical record of the site.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →