Skip to main content
Glama
lutfiArahaman

ArcGIS Pro MCP Bridge

by lutfiArahaman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ArcGIS Pro MCP Bridge

No user-submitted related servers found.

    Related Servers

    • arcpro-mcp

      qiobn
      A
      license
      A
      quality
      C
      maintenance
      Enables natural language control of live ArcGIS Pro sessions through the Model Context Protocol, allowing inspection of projects, layers, and attributes, and execution of geoprocessing tasks.
      25
      2
      MIT

    • ArcGIS Pro MCP

      Knight60
      A
      license
      B
      quality
      A
      maintenance
      Lets AI assistants control a live ArcGIS Pro session through arcpy, including layer management, attribute queries, geoprocessing, symbology, and export.
      112
      12
      AGPL 3.0

    • arcgis-pro-mcp

      AngelZ-YT
      F
      license
      Not graded
      quality
      C
      maintenance
      Drives a live ArcGIS Pro session from Claude via arcpy, enabling layer listing, dataset description, geoprocessing, and project inspection directly against an open project.
      -
    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

    A3.7/5.0

    Scored across 31 tools

    Disambiguation3/5

    Most tools target a distinct resource/action, but several status/inspection tools overlap (ping vs get_project_info vs get_active_map_name) and run_geoprocessing vs execute_python both offer broad arcpy execution. The descriptions help disambiguate, but an agent could easily pick the wrong one in those cases.

    Naming Consistency4/5

    Tool names generally follow a clear verb_noun pattern, with consistent use of list_ for enumerations, get_ for single values/status, and create_/set_/update_ for mutations. The main outliers are the bare ping and prepositional forms like zoom_to_layer and select_by_attribute, so the set remains predictable overall.

    Tool Count2/5

    31 tools is on the heavy side for an MCP bridge, exceeding the 25+ threshold for 'too many' in the calibration. The broad ArcGIS Pro scope explains some of the count, but run_geoprocessing and execute_python are generic escape hatches that make several specialized wrappers feel redundant.

    Completeness4/5

    The tool set covers core ArcGIS Pro workflows well: project status, layer management, attribute inspection/selection/update, workspace exploration, layout creation/export, and publishing. Minor gaps like map/layout deletion, feature editing, and symbology changes lack dedicated tools, but run_geoprocessing/execute_python provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources