A
licenseB
qualityD
maintenanceA comprehensive MCP server for Dataiku DSS integration, providing Claude Code with direct access to manage recipes, datasets, and scenarios.
44
4 npm
1
Apache 2.0
Dataiku MCP Server
by clssck
Related Servers
Alternatives to Dataiku MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA FastMCP server packaged for easy installation into Dataiku code environments, enabling the addition and execution of MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables operating Dataiku DSS projects, datasets, and Agent tools from any MCP client over Streamable HTTP, with read-only by default and secure bearer-token authentication.Apache 2.0
- AlicenseBqualityBmaintenanceMCP server for Microsoft Fabric REST APIs that enables data engineers and analysts to manage Fabric components using AI assistants.21945 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server for managing Microsoft Fabric notebooks and Dataflow Gen2 via the Fabric REST API. Supports reading, creating, updating, running, and deleting items within workspaces.MIT
- AlicenseNot gradedqualityCmaintenanceProduction-ready MCP server enabling AI assistants to interact with SAP Datasphere for real tenant data discovery, metadata exploration, analytics operations, ETL data extraction, database user management, data lineage analysis, and column-level data profiling.MIT
TDQS
A3.6/5.0
Scored across 9 tools
Disambiguation5/5
Each tool maps to a distinct Dataiku resource type (project, dataset, recipe, job, scenario, variable, managed_folder, connection, code_env), with no overlapping responsibilities. The descriptions clearly differentiate the scope of each tool.
Naming Consistency5/5
All tool names are single lowercase nouns or snake_case compound nouns (e.g., managed_folder, code_env), following a predictable resource-based pattern. No mixing of styles or vague verbs.
Tool Count5/5
With 9 tools, the server is well-scoped for Dataiku's domain. Each entity earns its place and the count is comfortably within the ideal 3-15 range.
Completeness4/5
The core workflows (list/inspect datasets, recipes, jobs, scenarios; run builds and scenarios) are well covered. Some gaps exist, such as project creation/deletion and code_env management, but these are secondary for common agent tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues