Skip to main content
Glama
Sangwxx

ArcGIS Pro Bridge MCP Server

by Sangwxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ArcGIS Pro Bridge MCP Server

No user-submitted related servers found.

    Related Servers

    • arcgis-pro-mcp-free

      IngKevinDavid
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable assistants to control an open ArcGIS Pro project locally over TCP 127.0.0.1, with 68 commands and 167 tools for layers, editing, symbology, layouts, geoprocessing, and arcpy execution.
      1
      MIT

    • ArcGIS Pro MCP

      652036
      A
      license
      C
      quality
      B
      maintenance
      It enables MCP clients to execute ArcPy-based GIS workflows within configured permission and path boundaries, manage projects, maps, layers, layouts, data, spatial analysis, networks, and publishing. It can also attach to a live ArcGIS Pro session when explicitly requested, while failing closed for unauthorized or unintended operations.
      458
      MIT

    • CLI-Anything · ArcGIS Pro

      Jasper0122
      A
      license
      A
      quality
      C
      maintenance
      Drive Esri's ArcGIS Pro from an AI agent — the ArcGIS Pro counterpart to QGIS MCP. A headless ArcPy CLI plus an in-process .NET 8 add-in that exposes the live Pro session as MCP tools (ping, zoom_to, query, run_gp, export_layout) so an agent drives the running project while you watch.
      6
      62
      PolyForm Noncommercial 1.0.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 13 tools

    Disambiguation3/5

    Several tools have overlapping diagnostic purposes (health_check, doctor, debug_runtime_context, ping, detect_arcgis_environment). While descriptions differentiate them, an agent may still struggle to pick the right one. Other tools like inspect_gdb, list_gis_layers, and build_gis_resource_uri are more distinct.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (buffer_features, clip_features, build_gis_resource_uri, etc.), but 'doctor', 'health_check', and 'ping' break the pattern as nouns or noun-verb combos. The mix is noticeable but not chaotic.

    Tool Count4/5

    13 tools is within the ideal 3-15 range for a specialized bridge server. The count feels reasonable, covering diagnostics, inspection, basic geoprocessing, and code execution without being overwhelming.

    Completeness3/5

    The tool surface covers core areas: environment detection, project inspection, simple spatial operations, and arbitrary arcpy execution. However, it lacks common GIS operations like intersect or dissolve, and the 'generate_sync_plan' is a placeholder. The arcpy execution tool mitigates some gaps but not all workflows are directly supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources