A secure, local-first MCP server exposing ArcGIS Pro's ArcPy engine over stdio JSON-RPC.
A secure, local-first MCP server exposing ArcGIS Pro's ArcPy engine over stdio JSON-RPC. That is what the arcgis mcp bridge mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
arcgis-mcp-bridge requires Windows, a licensed ArcGIS Pro installation, and Python 3.11 or newer for the bridge package.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 1 tool. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverConfiguration is passed through the environment: ARCPY_PYTHON_PATH, ARCGIS_MCP_ALLOWED_ROOTS, ARCGIS_MCP_SCRATCH_GDB, ARCGIS_MCP_MAX_WORKERS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
arcgis-mcp-bridge - An existing writable directory for ARCGIS_MCP_ALLOWED_ROOTS - An existing file geodatabase for ARCGIS_MCP_SCRATCH_GDB, unless <first allowed root>\scratch.gdb already existsThis sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. ArcGIS MCP Bridge's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by muend; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"arcgis-mcp-bridge": {
"command": "C:\\...\\envs\\arcgis-mcp-env\\python.exe",
"args": [
"-m",
"arcgis_mcp.server"
],
"env": {
"ARCPY_PYTHON_PATH": "C:\\...\\envs\\arcgis-mcp-env\\python.exe",
"ARCGIS_MCP_ALLOWED_ROOTS": "C:\\GIS\\Data;C:\\Workspace",
"ARCGIS_MCP_SCRATCH_GDB": "C:\\GIS\\Data\\scratch.gdb",
"ARCGIS_MCP_MAX_WORKERS": "2"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
arcgis-mcp-bridge - An existing writable directory for ARCGIS_MCP_ALLOWED_ROOTS - An existing file geodatabase for ARCGIS_MCP_SCRATCH_GDB, unless <first allowed root>\scratch.gdb already exists| Variable | Description | Required |
|---|---|---|
| ARCPY_PYTHON_PATH | Filesystem location the server is allowed to use. | Optional |
| ARCGIS_MCP_ALLOWED_ROOTS | Configuration value read at startup. | Optional |
| ARCGIS_MCP_SCRATCH_GDB | Configuration value read at startup. | Optional |
| ARCGIS_MCP_MAX_WORKERS | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.