Superset MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPERSET_URL | Yes | Superset base URL (without /api/v1) | |
| SUPERSET_PASSWORD | Yes | Superset account password | |
| SUPERSET_PROVIDER | No | Authentication provider (db or ldap) | db |
| SUPERSET_USERNAME | Yes | Superset account username | |
| SUPERSET_VERIFY_SSL | No | Whether to verify SSL certificates | true |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| superset_statusA | Validate configuration, JWT authentication, current-user access, and optional OpenAPI availability. |
| list_dashboardsA | List dashboards with optional title search and bounded pagination. |
| get_dashboardA | Get dashboard metadata by numeric ID or slug. |
| get_dashboard_chartsC | Get chart definitions and form data for a dashboard. |
| get_dashboard_datasetsC | Get datasets referenced by a dashboard. |
| get_datasetB | Get dataset metadata by numeric ID. |
| list_datasetsA | List datasets with optional name search and bounded pagination. |
| update_dataset_sqlA | Preview or replace SQL for an existing virtual dataset; confirm=true is required. |
| refresh_datasetA | Preview or refresh dataset columns from its SQL; confirm=true is required. |
| get_chartA | Get chart metadata by ID or UUID. |
| get_chart_dataA | Run the stored chart query and return its data; force bypasses the Superset cache. |
| create_virtual_datasetA | Preview or create a SQL-backed virtual dataset; confirm=true is required to write. |
| create_chartA | Preview or create a chart on a Superset dataset; confirm=true is required to write. |
| add_chart_to_dashboardA | Preview or add a chart to one or more dashboards; confirm=true is required to write. |
| update_chartA | Preview or update chart parameters/query context/dashboard links; confirm=true is required. |
| create_dashboardB | Preview or create a dashboard; confirm=true is required to write. |
| update_dashboardB | Preview or update dashboard layout/metadata/publication; confirm=true is required. |
| list_databasesB | List accessible Superset databases and their IDs. |
| execute_sqlB | Execute SQL unchanged through SQL Lab; Superset/database permissions are the safety boundary. |
| get_queryA | Get Superset query history/status details by query ID. |
| get_sql_resultA | Retrieve an asynchronous SQL Lab result using the resultsKey returned by execute_sql. |
| list_saved_queriesB | List saved SQL queries with optional label search. |
| get_saved_queryA | Get one saved query by ID. |
| create_saved_queryA | Preview or create a saved query. No write occurs unless confirm is true. |
| update_saved_queryA | Preview or update a saved query, preserving unspecified fields; confirm=true is required to write. |
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 25 tools
Most tools have clear, distinct purposes targeting specific resources and actions. The only potential confusion is between get_sql_result (async result retrieval) and get_query (query history/status), and between get_chart_data and get_chart, but descriptions are sufficiently clear.
The vast majority follow a consistent verb_noun snake_case pattern (list_, get_, create_, update_, execute_). The single outlier is superset_status, which is not verb-first but still readable and not disruptive.
At 25 tools, this is at the heavy end of the borderline range. Each tool has a purpose, but the granularity is excessive in places (e.g., four dashboard-related getters), making the surface feel larger than necessary.
The set covers most core workflows for dashboards, charts, datasets, saved queries, and SQL execution, but there are notable gaps: no list_charts, no delete operations for any resource, and no get_database by ID. These missing operations will require workarounds.