Skip to main content
Glama

superset-mcp

Apache Superset을 위한 MCP(Model Context Protocol) 서버입니다. AI 어시스턴트가 대시보드, 차트, 데이터셋, 데이터베이스 및 SQL 실행을 포함하여 Superset 인스턴스에 완전히 액세스할 수 있도록 합니다.

사전 요구 사항

  • uv — Python 패키지 관리자

  • 실행 중인 Apache Superset 인스턴스에 대한 액세스 권한

Related MCP server: Zaturn

설정 (약 1분 소요)

1. 저장소 복제

git clone <repo-url>
cd superset-mcp

2. 자격 증명 구성

cp .env.example .env

.env 파일 편집:

SUPERSET_URL=http://your-superset-host:8088
SUPERSET_USERNAME=your-username
SUPERSET_PASSWORD=your-password

3. 작동 테스트

uv run superset-mcp

MCP 서버가 오류 없이 시작되는 것을 확인할 수 있습니다. 중지하려면 Ctrl+C를 누르세요.


AI 클라이언트에 연결

/ABSOLUTE/PATH/TO/superset-mcp를 저장소를 복제한 실제 경로로 바꾸세요.

Claude Code

~/.claude/settings.json(또는 프로젝트 수준의 .claude/settings.json)에 추가:

{
  "mcpServers": {
    "superset": {
      "command": "uv",
      "args": ["--directory", "/ABSOLUTE/PATH/TO/superset-mcp", "run", "superset-mcp"],
      "env": {
        "SUPERSET_URL": "http://your-superset-host:8088",
        "SUPERSET_USERNAME": "your-username",
        "SUPERSET_PASSWORD": "your-password"
      }
    }
  }
}

또는 터미널에서 실행:

claude mcp add superset -- uv --directory /ABSOLUTE/PATH/TO/superset-mcp run superset-mcp

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json(macOS) 또는 %APPDATA%\Claude\claude_desktop_config.json(Windows)에 추가:

{
  "mcpServers": {
    "superset": {
      "command": "uv",
      "args": ["--directory", "/ABSOLUTE/PATH/TO/superset-mcp", "run", "superset-mcp"],
      "env": {
        "SUPERSET_URL": "http://your-superset-host:8088",
        "SUPERSET_USERNAME": "your-username",
        "SUPERSET_PASSWORD": "your-password"
      }
    }
  }
}

Cursor

프로젝트의 .cursor/mcp.json 또는 전역 ~/.cursor/mcp.json에 추가:

{
  "mcpServers": {
    "superset": {
      "command": "uv",
      "args": ["--directory", "/ABSOLUTE/PATH/TO/superset-mcp", "run", "superset-mcp"],
      "env": {
        "SUPERSET_URL": "http://your-superset-host:8088",
        "SUPERSET_USERNAME": "your-username",
        "SUPERSET_PASSWORD": "your-password"
      }
    }
  }
}

사용 가능한 도구

대시보드

도구

설명

list_dashboards

모든 대시보드 나열 (선택적 검색 포함)

get_dashboard

ID 또는 슬러그로 대시보드 가져오기

get_dashboard_charts

대시보드의 모든 차트 가져오기

get_dashboard_datasets

대시보드에서 사용하는 모든 데이터셋 가져오기

create_dashboard

새 대시보드 생성

update_dashboard

제목, 레이아웃, 메타데이터 업데이트

publish_dashboard

초안 대시보드 게시

copy_dashboard

대시보드 복제

delete_dashboard

대시보드 삭제

차트

도구

설명

list_charts

모든 차트 나열 (선택적 검색 포함)

get_chart

ID 또는 UUID로 차트 가져오기

get_chart_data

차트의 최신 데이터 가져오기

create_chart

새 차트 생성

update_chart

차트 속성 업데이트

delete_chart

차트 삭제

데이터셋

도구

설명

list_datasets

모든 데이터셋 나열

get_dataset

ID 또는 UUID로 데이터셋 가져오기

create_dataset

테이블 또는 SQL 쿼리에서 생성

get_or_create_dataset

기존 데이터셋 가져오기 또는 새로 생성

refresh_dataset

소스 테이블에서 열 동기화

update_dataset

데이터셋 속성 업데이트

get_dataset_related_objects

해당 데이터셋을 사용하는 차트/대시보드 확인

delete_dataset

데이터셋 삭제

데이터베이스

도구

설명

list_databases

모든 데이터베이스 연결 나열

get_database

ID로 데이터베이스 연결 가져오기

list_schemas

데이터베이스의 스키마 나열

list_tables

스키마의 테이블 나열

get_table_metadata

테이블의 열 정보 가져오기

get_select_star

테이블에 대한 SELECT * 템플릿 가져오기

SQL

도구

설명

execute_sql

SQL 쿼리 실행 및 결과 가져오기

format_sql

SQL 쿼리 예쁘게 출력

estimate_query_cost

쿼리 비용 추정 (지원되는 경우)

list_saved_queries

저장된 SQL 쿼리 나열

save_query

SQL 쿼리 저장


예시 프롬프트

AI 어시스턴트에 연결된 후:

  • "게시된 모든 대시보드 나열"

  • "'Sales Overview'라는 새 대시보드 생성"

  • "대시보드 11의 모든 차트 보여줘"

  • "데이터베이스 2에서 SQL 쿼리 실행: SELECT count(*) FROM orders"

  • "'Revenue' 대시보드에서 사용하는 데이터셋은 무엇인가요?"

  • "데이터셋 5를 사용하여 지역별 매출을 보여주는 막대 차트 생성"

Available Tools

34 tools
copy_dashboardC

Create a copy of a dashboard.

Inputs: id_or_slug (required). Returns: object

create_chartC

Create a new chart.

Inputs: slice_name (required), viz_type (required), datasource_id (required), datasource_type, +3 more. Returns: object

create_dashboardC

Create a new dashboard.

Inputs: title (required), slug, published, json_metadata, +1 more. Returns: object

create_datasetB

Create a dataset from a table or SQL query.

Inputs: database_id (required), table_name (required), schema, sql, +1 more. Returns: object

delete_chartC

Delete a chart by ID.

Inputs: pk (required). Returns: object

delete_dashboardC

Delete a dashboard by ID.

Inputs: pk (required). Returns: object

delete_datasetB

Delete a dataset by ID.

Inputs: pk (required). Returns: object

estimate_query_costC

Estimate the cost of running a SQL query (supported databases only).

Inputs: database_id (required), sql (required), schema. Returns: object

execute_sqlB

Execute a SQL query and return results.

Inputs: database_id (required), sql (required), schema, limit. Returns: object

format_sqlB

Format/pretty-print a SQL query.

Inputs: sql (required). Returns: object

get_chartC

Get a chart by ID or UUID.

Inputs: id_or_uuid (required). Returns: object

get_chart_dataC

Fetch the latest data for a chart.

Inputs: pk (required). Returns: object

get_dashboardB

Get a single dashboard by ID or slug.

Inputs: id_or_slug (required). Returns: object

get_dashboard_chartsB

Get all charts in a dashboard.

Inputs: id_or_slug (required). Returns: object

get_dashboard_datasetsB

Get all datasets used by a dashboard.

Inputs: id_or_slug (required). Returns: object

get_databaseB

Get a database connection by ID.

Inputs: pk (required). Returns: object

get_datasetB

Get a dataset by ID or UUID.

Inputs: id_or_uuid (required). Returns: object

get_or_create_datasetB

Get an existing dataset or create it if it doesn't exist.

Inputs: database_id (required), table_name (required), schema. Returns: object

get_select_starC

Get a SELECT * query for a table (with schema).

Inputs: database_id (required), table_name (required), schema. Returns: object

get_table_metadataC

Get column metadata for a table.

Inputs: database_id (required), table_name (required), schema. Returns: object

list_chartsC

List charts. Optionally filter by name.

Inputs: page, page_size, search. Returns: object

list_dashboardsB

List dashboards. Optionally filter by title with search.

Inputs: page, page_size, search. Returns: object

list_databasesB

List all database connections configured in Superset.

Inputs: page, page_size. Returns: object

list_datasetsC

List datasets (virtual or physical tables).

Inputs: page, page_size, search. Returns: object

list_saved_queriesB

List saved SQL queries.

Inputs: page, page_size. Returns: object

list_schemasB

List all schemas in a database.

Inputs: database_id (required). Returns: object

list_tablesB

List tables in a database schema.

Inputs: database_id (required), schema. Returns: object

publish_dashboardC

Set a dashboard as published.

Inputs: pk (required). Returns: object

refresh_datasetC

Refresh the dataset's columns and metrics from the source.

Inputs: pk (required). Returns: object

save_queryC

Save a SQL query.

Inputs: label (required), sql (required), database_id (required), schema, +1 more. Returns: object

update_chartC

Update a chart's properties.

Inputs: pk (required), slice_name, description, viz_type, +2 more. Returns: object

update_dashboardC

Update an existing dashboard.

Inputs: pk (required), title, published, json_metadata, +1 more. Returns: object

update_datasetC

Update a dataset's properties.

Inputs: pk (required), table_name, description, sql, +3 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 34 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources (charts, dashboards, datasets, databases, queries) and actions (create, get, list, update, delete, execute, format, etc.), with no apparent overlap or ambiguity. For example, get_chart, get_chart_data, and list_charts serve different functions without confusion.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as create_chart, delete_dashboard, list_datasets, and update_dataset, with no deviations in style or convention. This predictability makes the tool set easy to navigate and understand.

    Tool Count3/5

    With 34 tools, the count is borderline high for typical MCP server scopes, which often range from 3-15 tools. While it covers a comprehensive Superset domain, it may feel heavy and potentially overwhelming for agents, though not extreme like 50+ tools.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for charts, dashboards, datasets, and queries, along with execution, formatting, and metadata operations. There are no obvious gaps; agents can perform all core workflows from creation to deletion and analysis without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP 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.
      60
      195
      MIT
    • A
      license
      A
      quality
      D
      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
    • A
      license
      Not graded
      quality
      D
      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.
      MIT
    • A
      license
      A
      quality
      D
      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