Skip to main content
Glama
rasdaman

Rasdaman MCP Server

Official
by rasdaman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Rasdaman MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Ocean MCP

      ishimwe5555
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to work with Copernicus Marine ocean data through semantic tools for dataset discovery, metadata retrieval, recommendation, validation, point time-series extraction, area statistics, subsetting, and computation without exposing raw API plumbing.
      -

    • GIS MCP Server

      briannag1692
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to perform geospatial analysis, spatial data processing, vector and raster operations, coordinate transformations, spatial statistics, mapping, and access to climate, satellite, and other geospatial data through MCP-compatible clients.
      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.
      -

    • mcp-geo-server

      agent-engineering-studio
      A
      license
      B
      quality
      C
      maintenance
      Enables natural language interaction with a GeoServer instance for managing workspaces, datastores, feature types, layers, styles, and OGC services (WMS/WFS) via an LLM-powered agent.
      1
      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.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct action: listing coverages, describing a coverage, learning WCPS basics, executing a query, listing doc chapters, and fetching a chapter. The documentation tools are explicitly tiered (crash course -> chapter index -> chapter body), so there is little risk of misselection.

    Naming Consistency3/5

    The names are in readable snake_case, but they mix bare verb_noun names (list_coverages, describe_coverage, execute_wcps_query) with wcps_-prefixed resource-style names (wcps_query_crash_course, wcps_doc_chapters, wcps_get_chapter). The prefix and verb placement are inconsistent even though the overall style is still navigable.

    Tool Count5/5

    Six tools is an appropriate size for a rasdaman querying server: coverage discovery, metadata inspection, query execution, and three levels of documentation. No tool feels redundant or missing at a high level.

    Completeness4/5

    The discover -> describe -> learn -> execute -> debug workflow is well covered. Minor gaps include a lack of write/ingest/update/delete operations for coverages and no explicit way to retrieve the contents of large result files, but these are likely outside the server's query-focused scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources