Skip to main content
Glama
aptro

Superset MCP Integration

by aptro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Superset MCP Integration

No user-submitted related servers found.

    Related Servers

    • superset-mcp

      thedeceptio
      F
      license
      B
      quality
      D
      maintenance
      An 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
      -

    • Superset MCP Server

      okybaguslukmana
      A
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      43 npm
      MIT

    • mcp-superset

      chenwenyu1014
      A
      license
      Not graded
      quality
      C
      maintenance
      A 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

    • Metabase MCP Plus

      schachan
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.
      22
      MIT

    • Zaturn

      kdqed
      A
      license
      A
      quality
      C
      maintenance
      An open-source MCP server that connects to various data sources (SQL databases, CSV, Parquet files), allowing AI models to execute SQL queries and generate data visualizations for analytics and business intelligence.
      12
      75
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 60 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (chart, dashboard, database, etc.) and action (create, get, list, update, delete), making it easy to distinguish between them. For example, superset_chart_create and superset_chart_update are clearly different operations on the same resource.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with a superset_ prefix, using snake_case throughout. The naming convention is highly predictable: superset_resource_action (e.g., superset_dashboard_list, superset_database_create). There are no deviations in style or structure across all 60 tools.

    Tool Count2/5

    With 60 tools, this is an extremely large set that feels overwhelming for an MCP server. While Superset is a complex platform, 60 tools will be difficult for agents to navigate and may cause confusion. This exceeds the typical well-scoped range of 3-15 tools and approaches the extreme mismatch threshold.

    Completeness5/5

    The tool surface provides comprehensive coverage of the Superset API domain with complete CRUD operations for all major resources (charts, dashboards, databases, datasets, tags, etc.). There are no obvious gaps - the tools cover authentication, data exploration, SQL execution, metadata management, and user operations, providing full lifecycle support.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources