superset-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPERSET_URL | Yes | The URL of the Apache Superset instance (e.g., http://your-superset-host:8088). | |
| SUPERSET_PASSWORD | Yes | Your password for accessing the Superset instance. | |
| SUPERSET_USERNAME | Yes | Your username for accessing the Superset instance. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dashboardsB | List dashboards. Optionally filter by title with |
| get_dashboardB | Get a single dashboard by ID or slug. |
| get_dashboard_chartsB | Get all charts in a dashboard. |
| get_dashboard_datasetsB | Get all datasets used by a dashboard. |
| create_dashboardC | Create a new dashboard. |
| update_dashboardC | Update an existing dashboard. |
| delete_dashboardC | Delete a dashboard by ID. |
| copy_dashboardC | Create a copy of a dashboard. |
| publish_dashboardC | Set a dashboard as published. |
| list_chartsC | List charts. Optionally filter by name. |
| get_chartC | Get a chart by ID or UUID. |
| create_chartC | Create a new chart. |
| update_chartC | Update a chart's properties. |
| delete_chartC | Delete a chart by ID. |
| get_chart_dataC | Fetch the latest data for a chart. |
| list_datasetsC | List datasets (virtual or physical tables). |
| get_datasetB | Get a dataset by ID or UUID. |
| create_datasetB | Create a dataset from a table or SQL query. |
| get_or_create_datasetB | Get an existing dataset or create it if it doesn't exist. |
| update_datasetC | Update a dataset's properties. |
| refresh_datasetC | Refresh the dataset's columns and metrics from the source. |
| delete_datasetB | Delete a dataset by ID. |
| get_dataset_related_objectsC | Get charts and dashboards using this dataset. |
| list_databasesB | List all database connections configured in Superset. |
| get_databaseB | Get a database connection by ID. |
| list_schemasB | List all schemas in a database. |
| list_tablesB | List tables in a database schema. |
| get_table_metadataC | Get column metadata for a table. |
| get_select_starC | Get a SELECT * query for a table (with schema). |
| execute_sqlB | Execute a SQL query and return results. |
| format_sqlB | Format/pretty-print a SQL query. |
| estimate_query_costC | Estimate the cost of running a SQL query (supported databases only). |
| list_saved_queriesB | List saved SQL queries. |
| save_queryC | Save a SQL query. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 34 tools
Every tool has a clearly distinct purpose targeting specific resources (charts, dashboards, datasets, databases, queries) and actions (create, get, list, update, delete, execute, format, etc.), with no apparent overlap or ambiguity. For example, get_chart, get_chart_data, and list_charts serve different functions without confusion.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_chart, delete_dashboard, list_datasets, and update_dataset, with no deviations in style or convention. This predictability makes the tool set easy to navigate and understand.
With 34 tools, the count is borderline high for typical MCP server scopes, which often range from 3-15 tools. While it covers a comprehensive Superset domain, it may feel heavy and potentially overwhelming for agents, though not extreme like 50+ tools.
The tool surface provides complete CRUD/lifecycle coverage for charts, dashboards, datasets, and queries, along with execution, formatting, and metadata operations. There are no obvious gaps; agents can perform all core workflows from creation to deletion and analysis without dead ends.