gfw_dataset
Pack: global-forest-watch · Endpoint: https://gateway.pipeworx.io/global-forest-watch/mcp
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/gfw_dataset for the schema, then POST the same URL with its arguments for the data.
Full detail for ONE Global Forest Watch dataset — metadata (source, citation, spatial resolution, geographic coverage, update frequency, cautions, licence) plus its version list. Pass a version (or “latest”) to also get that version’s status, assets and field/band list, which is what gfw_query needs to build a valid SQL statement. Keyless.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
dataset | string | yes | Dataset name from gfw_datasets, e.g. “umd_tree_cover_loss”. |
version | string | no | Optional version, e.g. “latest” or “v1.13”. Omit for dataset-level metadata only. |
Example call
Arguments
{
"dataset": "umd_tree_cover_loss",
"version": "latest"
}
curl
curl -X POST https://gateway.pipeworx.io/global-forest-watch/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"gfw_dataset","arguments":{"dataset":"umd_tree_cover_loss","version":"latest"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('gfw_dataset', {
"dataset": "umd_tree_cover_loss",
"version": "latest"
});
More examples
{
"dataset": "umd_tree_cover_loss"
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"global-forest-watch": {
"url": "https://gateway.pipeworx.io/global-forest-watch/mcp"
}
}
}
See Getting Started for client-specific install steps.