General Tools

permitbird.com

An MCP server for determining applicable US Army Corps of Engineers nationwide permits and NPDES stormwater permit requirements for projects affecting waters of the US or construction/industrial sites.

1 endpoint8 known toolsFirst detected September 16, 2026Last detected September 16, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: permitbird
Version: 1.0.0

Capabilities

tools

Server instructions

Determine which NPDES stormwater permit governs a US construction or industrial site, what that permit requires of it, and whether the state requires a credentialed preparer. No model: every answer is a deterministic projection of a cited permit, so identical input always returns an identical determination, and every requirement carries the permit section it came from. A confidence of "unverified" on any fact means it could not be confirmed against the official source and must be presented as unverified, not as fact. Where we have not read a jurisdiction's permit, the requirement list comes back EMPTY with an explanation in `notices`; that means unknown, never "nothing is required". Always surface `notices` verbatim. Two limits are absolute and belong in any answer you give a user: this service does not perform the physical site inspections the permit requires, which a qualified person must carry out on site, and in a state that requires a credentialed preparer any document generated from this data is a draft for that person to review, amend and sign rather than a compliant filed plan. This is regulatory information citing published permits, not legal or engineering advice, and it is not a permit. Every tool is free and keyless, throttled by IP; an API key only lifts the rate limit.

Known tools 8

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

determine_stormwater_permit

Determine which NPDES stormwater permit governs a construction or industrial site, and what that permit requires of it.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.