The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Copernicus Dataspace listing page.
European Sentinel and Copernicus Contributing Mission archive from the EU's Copernicus Data Space Ecosystem — search Sentinel-1/2/3/5P, Copernicus DEM, land-cover and burnt-area products by area and date and get item ids, footprints, dates and product asset paths.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
copernicus_dataspace_collections(contains?, prefix?, limit?) — the product
collections, with licence, extent and date range. Call this first: search
refuses a query that names no collection.copernicus_dataspace_collection(collection_id) — one collection in full.copernicus_dataspace_search(collections, bbox?, datetime?, ids?, limit?, max_assets?)
— which products cover an area on given dates.Catalogue search is keyless. Downloading a product is not: asset hrefs are
s3://eodata/... object-store paths, and fetching the bytes needs a free
Copernicus account plus S3 or OData credentials (register at
https://dataspace.copernicus.eu). The ids, dates, footprints and asset
inventory returned here are complete and need no account.
The sentinel-hub pack is the commercial Sentinel Hub processing API (OAuth
client credentials; statistical/NDVI endpoints returning computed values). This
pack is the free EU catalogue underneath it — it says which scenes exist;
Sentinel Hub renders and analyses them. Neither substitutes for the other.
links to https://stac.dataspace.copernicus.eu/v1; both answer.Shared client: shared/src/stac.ts, also used by planetary-computer,
earth-search and meteoswiss.
POST /search with no collections answers HTTP 400
CollectionInQuerryIsMissingError (the upstream's own spelling).GET /collections pages ten at a time. A single un-paged read looks like a
ten-dataset catalogue — a confident wrong answer rather than an error. The
shared client follows rel="next".s3://, not HTTPS. An agent that treats one as a download URL
gets nothing and reads it as a broken link.Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/copernicus-dataspace/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/copernicus_dataspace_collections. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
Or run it directly to confirm it starts:
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT