Community project: driving ArcGIS Pro from an AI agent (ArcPy CLI + live MCP bridge) — is agent/MCP integration on the team's radar?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Review the issue and the linked CLI-Anything-Arcgis-Pro repository to understand the proposed ArcPy CLI and ArcGIS Pro SDK/.NET MCP bridge. The issue does not identify a file, test, or requested change; it seeks the team's direction on agent/MCP integration, alignment, and whether discussion should move to Esri Community.
Written by the indexing model from the issue text.
Description
Hi ArcGIS API for Python / GeoAI team 👋
I built an open-source bridge that lets an LLM agent (e.g. Claude) operate ArcGIS Pro end to end, and wanted to share it with the team that's closest to Esri's GeoAI work — and ask whether agent/MCP integration is something you're exploring.
Repo: https://github.com/Jasper0122/CLI-Anything-Arcgis-Pro
It has two modes:
- Headless CLI over ArcPy —
info / project / layout (incl. Map Series) / data / gp (any geoprocessing tool) / batch, JSON in / JSON out, with self-dispatch into Pro'sarcgispro-py3. - Live bridge + MCP — an in-process ArcGIS Pro SDK (.NET 8) add-in exposes the open Pro session over a local socket, wrapped as MCP tools (
ping / zoom_to / query / run_gp / export_layout), so an agent drives the running project and you watch it happen in the UI.
I know this repo is the Web GIS arcgis package rather than ArcPy / the Pro SDK — I'm posting here because the audience and the GeoAI direction overlap, and I'd value the team's perspective.
A few open questions:
- Is agent / MCP / tool-calling integration with ArcGIS something the team is looking at?
- If so, is there a preferred direction the community should build toward (so efforts align rather than fragment)?
- Any interest in feedback or a community contribution on this front?
(Not affiliated with Esri; ArcGIS, ArcGIS Pro and ArcPy are trademarks of Esri. This is an independent community integration.)
Happy to demo or move this to Esri Community if that's a better venue. Thanks!
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 1.1k
- Avg merge
- 2h 40m
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Esri/arcgis-python-api
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Esri/arcgis-python-api#2513 · 1 comment ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Esri/arcgis-python-api#2453 · 3 comments ·
-
documentation enhancement
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Esri/arcgis-python-api#2097 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Esri/arcgis-python-api#2537 · 3 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Esri/arcgis-python-api#2531 · 1 comment ·
All issues in Esri/arcgis-python-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100