NEPA-MCP

Case study · Policy

DOE sponsor and ACRES Brownfields contributor to PNNL’s environmental-data toolkit. 1 merged PR; 4 open PRs.

Stack
23 MCP servers, 88 research capabilities, 32 GIS layers; Python, published to PyPI. Built and maintained by PNNL.
Status
LIVE
Dates
Reviewed November 6, 2026
Links
Live site · Source code

Background

What federal, state, and local rules actually govern environmental review for a given project site?

NEPA-MCP is PNNL's PermitAI toolkit. Its 23 MCP servers provide 88 research capabilities and 32 GIS layers from 13 federal agencies. I sponsored the project at DOE and contributed the EPA ACRES Brownfields server.

Species, floodplain, historic-district, air-quality and contaminated-site records reside in separate federal systems. The toolkit lets an AI assistant query them during preliminary screening. It does not replace agency or Tribal consultation.

My Contributions

I sponsored NEPA-MCP at DOE and built its EPA ACRES Brownfields server, merged in PR #24. It returns grant-reported properties near a project area, with EPA record links and coverage limits.

My other PRs cover Superfund, former defense sites, BRAC installations, and NRC licensing documents.

PR status checked . Open PRs are proposed additions.

Screenshots

Select a screenshot to enlarge it.

PermitAI's federal environmental-data toolkit for NEPA screening (mobile) PermitAI's federal environmental-data toolkit for NEPA screening (desktop)
PermitAI's federal environmental-data toolkit for NEPA screening — 23 MCP servers across 13 agencies, built by PNNL.
The Map Composer server: federal GIS layers (mobile) The Map Composer server: federal GIS layers (desktop)
The Map Composer server: federal GIS layers — habitat, soil, flood, cultural — composed into one screening map, shown here with 11 of 32 layers over a Chesapeake Bay project area.

← Back to Homepage