ArcGIS Pro Automation

Operate saved ArcGIS Pro projects and local GIS datasets through the guarded arcgis-mcp-bridge tool surface. Treat the bridge as an execution backend, not as permission to mutate data or claim a result that was never observed.

Establish the boundary

• Require Windows, a licensed ArcGIS Pro installation, and a bridge worker interpreter that can import ArcPy for real geoprocessing.
• Use the bridge for local, headless, repeatable ArcPy work. It does not drive the visible ArcGIS Pro UI and does not administer ArcGIS Online or Enterprise.
• If the bridge tools are not callable, provide setup or a dry execution plan. Never simulate tool output or imply that an .aprx or .gdb changed.
• Use the schemas exposed by the connected MCP server. Tool names may be host- namespaced; match the semantic catalog name and never invent parameters.
• Keep every read and write inside the configured allowed roots. Use absolute paths and a dedicated scratch geodatabase for intermediate outputs.