Skip to main content
Glama
oceanum-io

Oceanum MCP

Official
by oceanum-io

Related Servers

Alternatives to Oceanum MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search Earth-science dataset collections by keyword, platform, instrument, time range, or bounding box; fetch full collection metadata; and list individual data granules with direct download links.
      12 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Access oceanographic and environmental data from 63+ ERDDAP servers worldwide through natural language queries. Search datasets, retrieve metadata, and download scientific data for climate research, marine biology, and coastal management.
      18
      -
    • A
      license
      B
      quality
      B
      maintenance
      Provides tools to search and execute Code Ocean capsules and pipelines while managing platform data assets. It enables users to interact with Code Ocean's computational resources and scientific workflows directly through natural language interfaces.
      26
      172 PyPI
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with the OSDU® data platform through Model Context Protocol, providing tools for search, storage, schema management, and dataset operations.
      2
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    The data-access tools are clearly tiered by role: search_catalog finds datasources, get_datasource_info/stage_query inspect metadata and size, query_data returns inline previews, and export_query offloads large results. The only real friction is load_datasource ('summarize an entire datasource') versus get_datasource_info ('metadata for one datasource'), which can look interchangeable at a glance, plus the storage_file_exists/storage_file_info pair.

    Naming Consistency4/5

    Every name is snake_case with a clear domain prefix (datamesh_/storage_) and most follow verb_noun (query_data, export_query, stage_query, list_files, read_file, delete_file). The deviations are minor: load_datasource rather than get_datasource, and the noun-first storage_file_exists/storage_file_info.

    Tool Count5/5

    Thirteen tools split cleanly into two domains (7 datamesh, 6 storage), each earning its place in the query/export workflow. Nothing feels redundant or padded at this size.

    Completeness4/5

    The data pipeline is covered end-to-end (discover → inspect → stage → query → export → update metadata) and storage has full create/read/list/delete/stat coverage. Gaps remain: no datasource creation or deletion, no storage copy/move, and metadata updates are the only write path for the catalog.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive