Skip to main content
Glama
HackerFund

Glendale GIS MCP Server

by HackerFund
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Glendale GIS MCP Server

No user-submitted related servers found.

    Related Servers

    • arcgis-peoria

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables search and query of City of Peoria, Arizona open geospatial datasets (parcels, zoning, public works) via ArcGIS feature services, allowing AI agents to access GIS data through natural language.
      3 npm
      MIT

    • arcgis-sanjose

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Search and query City of San Jose GIS open geospatial datasets (parcels, zoning, public works) via ArcGIS Feature Services, enabling AI agents to access live geospatial data through natural language.
      7 npm
      MIT

    • mcp-arcgis-tucson

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to search and query City of Tucson GIS open geospatial datasets (zoning, parcels, public safety, transport, city services) through natural language.
      4 npm
      MIT

    • mcp-arcgis-henderson

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and querying City of Henderson open geospatial datasets (parcels, zoning, public works) via natural language or direct tool calls.
      3 npm
      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

    A4.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: listing datasets, reading guides, describing schemas, querying data, geocoding, and specific hazard lookups per type (wildfire, flood, seismic, dam, debris) plus resource search. The aggregate hazards_at_location is explicitly differentiated from single-hazard tools.

    Naming Consistency5/5

    All tool names use lowercase snake_case with a consistent style, mostly verb_noun (list_datasets, read_guide, describe_dataset, query_dataset, geocode_address) or resource nouns (wildfire_zone, flood_zone, seismic_zones). The pattern is uniform and predictable.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range. Each tool covers a distinct aspect of the GIS domain (hazards, resources, querying, geocoding) without redundancy, and the count matches the server's comprehensive scope.

    Completeness5/5

    The tool surface provides complete coverage for the stated purpose: listing available datasets, describing schema, flexible querying (attribute, location, bbox), geocoding, all major hazard types, and community resources. No obvious gaps; read-only GIS queries are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources