@pipeworx/copernicus-cds

Connect: https://gateway.pipeworx.io/copernicus-cds/mcp · Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

The Copernicus Climate Data Store (C3S/ECMWF) catalogue — the ~140 published climate datasets behind ERA5, CMIP6/CORDEX projections, satellite essential climate variables and seasonal forecasts — plus the ability to submit a retrieval job against any of them.

Tools

• cds_collections(query?, limit?, offset?) — list or keyword-search the catalogue. Returns collection id, title, first line of the abstract, and the temporal/spatial extent. Keyless.
• cds_collection(collection_id, include_form?) — one collection in full: STAC record (abstract, licence, keywords, extent, documentation links) plus the retrieval request form, i.e. the variables, years, levels, area and output formats the job will accept. Keyless.
• cds_submit_request(collection_id, inputs, _apiKey) — submit an asynchronous retrieval job and return the job id. Needs a caller key.

Auth

Catalogue browsing is keyless and verified so (2026-09-17). Submitting a retrieval job needs a free CDS Personal Access Token, passed as _apiKey.

No platform key is provisioned. The intended env var when one lands is PLATFORM_CDS_KEY; sign up at https://cds.climate.copernicus.eu.

platformKeyEnv is deliberately NOT declared on this pack’s manifest entry while the key is unset, because keyBlockedTools() in the gateway blocks every tool in a pack whose declared platform key has no secret — which would sink the two keyless catalogue tools that work today. The keyed tool declares _apiKey as required, so routing sinks only that one. Add "platformKeyEnv": "PLATFORM_CDS_KEY" to the pack-manifest entry in the SAME change that lands the secret.

Not the same as copernicus-dataspace

copernicus-dataspace is the EU Copernicus Data Space Ecosystem — the Sentinel satellite imagery catalogue (catalogue.dataspace.copernicus.eu). This pack is the Climate Data Store (cds.climate.copernicus.eu): modelled and satellite-derived climate variables. Same programme, different host, different question.

Data sources

• https://cds.climate.copernicus.eu/api/catalogue/v1/collections — STAC collection list. It returns the WHOLE catalogue in one response and ignores limit and q, so the keyword filter and paging in cds_collections are applied here, not upstream.
• https://cds.climate.copernicus.eu/api/catalogue/v1/collections/{id} — one STAC collection.
• https://cds.climate.copernicus.eu/api/retrieve/v1/processes/{id} — the OGC API process description. Keyless, and it is where the request form lives; the STAC record alone does not say what a retrieval accepts.
• https://cds.climate.copernicus.eu/api/retrieve/v1/processes/{id}/execute — job submission. Auth is the PRIVATE-TOKEN header, not a Bearer token and not a query parameter. Unauthenticated it answers 401 "authentication required"; with a bad token, 401 "Authentication failed" — the two are distinguishable.

Accepting the dataset licence on the CDS website is a separate gate from holding a token: a valid token still gets a 403 for a dataset whose terms the account has not accepted.

Tools

• cds_collections — List or keyword-search the Copernicus Climate Data Store catalogue — the ~140 published climate datasets (ERA5 reanalysis, CMIP6/CORDEX projections, satellite ECVs, seasonal forecasts, in-situ network
• cds_collection — Full detail for ONE Copernicus Climate Data Store collection by id (e.g. “reanalysis-era5-single-levels”). Returns the STAC record — title, abstract, keywords, licence, temporal and bounding-box exten
• cds_submit_request — Submit a data-retrieval job to the Copernicus Climate Data Store and return the job id and status. Requires your own free CDS Personal Access Token, passed as _apiKey. Use cds_collection first to lear