MCP Superset

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. The README also documents HTTP configuration for Claude Code and identifies Cursor as a stdio use case.

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.