A
licenseA
qualityD
maintenanceEnables 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 Bridge
Related Servers
Alternatives to ArcGIS Pro MCP Bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to control ArcGIS Pro through natural language, executing geoprocessing tools, editing data, and automating GIS workflows via a persistent ArcPy session.12Apache 2.0
- AlicenseBqualityAmaintenanceLets AI assistants control a live ArcGIS Pro session through arcpy, including layer management, attribute queries, geoprocessing, symbology, and export.11224AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to externally drive a running ArcGIS Pro instance to run GP tools and Python, with real-time human-readable feedback in the Pro panel.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and visualize ArcGIS Online/Enterprise geospatial data through natural language, performing spatial analysis and map generation.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to directly operate ArcGIS Pro through natural language, giving access to 2,500+ spatial analysis tools across 46 toolboxes via the Model Context Protocol.MIT
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
ActivitySlowing
ResponsivenessNo issues