Skip to main content
Glama
HarshShinde0

GeoCroissant MCP Server

by HarshShinde0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GeoCroissant MCP Server

No user-submitted related servers found.

    Related Servers

    • STAC MCP Server

      BnJam
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to search and access geospatial datasets through STAC (SpatioTemporal Asset Catalog) APIs. Supports querying satellite imagery, weather data, and other geospatial assets with spatial, temporal, and attribute filters.
      11
      13
      MIT

    • Copernicus Earth Observation

      wb1016
      A
      license
      B
      quality
      D
      maintenance
      Provides tools to search, download, and manage satellite imagery from all Copernicus Sentinel missions via the Copernicus Data Space ecosystem. It enables advanced geospatial queries, temporal coverage analysis, and automated data management for Earth observation tasks.
      13
      5
      LGPL 3.0

    • OpenLandMap MCP Server

      tharlestsa
      F
      license
      A
      quality
      D
      maintenance
      Provides access to the OpenLandMap STAC catalog, offering over 100 global environmental datasets including soil, climate, and vegetation data. It enables AI agents to discover, search, and retrieve Cloud-Optimized GeoTIFFs for global geospatial analysis.
      27
      -

    • OpenDataMCP

      shahchiragh
      F
      license
      Not graded
      quality
      B
      maintenance
      Turns the AWS Registry of Open Data and public STAC catalogs into agent-callable tools for dataset search, STAC queries, and NDVI/NDBI/land-cover analysis on Sentinel-2 imagery.
      -

    • geolibre-mcp

      89nisham
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides geospatial data intelligence tools for inspecting, querying, and converting geospatial data using DuckDB Spatial.
      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.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    The main workflow stages are clearly separated: discovery tools distinguish catalogs, datasets, and scenes, while generation tools differ by their input source. There is some overlap among the inspection tools—inspect_geocroissant already reports RecordSets and distribution entries, making list_record_sets and extract_distribution_urls partially redundant—but the descriptions are detailed enough to guide selection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list, search, create, validate, inspect, get, and extract are used predictably. The naming also preserves resource hierarchy clearly, from catalogs to datasets to scenes, which helps agents infer relationships between tools.

    Tool Count5/5

    Twelve tools is an appropriate size for this domain: a few discovery tools, two generation paths, one validator, and several inspection/preview/extraction utilities. The count supports the full workflow without bloating the surface or feeling thin.

    Completeness5/5

    The toolset covers the full lifecycle: EO catalog/dataset/scene discovery, GeoCroissant creation from live STAC data or manual parameters, validation, structured inspection, record-set preview, and distribution URL extraction. There are no obvious dead ends because outputs from generation flow naturally into the validation and inspection tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources