Skip to main content
Glama
geo-pera

geopera-mcp

by geo-pera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to geopera-mcp

No user-submitted related servers found.

    Related Servers

    • @terranode-co/mcp-server by terranode-co

      @terranode-co/mcp-serverofficial

      terranode-co
      A
      license
      A
      quality
      D
      maintenance
      MCP server for spatial queries via the Terranode Geospatial API, enabling AI agents to perform point-in-polygon lookups, nearest feature search, distance calculations, and spatial joins.
      6
      38 npm
      MIT

    • MCP Data Server

      boettiger-lab
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that connects AI agents to cloud-native geospatial data via STAC metadata and DuckDB with H3 spatial indexing, enabling zero-configuration SQL queries on terabyte-scale datasets over S3.
      23
      BSD 3-Clause

    • 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"
    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

    C2.5/5.0

    Scored across 188 tools

    Disambiguation3/5

    Tools are namespaced by domain (e.g., alerts.*, analytics.*), which helps distinguish them. However, there is overlap in estimating functions across orders.archive.estimate, orders.estimate, processing.catalog.estimate, leading to potential confusion.

    Naming Consistency5/5

    All tools follow a consistent dot-separated prefix convention (domain.subdomain.action) with verb_noun patterns. No mixing of naming styles or unpredictable patterns.

    Tool Count2/5

    With 188 tools, the server is extremely large, likely overwhelming for agents. This count exceeds typical well-scoped servers and suggests the surface could be broken into smaller, more focused servers.

    Completeness4/5

    The tool set covers a vast array of geospatial operations including alerts, analytics, billing, catalog, orders, processing, and more. Minor gaps exist, such as lack of user management (e.g., invitations), but overall the domain is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources