Skip to content
← Directory

mcp · Global

CLI-Anything-Arcgis-Pro

Agent-native CLI + live-Pro MCP bridge for ArcGIS Pro — the closed-source counterpart to CLI-Anything's QGIS harness

Claim this listing

Represent CLI-Anything-Arcgis-Pro? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified
layout export to PDF · Map Series / map books export · layer attribute query returned as structured rows · run any ArcToolbox geoprocessing tool, with outputs added to the live map · read open project (maps, layouts, active view) · zoom active map to a layer or selection · graduated and unique-value symbology (headless CLI)
Formats docs-verified
JSON · PDF · ArcGIS Pro project (.aprx) · file geodatabase
Access docs-verified
Requires a licensed ArcGIS Pro install (provides ArcPy). Source-available under PolyForm Noncommercial 1.0.0: free for noncommercial use; commercial use needs a paid licence (see LICENSE-COMMERCIAL.md).

Useful for

Use cases llm-inferred
Export print-quality layouts and Map Series from an ArcGIS Pro project for consultation or planning reports · Run clip, buffer or intersect geoprocessing on site or catchment layers and add outputs to the live map for review · Query layer attributes to build constraint or receptor tables for an assessment · Let an agent assemble and symbolise a thematic map in the open project while the consultant watches
Audience llm-inferred
GIS analysts · flood risk consultants · drainage engineers · planners · ecologists

Limitations

Constraints docs-verified
Requires a licensed ArcGIS Pro install; no ArcPy outside Pro · Live bridge needs the .NET add-in built and installed in Pro, plus MCP registration · Verified only on ArcGIS Pro 3.4 / ArcPy 3.4.3 / .NET 8 · Cartographic authoring (symbology, layout, layer management) is still an open frontier on the roadmap · Noncommercial licence; commercial use needs a paid licence · Tool arguments and parameter names are not documented in the README
Licence
Other
Authentication
No credentials documented in README
GitHub stars
67
Last commit
22/06/2026
Last successful page check
14/10/2026
Page health
healthy
Package
Not recorded
Verification
Not independently verified

Provenance & evidence

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 15/10/2026 · research sweep: github-search