`copernicus_dataspace_collection`

Pack: copernicus-dataspace · Endpoint: https://gateway.pipeworx.io/copernicus-dataspace/mcp

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

Full detail for one Copernicus Data Space collection: title, description, licence, providers, spatial and temporal extent, and the asset keys its products carry. AUTHORITATIVE for what a Sentinel product level actually contains and how far the EU archive goes back. Get valid ids from copernicus_dataspace_collections — the Copernicus id for a mission differs from the id other STAC catalogues use for the same data.

Parameters

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

Example call

Arguments

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

curl

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

TypeScript (@pipeworx/sdk)

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

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

Connect

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

{
  "mcpServers": {
    "copernicus-dataspace": {
      "url": "https://gateway.pipeworx.io/copernicus-dataspace/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

copernicus_dataspace_collection