Let a model work in the ArcGIS Pro session you already have open

1. Download and verify

   From the latest release, download ArcGISProMCP-0.3.1-win-x64-self-signed-preview.zip and SHA256SUMS. In PowerShell, in that folder, check the zip before extracting it:

   $zip = 'ArcGISProMCP-0.3.1-win-x64-self-signed-preview.zip'
   $expected = (Select-String -Path .\SHA256SUMS -SimpleMatch $zip).Line.Split(' ')[0]
   if ((Get-FileHash $zip -Algorithm SHA256).Hash -eq $expected) { 'OK' } else { 'MISMATCH - do not install' }

2. Unblock and extract into C:\ArcGISProMCP\

   Unblock-File $zip
   Expand-Archive $zip -DestinationPath C:\ArcGISProMCP

   Or right-click the zip > Properties > Unblock, then Extract All to C:\ArcGISProMCP, removing the folder name Explorer suggests so the folder is not nested twice. The zip has one root folder, so the gateway is at C:\ArcGISProMCP\ArcGISProMCP-0.3.1-win-x64-development-preview\server\arcgis-pro-mcp.exe.

3. Install the add-in

   Verify and trust the included publisher certificate using the self-signed installation guide. Close ArcGIS Pro and double-click ArcGISProMCP.AddIn.esriAddinX. Keep signed-add-in restrictions enabled; managed computers may need IT approval.

4. Open a disposable project and the pane

   Open a disposable copy of a project. On the Add-In tab, click MCP Studio to open the ArcGIS MCP pane; its status should read Ready. Keep it open: approval cards appear there.

5. Connect your MCP client

   Claude Desktop: Settings > Developer > Edit Config (%APPDATA%\Claude\claude_desktop_config.json). Add the entry inside mcpServers, keeping any servers already there, then quit Claude Desktop from its tray icon and start it again.

   {
     "mcpServers": {
       "arcgis-pro": {
         "command": "C:\\ArcGISProMCP\\ArcGISProMCP-0.3.1-win-x64-development-preview\\server\\arcgis-pro-mcp.exe"
       }
     }
   }

   Claude Code

   claude mcp add --scope user arcgis-pro -- "C:\ArcGISProMCP\ArcGISProMCP-0.3.1-win-x64-development-preview\server\arcgis-pro-mcp.exe"
   claude mcp list

   VS Code: .vscode\mcp.json, or MCP: Open User Configuration

   {
     "servers": {
       "arcgis-pro": {
         "type": "stdio",
         "command": "C:\\ArcGISProMCP\\ArcGISProMCP-0.3.1-win-x64-development-preview\\server\\arcgis-pro-mcp.exe"
       }
     }
   }

   Any other MCP client: run the same path as a stdio server. Do not set ARCGIS_PRO_MCP_AUTONOMOUS_MODE: it skips the approval cards.

6. Verify

   The client lists the arcgis-pro server with 16 tools. Ask "What project is open in ArcGIS Pro?", then ask for a small edit, such as updating one attribute, and approve the card in the ArcGIS MCP pane.

   Trouble? arcgis_unavailable means ArcGIS Pro is not running or the add-in did not load. arcgis_host_ambiguous means several ArcGIS Pro windows are open: close the extra ones, or add "env": { "ARCGIS_PRO_MCP_HOST_PID": "<pid>" } to the client entry with the PID shown in the pane. If the client says the server failed, check the path and the .NET runtime.

Every client, troubleshooting, upgrade and uninstall: install guide. All settings: reference.

• The add-in and gateway are self-signed and require explicit certificate trust. Live acceptance of the signed package is pending.
• Workflows cannot run confirmation-gated steps in default mode; run those operations one at a time through approval.
• Workflows are not transactional or resumable after a crash, and nothing is rolled back automatically.
• ArcPy and gp.run can execute arbitrary user code. Neither is a sandbox.
• Revision checks are an optimistic guard, not a lock. Some direct edits in Pro, such as reordering layers, do not invalidate an approval.
• After each write the host waits up to 3 seconds for ArcGIS Pro's event echoes to settle; heavy layout and 3D steps sometimes reach that cap. Reading the final state still waits for Pro's main thread, so while Pro is busy (for example loading a newly added layer) a write can take much longer to return.
• Feature editing excludes batch edits and multipart construction. Advanced renderers, workspace connections and PDF export are outside the registry.
• Idempotency, workflow history and resources do not survive an ArcGIS Pro restart.

The full list: known limits and security and operational limits.