What is KS State Lands?
Kansas state lands aggregated from the AGOL tenant shared by KSDOT/KDWP/KSU (services1.arcgis.com). Four curated layers: protected_areas/0 (~993 KDWP-curated all-publicly-managed-land polygons across 95 owners and 99 managers — Kansas Dept of Wildlife Parks Tourism, US Army Corps of Engineers, US Fish and Wildlife Service, US Forest Service, Bureau of Land Management, plus all state parks, county parks, city parks, NGO holdings — no county column); PADUS4_1VectorAnalysis_KS_Only/0 (~3,127 USGS PAD-US 4.1 ownership polygons — 5 Category values Designation 1840 / Fee 1041 / Easement 119 / Other 41 / Proclamation 86; 8 Mang_Type codes FED/STAT/LOC/PVT/NGO/TRIB/JNT/DIST; 21 Mang_Name codes BLM/FWS/USFS/NPS/USACE/USBR/SLB/SPR/SFW/CITY/CNTY/REG/NGO/PVT/TRIB/JNT/UNKL/OTHF/OTHS/NRCS/DOD; 4 Pub_Access codes OA Open / RA Restricted / UK Unknown / XA Closed; 4 GAP Status codes 1-4 — conservation easements via category=Easement, fee parcels via category=Fee); KDWPT_Wildlife_Areas/0 (~213 state wildlife areas + state parks + state fishing lakes, with COMPLEX = federal reservoir name when KDWPT manages USACE shoreline land at Tuttle Creek/Perry/Cheney/Milford/Kanopolis/Wilson/El Dorado/Glen Elder/Marais Des Cygnes; Access_Res values Yes/No/Archery Only/Archery+Shotshell Only/AS Only/Special Hunts Only); KDWP_WIHA_Update_9_10_25/0 (~3,736 Walk-in Hunting Area private-lands public-access tracts with COUNTY column Title Case + ACRES + CONTRACTSTATUS + CONTRACTTYPE + CONTRACTNAME + ISARCHERYSHOTONLY + YEARCONTRACTBEGINS/YEARCONTRACTENDS + 10 SPECIES columns + POINTOFCONTACT + LEGENDID). §0 surprises: KS DASC Hub (hub.kansasgis.org) DCAT feed has no state-lands ownership / parcels / conservation-easements layer of its own; the KS Adjutant General GIS hub publishes no standalone state-lands FeatureServer either (only TIGER military boundaries show up in DASC's catalog with 7 polygons led by McConnell AFB). PAD-US KS has no county column — use bbox/near for county-level filtering. WIHA service has been renamed every season for the past five years (2019_iWIHA → 2020_2021_WIHA → ... → KDWP_WIHA_Update_9_10_25); handler hard-codes the latest stable name and falls back to 2025_2026_WIHA_REVIEW if it disappears. KDWP_protected_areas Owner has 95 distinct values and Manager has 99 — broader than just state-trust land. Native CRS EPSG:102100 (Web Mercator); handler requests outSR=4326. Last verified live 2026-05-08.
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 KS State Lands with the toggle — no credentials needed.
Call searchPublicLandsOwnership with category: 'Easement' to list all 119 Kansas conservation easements, or searchWalkInHuntingAreas with county: 'Sedgwick' for that county's Walk-in Hunting tracts.
Connect to Your AI Assistant
Choose your AI assistant below for specific setup instructions
Follow these steps to connect KS State Lands 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 KS State Lands 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 KS State Lands 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:
"KS State Lands-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"
}