ArcGIS Pro MCP
An ArcGIS Pro add-in that lets you say what you want.
It implements the Model Context Protocol inside ArcGIS Pro itself, so an AI assistant — Claude, Codex, Antigravity, or any other MCP client — can work on the project already open in front of you. Your data, your maps, your layouts. Not a copy, not an export.
Install the add-in, click the button for the assistant you use, done. No config files to find, no JSON to hand-edit, no Python to install.
In any language your assistant speaks. Your assistant does the
understanding; this add-in never matches on English keywords. Non-English text
travels intact in both directions, so a query can name a place in Thai and get
Thai back — PROV_NAMT LIKE '%เชียง%' returns เชียงใหม่ and เชียงราย.
"Style the provinces by area, pastel red through green"
"Which province has the highest population? Put the answer in a new field"
"Export the current map view as a PNG and show me"
"ระบายสีจังหวัดตามขนาดพื้นที่ ไล่จากแดงพาสเทลไปเขียว"
"จังหวัดไหนมีประชากรมากที่สุด ใส่คำตอบไว้ในคอลัมน์ใหม่"
"ส่งออกมุมมองแผนที่ปัจจุบันเป็น PNG แล้วเอามาให้ดู"
The aim is the whole of ArcGIS Pro, not a convenient corner of it. A request falls through three layers, and takes the fastest one that can answer it:
Layers 1 and 2 need nothing but the add-in. Layer 3 runs through an optional Python bridge inside ArcGIS Pro's own Python — install it when you want the escape hatch, skip it and the first two still work. A command the add-in does not implement is forwarded there automatically; if it is not running, the error says so and how to start it, rather than failing obscurely.
The practical effect is that there is no such thing as "the tool for that is missing". If it can be done in ArcGIS Pro, it can be asked for in a sentence.

Every frame above was rendered by the add-in itself, running the request in
the caption. Rebuild it with python scripts/make_demo_gif.py.

