ArcGIS Pro

You can expose ArcGIS Pro functionality through an MCP server so you can drive GIS tasks from an MCP client. This setup lets Copilot or other MCP clients query maps, list layers, count features, and control ArcGIS Pro actions via a simple, consistent interface.

How to use

You interact with the MCP server by calling MCP tools from your client. Practical examples include counting features in a specific layer, listing layers in the active map, or zooming to a layer. The ArcGIS Pro Add-In runs inside ArcGIS Pro and exposes operations through a local IPC channel. The MCP server is a separate console application that defines tools and communicates with the Add-In to perform the requested actions.

From your MCP client, call tools such as pro.listLayers to retrieve the layers in the active map or pro.countFeatures layer=Buildings to get the number of features in a layer. The bridge between the MCP server and ArcGIS Pro is handled transparently via the Named Pipe interface established by the Add-In on startup.

How to install

Prerequisites you need installed on your machine before you begin:

• ArcGIS Pro installed on the same machine
• ArcGIS Pro SDK for .NET
• .NET 8 SDK

Step-by-step setup and run flow:

# 1) Ensure .NET 8 SDK and Visual Studio 2022+ are installed on your machine.
# 2) Open the solution in Visual Studio 2022 (17.14 or newer).
# 3) Build the ArcGIS Pro Add-In so it runs inside ArcGIS Pro and hosts the IPC channel (Named Pipes).
# 4) Load ArcGIS Pro and load the Add-In so the Named Pipe server exists.
# 5) In your MCP environment, place the MCP manifest and start the MCP server as described below.
# 6) Use Copilot in Agent mode or another MCP client to call pro.* tools.

Configuration and runtime

The MCP server is configured to run as a local stdio server. It starts by executing the dotnet command that runs the dedicated MCP project. The ArcGIS Pro Add-In hosts a Named Pipe server and provides the bridge for tool execution.

{
  "servers": {
    "arcgis": {
      "type": "stdio",
      "command": "dotnet",
      "args": [
        "run",
        "--project",
        "McpServer/ArcGisMcpServer/ArcGisMcpServer.csproj"
      ]
    }
  }
}

Additional notes

For best results, ensure the ArcGIS Pro Add-In is loaded when you start the MCP server so the IPC channel is available. You can extend the tooling by adding new MCP tools that wrap additional ArcGIS Pro operations as you need.

Troubleshooting and tips

If tools do not respond, verify that ArcGIS Pro is running and the Add-In is loaded so the Named Pipe server is active. Check that the Copilot Agent Mode is configured to read the MCP manifest (.mcp.json) and launch the MCP server accordingly. Ensure the IPC channel names match between the Add-In and the MCP server.

Examples of available actions

Sample actions you can implement or extend include counting features in a layer, listing active map layers, and zooming to a specific layer. The built-in tool Count features in a layer demonstrates how to bridge a client request to a Pro operation and return results to the client.

Available tools

pro.countFeatures

Counts features in a specified layer by asking ArcGIS Pro to examine the layer's feature class and return the count.