mcp-superset
Related Servers
Alternatives to mcp-superset
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
- 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-
- 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 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
- AlicenseBqualityCmaintenanceMCP server providing backend access to PostgreSQL, Storage (Supabase/S3), Iceberg data lake, and SQL seeds. It offers 32 tools for database queries, storage operations, seed management, and more.313MIT
TDQS
Scored across 137 tools
The tools mostly have clear, distinct purposes (e.g., dashboard_list vs chart_list vs dataset_list). A few pairs could be confused, such as superset_sqllab_export_csv vs superset_sqllab_results or superset_chart_data vs superset_chart_get_data, but detailed descriptions mitigate ambiguity. Overall, each tool targets a specific object or action, though the sheer quantity makes selection challenging.
Every tool follows the consistent pattern `superset_<object>_<action>` (e.g., dashboard_create, chart_update, dataset_delete). Exceptions like superset_get_menu or superset_get_current_user still use a verb-oriented convention. No mixed casing or inconsistent verb styles; the prefix `superset_` unifies the entire set.
With 137 tools, this is far beyond the typical well-scoped server and exceeds even the 50+ threshold for an extreme mismatch. While Superset is a complex platform, exposing this many tools burdens the agent with excessive choice and likely includes many rarely-used operations. The count is inappropriate for efficient discovery and selection.
The tool surface covers comprehensive CRUD and lifecycle operations for all major Superset entities: dashboards, charts, databases, datasets, users, roles, RLS rules, tags, reports, annotations, and groups. It also includes import/export, bulk operations, permissions auditing, and SQL lab utilities. No obvious gaps prevent common workflows; the set is remarkably thorough.