What is AL Department of Environmental Management?
Alabama Department of Environmental Management environmental permits, UST sites, brownfields, Justice40 census tracts, and public complaints via agency data services. Five curated layers from ADEM's sprawling 110+ data services catalog: layer 0 ADEM e-Permitting + Compliance Activities (~83,663 points covering 42 distinct permit categories including Industrial Individual Permit, Industrial General, MS4 General/Individual, Construction General, Mining General/Individual, Stormwater, Stage 1 Air Permit, Solid Waste Landfill / Post Closure, UIC Class 1/3/5 + General, CAFO Registration, Asbestos Notification/Contractor, Bulk Gasoline Plant, Materials Recovery, Recycling, Scrap Tire Facility/Landfill/Processor/Transporter, Coastal Variance, 401 WQC, Pesticides, Storage Tank Registration; 12 STATUS values: Closed/Expired/Expired (Inactive)/Extended/In Effect/In Process/Issued (Not In Effect)/Post Closure/Superseded/Suspended/Terminated/Terminated (Can Re-Register)); layer 0 (~10,347 underground storage tank facilities; SITE_ID_COUNTY uses 3-digit FIPS strings only — handler maps county names to FIPS internally); layer 0 ADEM Brownfield Events (~776 sites with site number, master ID, address, county, recorded owner, approx acres, last activity date); layer 4 Justice40 Disadvantaged Census Tracts (~655 polygons; 248 CEJST methodology fields covering demographics + screening factors + DF_PFS / AF_PFS / HDF_PFS / DSF_PFS / EBF_PFS / EALR_PFS / EBLR_PFS / EPLR_PFS / HBF_PFS / LLEF_PFS / LIF_PFS / LMI_PFS / MHVF_PFS / PM25F_PFS / etc.); layer 0 (~12,988 public environmental complaints; Media is exactly 4 UPPERCASE values AIR/COASTAL/LAND/WATER; Status is exactly 2 UPPERCASE values OPEN/CLOSED). §0 surprises: AEPACS uses both lowercase `object_id` (Double, duplicate) and uppercase `ESRI_OID` (actual OID, esriFieldTypeOID) — handler reads ESRI_OID. AEPACS does NOT support `aggregation` reliably and refuses `distinct-values=true` with geometry (`Geometry is not supported with DISTINCT.`). UST_Sites SITE_ID_COUNTY is 3-digit FIPS-only with no county-name column — handler exposes a county filter that accepts FIPS or county name and resolves via embedded 67-county map. Brownfields County column has casing inconsistencies ('DeKalb' 9 + 'De Kalb' 4 same county) and whitespace bugs (' Montgomery ' with leading + trailing spaces) — handler trims + uppercases. Brownfields LastActivityDate is a STRING formatted '10/20/2025 2:12 PM' (NOT epoch ms) — handler parses with new Date(...). AEPACS native CRS EPSG:26916 (NAD83 UTM Zone 16N), other layers EPSG:3857; Last verified live 2026-05-07.
Available Tools
Requirements
- Toggle onToggle on and use — no setup needed.
Quick Setup Guide
Follow these steps to connect your AI agents to this connector
Open /mcp and enable AL Department of Environmental Management with the toggle — no credentials needed.
Call searchPermits with permitCategory: 'Stage 1 Air Permit' and status: 'In Effect' for active major air sources, or searchUSTSites with county: 'Mobile' (handler maps to FIPS 097) for Mobile County tank sites.
Connect to Your AI Assistant
Choose your AI assistant below for specific setup instructions
Follow these steps to connect AL Department of Environmental Management to Claude:
Step 1: Open Claude Settings
Launch Claude → Click the profile button (bottom left) → Navigate to Settings
Step 2: Access Connectors
Scroll down to the Connectors tab → Navigate to the bottom → Click “Add Custom Connector”
Step 3: Name Your Connector
Enter any name you'd like for this connector
Step 4: Get the Connector URL
Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use
Step 5: Add the Connector
Paste the URL in the “Remote MCP Server URL” text box → Click Add
Step 6: Start Using
Your connector is now ready to use in Claude
Follow these steps to connect AL Department of Environmental Management to ChatGPT:
Step 1: Enable Developer Mode
Go to Settings → Connectors → Advanced → Enable Developer mode
Step 2: Create New Connector
Go back to Connectors page → Click “Create” (top right)
Step 3: Name Your Connector
Enter any name you'd like for this connector (descriptions are optional)
Step 4: Get the Connector URL
Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use
Step 5: Add the URL
Paste the URL in the “MCP Server URL” text box
Step 6: Set Authentication
Click the authentication dropdown → Select “No authentication” (PatchOps handles authentication internally)
Step 7: Create the Connector
Click “I understand and want to continue” checkbox → Press Create
Step 8: Using the Connector
Start a new chat → Click the + button (left of text box) → Open dropdown → Hover over three dots labeled “More” → Select your connector
Instructions for connecting AL Department of Environmental Management to GitHub Copilot:
Coming Soon
Detailed setup instructions for GitHub Copilot will be added here.
For other MCP-compatible platforms:
Step 1: Get the Connector URL
Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use
Step 2: Add to Configuration
Add this configuration to your MCP settings file. Replace the URL with your specific connector URL from the /mcp page:
"AL Department of Environmental Management-MCP": {
"url": "https://patchops.ai/api/mcp/...",
"type": "http"
}Example Configuration
Here’s an example using PatchOps MCP:
"PatchOps-MCP": {
"url": "https://patchops.ai/api/mcp/...",
"type": "http"
}