Dataiku ACTION
List Datasets
List the datasets of a DSS project. Use this to discover a dataset's
name — the identifier Build Dataset needs to build it — along with its type (e.g. Filesystem) and connection parameters. Use List Projects first if you do not know the project key. Requires the READ_CONF privilege on the project. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Dataiku account once, then configure and run List Datasets from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "dataiku-list-datasets",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
dataiku: { authProvisionId: "apn_xxxxxxx" },
projectKey: "Project Key",
tags: ["Tags"],
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "dataiku-list-datasets",
"configured_props": {
"dataiku": { "authProvisionId": "apn_xxxxxxx" },
"projectKey": "Project Key",
"tags": ["Tags"]
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "dataiku",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "dataiku-list-datasets",
arguments: {
projectKey: "Project Key",
tags: ["Tags"],
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
projectKey Project Key | string | The key of the DSS project, e.g. MYPROJECT. Call List Projects and pass the projectKey field of the project you want. This is an identifier, not the project's display name — a display name will not resolve. In the Dataiku DSS GUI the same value appears in the project's URL as /projects/MYPROJECT/. Required |
tags Tags | string[] | Only return items carrying at least one of these tags, e.g. ["production", "finance"]. Omit to return everything the API key can read. Optional |
foreign Include Foreign Datasets | boolean | Set to true to also list datasets that belong to other projects but are exposed to this one. Defaults to false, which lists only the project's own datasets. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- dataiku-list-datasets
- Version
- 0.0.2
- App
- Dataiku
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