Dataiku DSS MCP Server
Related Servers
Alternatives to Dataiku DSS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Dataiku DSS REST APIs, enabling flow analysis and day-to-day operations on projects, datasets, recipes, jobs, scenarios, folders, variables, connections, and code environments.923 npmMIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server with file management, HTTP requests, system info, and environment variable tools, plus a management UI and dual transport for Claude Desktop and Claude.ai.261 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server implementation that integrates Claude with Salesforce, enabling natural language interactions with Salesforce data and metadata.852 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides access to over 100 development skills for frontend, backend, integration, design, devops, and process categories via Claude Code and other MCP clients.-
- FlicenseBqualityCmaintenanceMCP server that exposes the Workato Platform API to Claude Desktop and other MCP clients, enabling management of recipes, jobs, connections, folders, custom connectors, and account properties through natural language.19-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects to open data portals like CKAN and Socrata, enabling natural language querying of datasets via Claude.MIT
TDQS
Scored across 43 tools
Most tools have distinct purposes, e.g., get_recipe_info vs get_recipe_code clearly separate; overlapping functions like get_job_details and get_recent_runs are scoped differently. A few pairs like search_project_objects and individual list functions could cause confusion, but descriptions generally clarify.
Majority follow verb_noun pattern (e.g., create_dataset, delete_recipe). Some deviations exist (check_dataset_metrics instead of get_, batch_update_objects as a prefix), but overall consistency is high with no mixed conventions.
43 tools is high, but the Dataiku platform is complex, covering datasets, recipes, scenarios, projects, and system resources. While some tools could be consolidated (e.g., multiple scenario getters), the count is borderline but reasonable for the domain.
Covers CRUD for main objects, plus build, run, test, validate, search, batch operations, and project-level exports. Missing delete_project and user management, but core workflows are well-supported with no dead ends.