Skip to main content
Glama
Sign In
arcmap-10-8-mcp

arcmap-10-8-mcp

by Stella8758
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to arcmap-10-8-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • arcmap-mcp

      pedralcg
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that allows AI agents to control a live ArcMap session via arcpy, including listing layers, zooming, exporting maps, and viewing the canvas, specifically for legacy ArcMap 10.4-10.8.
      17
      MIT

    • ArcGIS Pro Local MCP

      joshisman0925
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to inspect and modify maps and scenes open in a locally running desktop GIS session through natural language, exposing 38 fixed tools for session and layer queries, fields, selection, visibility and renaming, symbology, transparency, camera and elevation, map switching, raster, layout export, whitelisted geoprocessing, and attribute editing. It routes stdio MCP calls through a Windows named pipe to a C# add-in, with no network ports and no arbitrary code execution.
      MIT

    • arcgis-pro-mcp-free

      IngKevinDavid
      A
      license
      Not graded
      quality
      B
      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.
      2
      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 15 tools

    Disambiguation4/5

    Most tools clearly target distinct resources and actions, such as MXD inspection, dataset metadata, feature queries, and exports. The main ambiguity is between run_geoprocessing and run_advanced_geoprocessing, and the multiple export_mxd_* variants require careful reading to avoid misselection.

    Naming Consistency4/5

    Names generally follow a readable verb_noun snake_case pattern, e.g., list_mxd_layers, describe_dataset, export_mxd_to_png. Minor inconsistencies like health_check and the awkward export_mxd_with_overlay_png keep it from being perfectly uniform.

    Tool Count5/5

    Fifteen tools is at the upper bound but each one earns its place across the ArcMap server's broad scope: health checks, capability discovery, dataset/MXD inspection, feature queries, exports, and geoprocessing. There is no obvious redundancy or bloat.

    Completeness4/5

    The core read, query, export, and geoprocessing workflows are well covered, especially with scratch-confirmed write paths. Minor gaps exist, such as no workspace-content listing or general MXD editing beyond layer visibility, but these do not break the main workflows.

    Resources