Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to arcgis-mcp-bridge

Related Servers

  • arcgis-pro-mcp-free

    IngKevinDavid
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables MCP-capable assistants to control an open ArcGIS Pro project locally over TCP 127.0.0.1, with 68 commands and 167 tools for layers, editing, symbology, layouts, geoprocessing, and arcpy execution.
    1
    MIT

  • CLI-Anything · ArcGIS Pro

    Jasper0122
    A
    license
    A
    quality
    C
    maintenance
    Drive Esri's ArcGIS Pro from an AI agent — the ArcGIS Pro counterpart to QGIS MCP. A headless ArcPy CLI plus an in-process .NET 8 add-in that exposes the live Pro session as MCP tools (ping, zoom_to, query, run_gp, export_layout) so an agent drives the running project while you watch.
    6
    64
    PolyForm Noncommercial 1.0.0

  • arcmap-10-8-mcp

    tina6668758-debug
    F
    license
    B
    quality
    C
    maintenance
    Enables safe local MCP-based control of ArcMap Desktop 10.8, allowing read-only inspection of map documents, layers, datasets, and execution of allowlisted geoprocessing tools through ArcPy.
    15
    2
    -

  • mcp-server

    Ezzeay
    A
    license
    B
    quality
    D
    maintenance
    Production-ready TypeScript MCP server exposing utility, GitHub, and Microsoft Teams tools over stdio.
    14
    1
    MIT

  • ArcGIS Pro MCP

    652036
    A
    license
    C
    quality
    B
    maintenance
    It enables MCP clients to execute ArcPy-based GIS workflows within configured permission and path boundaries, manage projects, maps, layers, layouts, data, spatial analysis, networks, and publishing. It can also attach to a live ArcGIS Pro session when explicitly requested, while failing closed for unauthorized or unintended operations.
    458
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 103 tools

Disambiguation3/5

Most tools have distinct names and descriptions, but at 103 tools there are several close pairs that could be confused, such as set_map_extent_from_layer vs zoom_to_layer, near_analysis vs generate_near_table, and zonal_statistics vs zonal_statistics_as_table. Descriptions generally clarify intent, but the sheer number of overlapping analysis/data-management operations makes misselection a real risk.

Naming Consistency4/5

The overwhelming majority of tool names are snake_case and follow a descriptive verb_noun or noun_to_format pattern, which is easy to scan and predict. However, a meaningful subset uses bare noun phrases like hotspot_analysis, service_area, od_cost_matrix, hillshade, and spatial_autocorrelation, so the verb_noun convention is not perfectly uniform.

Tool Count1/5

With 103 tools, the surface is far beyond the 25+ threshold and clearly in the extreme range. Even though ArcGIS is a broad platform, this many tools creates excessive selection overhead and makes the server difficult for an agent to navigate coherently.

Completeness3/5

The tool set covers an impressive breadth of vector, raster, network, QA/QC, and map/layout workflows. Notable gaps remain, however: there is no direct way to query and return feature attribute rows, and general row-level insert/update/delete operations are missing beyond append, calculate_field, and delete_identical. These gaps are workable in many workflows but represent real missing lifecycle coverage.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources