Skip to main content
Glama
agent-engineering-studio

mcp-geo-server

by agent-engineering-studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-geo-server

No user-submitted related servers found.

    Related Servers

    • GeoServer MCP Server

      ronitjadhav
      A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server that exposes GeoServer REST API functionality for natural language interaction through AI assistants like Claude, VS Code Copilot, and other MCP-compatible clients.
      BSD 2-Clause "Simplified"

    • GeoServer MCP Server

      mahdin75
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that connects Large Language Models to the GeoServer REST API, enabling AI assistants to query and manipulate geospatial data through natural language.
      9
      89
      MIT

    • Geo-INQUIRE MCP Server

      lukwe
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with Geo-INQUIRE OGC API Processes for geospatial operations, including planning, execution, and job management through natural language.
      -

    • arcgis-mcp

      riyahkana-lang
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying and metadata retrieval from ArcGIS REST services, allowing users to interact with geospatial data layers through natural language.
      -

    • Rasdaman MCP Server

      fastmcp-me
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language interaction with rasdaman databases, allowing users to list coverages, describe datacubes, and execute WCPS queries.
      5
      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 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion between tools. The single tool serves all purposes.

    Naming Consistency5/5

    With a single tool, naming is trivially consistent. The name 'geoserver-agent' clearly indicates its role.

    Tool Count2/5

    One tool for a broad domain (GeoServer administration, queries, OGC operations) is too coarse. It would be better to split into multiple focused tools (e.g., workspaces, datastores, layers). The single agent obscures individual capabilities.

    Completeness3/5

    The tool claims to handle many GeoServer aspects (workspaces, datastores, feature types, layers, styles, OGC operations), so coverage is broad. However, because it's a single monolithic agent, it's unclear whether all operations are reliably exposed or if there are gaps. A proper tool set would make completeness more assessable.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources