MCP Superset vs Jitsu
A side-by-side look at the MCP Superset and Jitsu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Superset for data platforms work as a local process; choose Jitsu for data platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Superset when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
SUPERSET_BASE_URL, SUPERSET_USERNAME, SUPERSET_PASSWORD, SUPERSET_AUTH_PROVIDER, SUPERSET_SESSION_COOKIE, SUPERSET_SESSION_COOKIE_NAME, SUPERSET_MCP_HOST, SUPERSET_MCP_PORT. - You want tools like
superset_dashboard_list, superset_dashboard_get, superset_dashboard_create.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 63/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | SUPERSET_BASE_URLSUPERSET_USERNAMESUPERSET_PASSWORDSUPERSET_AUTH_PROVIDERSUPERSET_SESSION_COOKIESUPERSET_SESSION_COOKIE_NAMESUPERSET_MCP_HOSTSUPERSET_MCP_PORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 59 | 5,113 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 80 | Not listed |
| Full listing | View MCP Superset | View Jitsu |
Tools & capabilities
MCP Superset tools 80
superset_dashboard_listList dashboards with filtering and paginationsuperset_dashboard_getGet dashboard details by IDsuperset_dashboard_createCreate a new dashboardsuperset_dashboard_updateUpdate dashboard propertiessuperset_dashboard_deleteDelete a dashboard (requires confirmation)superset_dashboard_copyDuplicate a dashboardsuperset_dashboard_publishPublish a draft dashboardsuperset_dashboard_unpublishUnpublish a dashboardsuperset_dashboard_chartsList charts in a dashboardsuperset_dashboard_datasetsList datasets used by a dashboardsuperset_dashboard_exportExport dashboard as ZIP (base64)superset_dashboard_importImport dashboard from ZIP file- +68 more on the listing page
Jitsu tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Superset
{
"mcpServers": {
"bintocher-mcp-superset": {
"command": "uvx",
"args": [
"mcp-superset"
],
"env": {
"SUPERSET_BASE_URL": "YOUR_SUPERSET_BASE_URL_HERE",
"SUPERSET_USERNAME": "YOUR_SUPERSET_USERNAME_HERE",
"SUPERSET_PASSWORD": "YOUR_SUPERSET_PASSWORD_HERE",
"SUPERSET_AUTH_PROVIDER": "YOUR_SUPERSET_AUTH_PROVIDER_HERE",
"SUPERSET_SESSION_COOKIE": "YOUR_SUPERSET_SESSION_COOKIE_HERE",
"SUPERSET_SESSION_COOKIE_NAME": "YOUR_SUPERSET_SESSION_COOKIE_NAME_HERE",
"SUPERSET_MCP_HOST": "YOUR_SUPERSET_MCP_HOST_HERE",
"SUPERSET_MCP_PORT": "YOUR_SUPERSET_MCP_PORT_HERE"
}
}
}
}
Jitsu
No confirmed install command for Jitsu yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Superset is categorized under Data Platforms and uses a local stdio subprocess. Jitsu belongs to Data Platforms and uses an install path we have not confirmed yet. Pick MCP Superset for data platforms work and Jitsu for data platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Jitsu has no confirmed install command yet — follow its own setup instructions.
MCP Superset is listed as free. Auth: other. Jitsu has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bintocher-mcp-superset and jitsu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Superset has a quality signal of 63/100 (Good) with 5 views, 0 installs and 59 GitHub stars. Jitsu has 41/100 (Fair) with 1 views, 0 installs and 5,113 GitHub stars.