INDIVIDUAL MCP TOOL

get_stormwater_requirements

The requirements for a site: inspection frequency, stabilisation deadlines, Notice of Intent and Notice of Termination deadlines, corrective-action windows, record retention and buffer rules, each citing the permit section it came from.

permitbird.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://www.permitbird.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_stormwater_requirements and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

permitbird.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.permitbird]
url = "https://www.permitbird.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "permitbird": {
      "type": "http",
      "url": "https://www.permitbird.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: permitbird
Remote MCP URL: https://www.permitbird.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "permitbird": {
      "url": "https://www.permitbird.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "permitbird": {
      "type": "http",
      "url": "https://www.permitbird.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "permitbird",
  "transport": "streamable-http",
  "url": "https://www.permitbird.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

determine_nwp_pathway — Determine which of the 57 US Army Corps of Engineers nationwide permits (2026 reissuance, 91 FR 768, effective 15 March 2026) could authorise a project's impact to a wetland, stream or other water of the United States, whether a pre-construction notification is triggered, and what still needs checking at the district and state Section 401 layers.
lookup_nationwide_permit — The compiled record for one nationwide permit: title, summary, acreage limit (including the tidal/non-tidal split where the permit sets one), whether a pre-construction notification is always, never or conditionally required, and the source citation.
list_nwp_reference_data — The reference sets behind determine_nwp_pathway: all 38 USACE districts (name, division, member states, whether regional conditions are compiled), all 54 states/territories (whether the Section 401 certification is compiled), or the activity-to-candidate-permit mapping.
determine_stormwater_permit — Determine which NPDES stormwater permit governs a construction or industrial site, and what that permit requires of it.
get_preparer_credential — Whether a state requires a credentialed preparer (California's Qualified SWPPP Developer, and the analogous credential elsewhere) to prepare or sign a stormwater pollution prevention plan, and whether that requirement bites for a site of this size.
list_jurisdictions — Every state, territory and DC we hold a row for: NPDES authorisation status, the governing permit and its number, the agency name and URL, and the preparer-credential gate.
get_usage — What the credential on this connection is allowed to do: the tier it resolves to (anonymous, sandbox, test key, or a live key on a plan), the per-minute burst, the daily or monthly allowance, and whether calls bill.