Superset MCP Server
Related Servers
Alternatives to Superset MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server for Apache Superset. Gives AI assistants full control over your Superset instance — dashboards, charts, datasets, SQL Lab, users, roles, RLS, and more — through 137 tools.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to manage Apache Superset BI metadata (charts, dashboards, datasets, and queries) via MCP, with a read-only default and optional governed write access.-
- AlicenseBqualityCmaintenanceConnects LLM clients to Apache Superset for querying charts, dashboards, datasets, databases, and executing SQL.121GPL 3.0
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Metabase for database operations, SQL queries, dashboard management, and analytics automation.28MIT
- AlicenseBqualityFmaintenanceMCP server enabling AI agents to programmatically connect to and control Apache Superset instances, allowing users to manage dashboards, charts, databases, datasets, and run SQL queries through natural language interactions.60191MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Redash queries, dashboards, visualizations, and data sources via natural language.156 npmMIT
TDQS
Scored across 17 tools
Most tools target distinct resources and actions. The only potential confusion is between superset_list_datasets and superset_list_all_datasets, but their descriptions clearly differentiate (filtered/search vs all pages). superset_get_dashboard_charts also overlaps slightly with superset_list_charts, but the dashboard scoping is clear.
All tools follow a consistent `superset_verb_noun` pattern with snake_case. The verb is always placed immediately after the prefix, and nouns are lowercase (e.g., superset_list_databases, superset_create_dashboard). The only minor deviation is superset_list_all_datasets, but it's still readable and predictable.
17 tools is slightly above the typical sweet spot, but each tool addresses a distinct operation on the core entities (databases, datasets, dashboards, charts). There are no trivial or redundant tools, so the count feels justified for full chart/dashboard lifecycle management.
Charts and dashboards have complete CRUD coverage plus extra operations (filters, adding charts). However, databases and datasets only support listing/getting, with no create, update, or delete. Additionally, there is no way to remove a chart from a dashboard without deleting it, which is a notable gap.