`copernicus_dataspace_search`

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_search for the schema, then POST the same URL with its arguments for the data.

Search the EU Copernicus archive for Sentinel and Contributing Mission products over an area and date range, returning product ids, sensing datetimes, footprints and the asset inventory. AUTHORITATIVE for ‘which European satellite products cover this place on these dates’, queried against the operator’s own live catalogue. collections is REQUIRED — the upstream refuses a catalogue-wide search. Metadata is keyless; the s3:// asset paths it returns need a free Copernicus account to download. bbox is WGS84 degrees, [west, south, east, north].

Parameters

Name	Type	Required	Description
`collections`	array	yes	Collection ids to search, e.g. [“sentinel-2-l2a”]. REQUIRED — the Copernicus Data Space rejects a search with none. List them with copernicus_dataspace_collections.
`items`	string	no
`bbox`	array	no	Bounding box in WGS84 degrees as [west, south, east, north], e.g. [7.4, 46.9, 7.5, 47.0] for Bern. Longitude first.
`items`	number	no
`datetime`	string	no	RFC 3339 instant or interval, e.g. “2026-08-01T00:00:00Z/2026-09-01T00:00:00Z”. Omit for any date.
`ids`	array	no	Fetch specific product ids instead of searching by area/date.
`items`	string	no
`limit`	number	no	Products to return, 1-100. Default 10.
`max_assets`	number	no	Asset entries per product, 1-50. Default 8 — a Sentinel-2 L2A product lists well over 100 assets and returning all of them for 100 products is a very large payload.

Example call

Arguments

{
  "collections": [
    "sentinel-2-l2a"
  ],
  "bbox": [
    7.4,
    46.9,
    7.5,
    47
  ],
  "datetime": "2026-08-01T00:00:00Z/2026-09-01T00:00:00Z",
  "limit": 3,
  "max_assets": 4
}

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_search","arguments":{"collections":["sentinel-2-l2a"],"bbox":[7.4,46.9,7.5,47],"datetime":"2026-08-01T00:00:00Z/2026-09-01T00:00:00Z","limit":3,"max_assets":4}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('copernicus_dataspace_search', {
  "collections": [
    "sentinel-2-l2a"
  ],
  "bbox": [
    7.4,
    46.9,
    7.5,
    47
  ],
  "datetime": "2026-08-01T00:00:00Z/2026-09-01T00:00:00Z",
  "limit": 3,
  "max_assets": 4
});

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_search