MCP server for reading and editing Apache Superset dataset data
Superset MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Superset MCP directly instead of describing what you should do. MCP server for reading and editing Apache Superset dataset data.
A Model Context Protocol (MCP) server for managing Apache Superset datasets, metrics, and SQL queries.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 4 environment variables: SUPERSET_BASE_URL, SUPERSET_USERNAME, SUPERSET_PASSWORD, SUPERSET_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by Winding2020; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
{
"mcpServers": {
"superset-mcp": {
"command": "npx",
"args": [
"-y",
"superset-mcp"
],
"env": {
"SUPERSET_BASE_URL": "",
"SUPERSET_USERNAME": "",
"SUPERSET_PASSWORD": ""
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SUPERSET_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| SUPERSET_USERNAME | Configuration value read at startup. | Optional |
| SUPERSET_PASSWORD | Configuration value read at startup. | Optional |
| SUPERSET_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.