Menu
Use Superset MCP tools for dataset inspection, semantic-layer querying, and virtual dataset creation. Use only for MCP tool workflows; do not use for direct API work.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Prepare direct Preset API access: auth, JWT exchange, base URLs, pagination, Rison parameters, response handling, and shared API setup. Use only for direct API workflows; Do not use for MCP-only work.
Inspect Preset workspace dashboards, charts, dashboard composition, screenshots, thumbnails, chart data, and chart/dashboard operation routing through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.
Run or route SQL Lab execution, result retrieval, exports, query stop, saved-query mutation, and permalink workflows through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.
Drive Preset's `sup` CLI (PyPI package `superset-sup`) for shell, scripting, CI/CD, and agent-driven Preset workflows. Use only for CLI workflows; Do not use for MCP-only work or for direct HTTP/SDK code paths.
Inspect and route direct Superset import/export workflows for dashboards, charts, datasets, databases, saved queries, themes, and asset bundles. Use only for direct API workflows; Do not use for MCP-only work.
Inspect Preset SQL Lab bootstrap, query history, saved queries, result/export routing, query control, and SQL execution routing through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.
| name | preset-mcp-datasets |
| description | Use Superset MCP tools for dataset inspection, semantic-layer querying, and virtual dataset creation. Use only for MCP tool workflows; do not use for direct API work. |
Use for dataset-centered MCP workflows.
list_datasets and get_dataset_info for dataset discovery.get_dataset_info; query_dataset accepts saved metrics only, not ad-hoc expressions. When no saved metric fits, compute the aggregate with execute_sql (route to preset-mcp-sqllab) instead of guessing metric names or stopping to ask.query_dataset for semantic-layer data results.create_virtual_dataset only when the user wants to save SQL as a chartable dataset.list_datasets, get_dataset_info.preset-mcp-data / query_dataset.create_virtual_dataset.preset-mcp-visualization.list_databases and get_database_info through discovery.page_size); paginate or refine the filter only when the target is not in the returned page.get_dataset_info call before data or chart workflows.