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
- AlicenseBqualityCmaintenanceMCP server for Preset (managed Apache Superset). Manage dashboards, charts, and datasets from Claude Code and other LLM agents.591MIT
- 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
- AlicenseNot gradedqualityAmaintenanceMCP server that connects to SQL databases (SQLite, PostgreSQL, MSSQL, MySQL) and provides tools to run read-only queries, list schemas/tables, and manage connections via stdio transport.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server for Apache Superset that enables AI models to manage dashboards, create charts with auto-detection, and execute SQL queries programmatically. It utilizes stateless HTTP transport to ensure compatibility with integration tools like Open WebUI.68 npmMIT
- FlicenseBqualityDmaintenanceAn MCP server that provides AI assistants with full access to Apache Superset instances, enabling interaction with dashboards, charts, datasets, databases, and SQL execution capabilities.34-
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.