`earth_search_collection`

Pack: earth-search · Endpoint: https://gateway.pipeworx.io/earth-search/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/earth_search_collection for the schema, then POST the same URL with its arguments for the data.

Full detail for one Earth Search collection: title, description, licence, providers, spatial and temporal extent, and the asset keys (bands, thumbnails, metadata) its items carry. AUTHORITATIVE for which bands a mission delivers here and how far the archive goes back. Get valid ids from earth_search_collections — they differ from the ids other STAC catalogues use for the same mission.

Parameters

Name	Type	Required	Description
`collection_id`	string	yes	Collection id exactly as listed, e.g. “sentinel-2-c1-l2a”, “landsat-c2-l2”, “sentinel-1-grd”.

Example call

Arguments

{
  "collection_id": "sentinel-2-c1-l2a"
}

curl

curl -X POST https://gateway.pipeworx.io/earth-search/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"earth_search_collection","arguments":{"collection_id":"sentinel-2-c1-l2a"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('earth_search_collection', {
  "collection_id": "sentinel-2-c1-l2a"
});

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "earth-search": {
      "url": "https://gateway.pipeworx.io/earth-search/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

earth_search_collection