MCP Superset logo

MCP Superset

by bintocher

Manage Superset dashboards, charts, datasets, SQL Lab, security, and access controls through MCP.

Install MCP Superset

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "bintocher-mcp-superset": {
      "command": "uvx",
      "args": [
        "mcp-superset"
      ],
      "env": {
        "SUPERSET_BASE_URL": "YOUR_VALUE_HERE",
        "SUPERSET_USERNAME": "YOUR_VALUE_HERE",
        "SUPERSET_PASSWORD": "YOUR_VALUE_HERE",
        "SUPERSET_AUTH_PROVIDER": "YOUR_VALUE_HERE",
        "SUPERSET_SESSION_COOKIE": "YOUR_VALUE_HERE",
        "SUPERSET_SESSION_COOKIE_NAME": "YOUR_VALUE_HERE",
        "SUPERSET_MCP_HOST": "YOUR_VALUE_HERE",
        "SUPERSET_MCP_PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The bintocher/mcp-superset MCP server exposes Apache Superset administration and analytics operations through 137 MCP tools. It supports dashboard and chart CRUD, datasets, SQL Lab, users, roles, row-level security, groups, permissions audits, reports, tags, and asset import/export. Run it locally with stdio or serve it over streamable HTTP or SSE, using JWT authentication or a Superset session cookie. Reach for it when an AI client needs to inspect, modify, or govern Superset resources with confirmation checks and SQL safety controls.

Use cases

  • Manage Superset dashboards and native filters
  • Query saved charts and SQL Lab data
  • Audit user, dataset, and dashboard permissions
  • Automate Superset asset export and import

Key features

  • 137 MCP tools for Apache Superset
  • Dashboard and chart CRUD with import/export
  • SQL Lab query execution and CSV export
  • User, role, group, and RLS management
  • Confirmation checks and DDL/DML blocking
  • HTTP, SSE, and stdio transports

Tools80

What MCP Superset lets your agent do. Expand a tool for its parameters.

Self-reported~1.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

21/21 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · mcp-superset (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars60Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
Tools exposed80Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Superset works

What bintocher/mcp-superset MCP server does

The bintocher/mcp-superset MCP server connects an MCP-compatible client to an Apache Superset instance. Its 137 tools cover administrative, content-management, analytics, and access-control workflows. Dashboard operations include listing, filtering, creating, updating, copying, publishing, exporting, importing, and managing native filters or embedded settings. Chart tools support CRUD operations, duplication, saved-chart data retrieval, query execution, and asset transfer.

Beyond dashboards and charts, the project covers databases, datasets, SQL Lab, users, roles, permissions, row-level security, groups, reports, annotations, tags, and saved queries. It also provides access-control operations for dashboards and automatic datasource permission synchronization, plus a permissions matrix for auditing access across users, dashboards, datasets, and RLS rules.

How it works

The server communicates with Superset through its REST API and presents those operations as MCP tools. It can run with streamable HTTP, SSE, or stdio transport. HTTP is the default transport, while stdio is suitable for desktop clients that launch the process locally. The bind host, port, and transport can be selected with command-line options or environment variables.

Authentication can use Superset username and password credentials, with the authentication provider set to database or LDAP. For Superset deployments behind SSO, OAuth, or SAML, the server can instead send a browser session cookie. Cookie authentication does not renew the session; an expired cookie requires a new value and a server restart. JWT handling includes token refresh and CSRF handling when using the credential-based login flow.

Setup and configuration

Install the mcp-superset package from PyPI with pip, uv, or uvx. Running uvx mcp-superset starts the server without a separate installation. A local .env file or exported variables should define SUPERSET_BASE_URL, SUPERSET_USERNAME, and SUPERSET_PASSWORD for the standard login path. SUPERSET_AUTH_PROVIDER selects db or ldap.

For session-cookie authentication, set SUPERSET_SESSION_COOKIE and, when necessary, SUPERSET_SESSION_COOKIE_NAME. The cookie name defaults to session, but Superset deployments may configure another name. SUPERSET_MCP_HOST, SUPERSET_MCP_PORT, and SUPERSET_MCP_TRANSPORT control server binding and transport. The CLI also accepts --env-file for a specific environment file.

The bintocher/mcp-superset MCP server can be added to Claude Desktop with a stdio command such as uvx mcp-superset --transport stdio.

Tools and capabilities

  • Manage dashboards, charts, datasets, databases, tags, reports, annotations, and saved queries.
  • Execute SQL Lab queries, format SQL, estimate query cost, and export results as CSV.
  • Inspect chart data and dashboard relationships, including the charts and datasets used by a dashboard.
  • Configure dashboard native filters and embedded-mode domains.
  • Manage users, roles, permissions, groups, and row-level security rules.
  • Export and import dashboards, charts, datasets, and complete instance assets.
  • Apply confirmation requirements to destructive actions and block DDL or DML in SQL Lab.

Limitations and notes

The bintocher/mcp-superset MCP server requires access to a compatible Superset deployment and credentials or a valid session cookie. The README targets Superset 6.0.1. Session cookies grant the associated Superset account's access for their lifetime, so they should be treated as credentials and kept out of shell history and committed configuration. Destructive operations such as deletion and filter resets require confirmation, and SQL Lab safety restrictions may prevent DDL or DML statements.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Superset

Install it from PyPI with pip or uv, or run it without installation using `uvx mcp-superset`.

Yes.

The standard login configuration uses `SUPERSET_BASE_URL`, `SUPERSET_USERNAME`, and `SUPERSET_PASSWORD`. Session-cookie authentication uses `SUPERSET_SESSION_COOKIE` instead of username and password.

Yes. It supports streamable HTTP, SSE, and stdio transports. Streamable HTTP is the default.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Superset AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/bintocher-mcp-superset?style=directory)](https://allmcps.com/mcp/bintocher-mcp-superset)
HTML Embed
<a href="https://allmcps.com/mcp/bintocher-mcp-superset"><img src="https://allmcps.com/api/badge/bintocher-mcp-superset?style=directory" alt="MCP Superset on AllMCPs" /></a>