Skip to main content
Glama
MSPFE2019

occ-gis-mcp

by MSPFE2019
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to occ-gis-mcp

No user-submitted related servers found.

    Related Servers

    • sodabar

      UsmarHaider
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that puts open data on tap, enabling LLM clients to search, inspect, and query 30,000+ civic datasets from Socrata portals with built-in guardrails like row caps and actionable error messages.
      4
      MIT

    • mcp-arcgis-houston

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server provides access to City of Houston GIS open geospatial data, enabling search, query, and schema retrieval of datasets like parcels and zoning through ArcGIS feature services.
      259 npm
      MIT

    • mcp-arcgis-tulsa

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and querying City of Tulsa GIS open geospatial datasets (parcels, zoning, public works) via ArcGIS Feature Services through natural language or direct MCP tool calls.
      257 npm
      MIT

    • socrata-mcp

      jcscocca
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives LLM agents typed, cached access to civic open-data portals via Socrata (SODA 2.1 + Discovery API), enabling search, query, profiling, sampling, and CSV export of datasets.
      6
      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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: listing/searching datasets, fetching full dataset details, inspecting layer metadata, and querying layer features. There is no overlap that would confuse an agent selecting among them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_datasets, get_dataset, get_layer_metadata, query_layer), using snake_case throughout and verbs that clearly indicate the action.

    Tool Count5/5

    Four tools is an appropriate scope for a read-only GIS data discovery and query server. Each tool fills a necessary step in the workflow without redundancy or bloat.

    Completeness5/5

    The tool surface fully covers the core workflow: discovering datasets, retrieving full metadata, inspecting layer schemas, and querying features. No obvious dead ends exist; even direct data downloads are covered via distribution URLs returned by the get_dataset tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources