WV Geological & Economic Survey logo

WV Geological & Economic Survey

Live

WVGES subsurface geology for Marcellus + Utica plays. ~478 formation-top control wells, ~5.5K Marcellus completed wells with full production history, ~1.2K WVOG fields by play, 10 geologic age polygons.

What is WV Geological & Economic Survey?

West Virginia Geological & Economic Survey (WVGES) — subsurface geology for Marcellus + Utica plays. Probed 2026-05-02. Native server at `atlas2.wvgs.wvnet.edu/server/rest/services` — 14 folders (Boundaries/CAP/CBMP/Geology/Geothermal/Hosted/LakeTight/OilGas_ATG/OilGas_MRCL/OilGas_WVOG/Utica/Boundaries/etc.). 4 layers consumed: OilGas_MRCL/MarcellusPlusGeology/1 'Control Wells' (~478 with formation tops HURN_MD/JAVA_MD/ANGL_MD/RNSR_MD/MDLX_MD/WRVR_MD/GBRK_MD/TLLY_MD/MNNG_MD/OKCA_MD/OKCB_MD/CHVL_MD/USPG_MD/TRSZ_MD/ONDG_MD plus matching _SS subsea + _THK thickness columns), OilGas_MRCL/Marcellus/0 'Completed Marcellus Wells' (~5,517 with rich production-history schema — gas_2005..2025, oil_2005..2025, ngl_2013..2025), OilGas_WVOG/WVOG_Fields/0 'Fields by Play' (~1,211 polygons — Field_Type Gas=1019/Oil=142/Storage=36/CBM=14, Play codes Mgn/Mbi/Dvs/MDe/Pps/Dbs/Des/UDs/etc.), Geology/Generalized_Geology_Ages/2 (10 age polygons Cambrian→Permian). **Critical upstream quirk**: MarcellusPlusGeology/1 does **NOT** support pagination (advancedQueryCapabilities.supportsPagination=false; queries with resultRecordCount return error 400 'Pagination is not supported'). Handler queries via returnIdsOnly=true first, then fetches features by objectIds in chunks of 100. Other 3 layers paginate normally. WVOG_Fields columns have truncated names: Formation_ (with trailing underscore), Geologic_A, Discovery_, Number_of_, Pressure_a, Hydrostati, Permeabili, Oil_Satura, Gas_Satura, Water_Satu, Geothermal, Salinity, Depth_of_R. WVOG_Fields has unmasked sentinel values -99999.99/-99999.9999/-99999 indicating missing data — handler treats as null. Marcellus wells layer 0 has 95+ columns (21 gas_YYYY, 21 oil_YYYY, 13 ngl_YYYY); handler aggregates production into recentGas/recentOil arrays + cumulative totals. Spatial reference varies (102100 Web Mercator for OilGas_MRCL; 26917 NAD83 UTM 17N for some Geology services); handler always requests outSR=4326. Spec drift: spec mentioned 'searchOilGasGeology' for pay-zone overlays — closest authoritative is WVOG_Fields with Play+Lithology+Thickness+Porosity+Pressure attribution. Utica/MD_Energy_Investigations_2 service has 160+ layers but most are project-specific WMA studies (R.D. Bailey, Lewis Wetzel, Tug Fork) — too narrow for generic exposure.

Available Tools

  • searchFormationTops
    Marcellus + Utica formation tops (~478 control wells). Each record returns formationTops[] with code/name/MD/SS/THK for HURN/JAVA/ANGL/RNSR/MDLX/WRVR/GBRK/TLLY/MNNG/OKCA/B/CHVL/USPG/TRSZ/ONDG/HMLN/MRCL.
  • searchOilGasGeology
    WVOG fields by play (~1.2K). Filter fieldType (Gas/Oil/Storage/CBM), play (Mgn/Mbi/Dvs/MDe/etc.), geologicAge, lithology.
  • searchGeologicMaps
    Generalized geology age polygons (10). Filter age (Devonian/Pennsylvanian/etc.) or mapUnit code.
  • searchMarcellusWells
    Completed Marcellus wells (~5.5K) with production history. Returns recentGas/recentOil + cumulativeGas/Oil. Filter county/operator/targetFormation/yearFrom/minCumulativeGas.
  • getServiceInfo
    Schema + record counts for any of 4 services. Returns _nativeServer summary listing all 14 WVGES folders.

Requirements

  • ENABLE_ENVIRONMENTAL_APIS
    Set ENABLE_ENVIRONMENTAL_APIS=true to allow connector toggles.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Set ENABLE_ENVIRONMENTAL_APIS=true for your deployment.

Open /mcp and turn on WV Geological & Economic Survey with the environmental switch.

Call the wv-ges MCP tool — start with method=searchFormationTops or method=searchMarcellusWells.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect WV Geological & Economic Survey 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 WV Geological & Economic Survey 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 WV Geological & Economic Survey 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:

"WV Geological & Economic Survey-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"
}