Install
Get it from the latest release and pick one of the two files.
The add-in on its own
Download
ArcGISProMCP.esriAddinX
and double-click it. ArcGIS Pro's own installer takes it from there. Restart
Pro and the MCP tab appears.
Or the installer, if that does not work
Install-ArcGISProMCP.cmd
is one self-contained file — the add-in is inside it, so there is nothing else
to download.
Double-click it, or run it from a prompt. It is a .cmd, not a .ps1, so
Windows' script execution policy never gets in the way.
Use this one when Pro loads the add-in but the MCP tab never appears: some machines have add-in security turned on, and the add-in alone cannot say so. The installer checks, tells you which of the two states it found, and offers the fix. Run it a second time and it offers to uninstall.
Requires ArcGIS Pro 3.7. Nothing else — no Python, no SDK, no admin rights. It is built against 3.7 and will not load on anything older; a newer Pro should be fine, and the installer says so rather than stopping you.
The same two files are also committed to
dist/. It holds
the most recent build that has been through
release validation, so it matches the latest
release, and can be ahead of it when a validated fix is not yet tagged.
Building from source writes elsewhere; only a validated build reaches dist/.
They are committed rather than left as build output because GitHub Actions has no ArcGIS Pro to build against: a build only exists if someone with Pro installed produces it. Committing it keeps a download beside the source that made it.
Take the release unless you have a reason to want something newer than it.
Uninstalling
Run the installer again and answer yes, or:
Install-ArcGISProMCP.cmd -Uninstall
It removes every copy it finds, including the one ArcGIS Pro's own installer
unpacks into a folder named after the add-in id. The .esriAddinX cannot
uninstall anything — double-clicking it only ever installs. The other way is
ArcGIS Pro itself: Project ▸ Add-In Manager ▸ Delete this Add-In.
Connect an AI client
Open the MCP tab in ArcGIS Pro and click your assistant — the three most used are on the ribbon, the rest are under More clients.
It asks before changing anything, tells you which file it will write, and backs that file up first.
Supported: Claude Code, Codex, Antigravity, VS Code, Cursor, Cline, Gemini CLI, Claude Desktop.
The address every one of them connects to is
http://127.0.0.1:6520/mcp
That is the only number worth remembering. The add-in also listens on 6510 for
a legacy TCP bridge, and optionally on 6511 for the in-Pro Python fallback, but
no AI client uses either. All three are bound to 127.0.0.1 and are not
reachable from another machine — see SECURITY.md.
Most clients connect over HTTP:
claude mcp add --transport http arcgis http://127.0.0.1:6520/mcp
{ "mcpServers": { "arcgis": { "type": "http", "url": "http://127.0.0.1:6520/mcp" } } }
Antigravity wants serverUrl instead of url and no type.
Codex connects directly using Streamable HTTP. In ~/.codex/config.toml,
replace the existing arcgis section (including its old env subtable) with:
[mcp_servers.arcgis]
url = "http://127.0.0.1:6520/mcp"
The Codex ribbon button writes exactly this, backs the file up first, and
replaces an older command/args registration in place — one click, whichever
state you are in. Everything else in the file is left alone. Restart Codex
afterwards. Installing the add-in never rewrites a client config on its own.
See the official Codex MCP documentation.
Claude Desktop is the one client that cannot dial out to a server — it can
only launch one. So the add-in writes the missing piece itself: a small
PowerShell bridge at %LOCALAPPDATA%\ArcGIS Pro MCP\stdio-bridge.ps1 that
forwards each message to the same HTTP endpoint, and registers Claude Desktop
to run it:
{ "mcpServers": { "arcgis": {
"command": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",
"args": ["-NoProfile", "-ExecutionPolicy", "Bypass", "-File",
"C:\\Users\\you\\AppData\\Local\\ArcGIS Pro MCP\\stdio-bridge.ps1"] } } }
Windows PowerShell ships with Windows, so there is still nothing to install — no Python, no Node, no pip. The bridge is rewritten whenever you register a client, so upgrading the add-in upgrades it too.
The bridge lives inside ArcGIS Pro, so Pro has to be open. Close it and the client's connection goes red.
The ribbon
One button starts and stops, the way a play button does: the icon shows what the next click will do, so it doubles as the state readout. Green ▶ means stopped, red ⏹ means running.
Status shows a green broadcast while listening and a contained grey dot when not, captioned with the MCP port. Hover it for the full address to paste into a client; click it for the full report: requests served, which clients are connected, and the last error.
Tools
112 tools. Anything not listed is still reachable through run_geoprocessing_tool or execute_arcpy_code.
Session and project (14)
Layer (19)
Attributes and editing (11)
Selection (6)
Schema and dataset creation (11)
Geoprocessing (7)
Symbology and labels (6)
Map view and bookmarks (7)
Layouts and printing (16)
Raster (5)
Finding and inspecting data (6)
Escape hatch (4)
⚠️ = changes or deletes real data 🖼️ = returns an image the AI can look at
Troubleshooting
No MCP tab after restarting Pro. Add-in security is the usual cause.
Run Install-ArcGISProMCP.cmd; it will say so and offer the two ways round it.
The setting itself is in ArcGIS Pro under Project ▸ Add-In Manager ▸
Options:

