MS State Lands

Live

Mississippi state lands — state parks, Wildlife Management Areas, and Forestry Commission Section 16 BOE forestry plans. 3 curated layers across 39 state parks, 64 WMAs, and ~1,067 Section 16 forestry plans. No credentials required.

What is MS State Lands?

Mississippi state lands aggregated across two agencies — the Mississippi Forestry Commission (MFC) and a curated parks+WMAs polygon source. Three curated layers: MS State Parks (39 polygons covering Buccaneer / Tishomingo / Percy Quin / Natchez SP / Roosevelt / J.P. Coleman / Clarkco / Florewood River Plantation / Lake Lincoln / Winterville Mounds / Sam Dale / Casey Jones / Nanih Waiya / 26 others); MS Wildlife Management Areas (64 MDWFP-administered polygons including Pascagoula River WMA / Mahannah / Sandy Creek / Malmaison / Black Prairie / Calhoun County / Caney Creek); MS Forestry Commission Section 16 BOE forestry plans (~1,067 polygons — one per Board of Education school-trust parcel under a written stewardship plan; PrimGoal distinct values: Timber Production 573 / Wildlife Management - General 317 / Fire Protection 107 / Aesthetics 25 / Water Quality 21 / AIR QUALITY 10 / Recreation 10 / Environmental Education 3 / Wildlife Management - Deer 1; PlanType: New 721 / Revised 346; District: 1/2/3/4 across 4 MFC districts). Section 0 surprises: Mississippi has NO single state lands portal. The state GIS portal only exposes DEQ hydrography + imagery basemaps; the historic public-data hub MARIS is currently DOWN (no response — handler does not depend on it). The MDWFP server has TWO problems blocking sandbox access — (1) its TLS certificate chain is incomplete (server omits the GlobalSign Atlas R3 OV TLS CA 2026 Q1 intermediate, so Node.js TLS verification fails with 'unable to verify the first certificate' — curl + browsers work via the system keychain fallback), and (2) even when reachable, the MDWFP query endpoint strips polygon geometry on the wire even when geometry is explicitly requested. Both reasons exclude MDWFP — state-lake + boat-ramp datasets are NOT exposed. Park + WMA polygons come from an alternate curated source. The forestry plans dataset exposes client PII upstream (FirstName / LastName / Phone1 / Phone2 / Email / Zipcode / StreetNumber / StreetName) — handler does NOT expose any of those, only parcel-level forestry attributes (PlanName, PlanType, OwnerType, County, District, PrimGoal, Goal2-5, PlanAcres, ClientName which is always a public Board of Education entity). The state-parks+WMAs polygons have a minimal upstream schema — name + shape area only; no county/type/acres columns (acreage approximate from shape area). One park feature has NAME = ' ' (whitespace) — handler treats as null. Toggle on and use — no setup needed. Last verified live 2026-05-08.

Available Tools

searchStateParks
MS state park polygons (39 parks: Buccaneer / Tishomingo / Percy Quin / Natchez SP / Roosevelt / Sam Dale / J.P. Coleman / etc.). Filter parkName substring, bbox, near. Schema is minimal — NAME + Shape__Area only; no county/type/acres columns upstream.
searchWildlifeManagementAreas
MS Wildlife Management Area polygons (64 MDWFP-administered tracts: Pascagoula River / Mahannah / Sandy Creek / Malmaison / etc.). Filter wmaName substring, bbox, near.
searchForestryPlans
MS Forestry Commission Section 16 BOE forestry plan polygons (~1,067). Filter county (Title Case), district (1-4), planType (New/Revised), primaryGoal (Timber Production / Wildlife Management - General / Fire Protection / Aesthetics / Water Quality / Recreation / AIR QUALITY / Environmental Education), planName/clientName, minAcres, treeFarmOnly, certifiedStewardshipOnly. Returns plan + parcel + section-township-range + secondary goals + start/end + plan length.
getServiceInfo
Schema, record counts (live), max-page caps, forestry plan enums (PrimGoal/PlanType/Districts), §0 probe notes including the MARIS-down + MDWFP-TLS-chain surprises.

Requirements

Toggle on
Toggle on and use — no setup needed.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Open /mcp and enable MS State Lands with the toggle — no credentials needed.

Call searchStateParks with parkName: 'Buccaneer' for that park's polygon, or searchWildlifeManagementAreas with wmaName: 'Pascagoula' for the Pascagoula River WMA boundary, or searchForestryPlans with primaryGoal: 'Wildlife Management - General' and county: 'Montgomery' for BOE Section 16 wildlife-focused plans.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect MS 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

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 MS 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

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 MS 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

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:

"MS 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"
}