The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Copernicus Cds listing page.
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.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
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.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.
copernicus-dataspacecopernicus-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.
limit and q, so the keyword filter and paging in cds_collections are
applied here, not upstream.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.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/copernicus-cds/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/cds_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