The middle setting is the one this add-in is signed for. The bottom one loads anything. What each choice means.
The client shows the server in red. ArcGIS Pro is closed, or the bridge is stopped. Open Pro and check the toggle on the MCP tab shows ⏹ (running).
A command says a layer does not exist. Layers inside a group need their
full name, "Group\Layer", for anything that runs through geoprocessing.
An edit did not appear. ArcGIS Pro holds edits open so they can be undone,
which also keeps the data locked. Call save_edits.
Safety
These tools change the project you have open and the data under it. Tools marked ⚠️ above modify or delete real data.
The bridge binds to 127.0.0.1 only — nothing on the network can reach it —
but anything that can run code on your machine can drive ArcGIS Pro through it
while Pro is open. execute_arcpy_code runs arbitrary Python inside Pro.
Prefer non-destructive steps, use save_project deliberately, and let the
assistant confirm before bulk edits.
How it works
An ArcGIS Pro add-in written in C#, running inside Pro's own process:
AI client ──MCP over HTTP :6520/mcp ─┐
│
AI client ──MCP stdio──► arcgis-pro-mcp ──TCP :6510──┐
│ │
▼ ▼
┌─ C# add-in (inside the ArcGIS Pro process) ─┐
│ → QueuedTask.Run (Main CIM Thread) │
│ anything it does not implement ─┐ │
└───────────────────────────────────┼─────────┘
▼ :6511
Python bridge (execute_arcpy_code)
Being in-process is the whole point. ArcGIS Pro will only let its own Main CIM
Thread touch the open project, and an outside process cannot get onto it. An
earlier all-Python version had to hand work to Pro's Python thread and wait,
which took around 28 seconds per call. The add-in uses QueuedTask.Run
directly: 9 ms.
Three of the 112 tools stay on the Python side, and belong there:
execute_arcpy_code, because a compiled add-in cannot run code composed at
call time, and get_pump_status / stop_pump, which report on the Python
bridge's own dispatcher.
More detail in docs/.
Building it yourself
You do not need to — the release is a single download. If you want to change something, see BUILD.md.
.\scripts\build.ps1
Everything used to produce a release is in this repository: the build, the signing, the icon drawing, and the installer that gets packed into one file.
Author and licence
Built by Pisut Nakmuenwai (@Knight60).
Dual licensed.
AGPL-3.0 — free, and free to keep. Use it for your own work, paid or unpaid, on as many machines as you like. Modify it. Build on it. The one condition is reciprocal: if you pass on a work built from this one, or run it as a service other people use, those people get its source under the same terms.
Commercial — for shipping it inside a product you do not publish the source of, hosting it in a closed service, or redistributing it under your own name.
Doing GIS work with it and delivering the maps and analysis is ordinary use, not distribution. Most people never need the second licence; the details say where the line falls, and asking is free.
Releases up to v1.0 were MIT and stay MIT — that grant cannot be withdrawn. The dual licence applies from v1.1. NOTICE carries the copyright and an AGPL Section 7 permission for linking with the ArcGIS Pro SDK.
Support this project
Built and maintained in the open, with no company behind it.
If it saves you time, sponsoring it helps keep it working. Most of the ongoing effort is not new features but keeping up with ArcGIS Pro: every release can move the framework it targets and shift the parameter order of its two thousand geoprocessing tools, and each one means regenerating that table and testing the whole surface again.
Starring the repository costs nothing and helps other people find it. So does telling me what broke — a clear issue is worth a great deal.
Disclaimer
This software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and non-infringement. In no event shall the author or copyright holder be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from or in connection with the software or its use. The full terms are in LICENSE.
Two properties of this software deserve stating plainly rather than being left to the licence, because they are what it is for rather than defects in it:
- It executes commands against a live ArcGIS Pro session, including operations that permanently alter or delete datasets, project files, and geodatabase contents. The tools marked ⚠️ in the table above are the ones that do so.
- Those commands are issued by an AI assistant, whose output is not
deterministic and is not reviewed before it runs.
execute_arcpy_codeexecutes arbitrary Python inside ArcGIS Pro with the privileges of the signed-in user.
You remain responsible for your data and for the consequences of any operation performed through this software. Back up anything you cannot afford to lose, work on copies where practical, and verify results before relying on them. Use against production data, or against data you cannot restore, is entirely at your own risk.
This project is an independent work. It is not affiliated with, endorsed by, sponsored by, or supported by Esri, and it is not a supported ArcGIS product. ArcGIS and ArcGIS Pro are trademarks of Esri. Your use of ArcGIS Pro remains governed by your own licence agreement with Esri, and nothing here modifies it.