Avo vs MCP Superset
A side-by-side look at the Avo and MCP Superset MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Avo for data platforms work over a hosted endpoint; choose MCP Superset for data platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Avo when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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 | 44/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | SUPERSET_BASE_URLSUPERSET_USERNAMESUPERSET_PASSWORDSUPERSET_AUTH_PROVIDERSUPERSET_SESSION_COOKIESUPERSET_SESSION_COOKIE_NAMESUPERSET_MCP_HOSTSUPERSET_MCP_PORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 59 |
| Directory activity | 65 views 0 installs 1 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 80 |
| Full listing | View Avo | View MCP Superset |
Tools & capabilities
Avo tools
No tool names declared yet. Check the project README from the listing page.
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
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.
Avo
{
"mcpServers": {
"avo": {
"url": "https://mcp.avo.app/mcp"
}
}
}
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"
}
}
}
}
Frequently asked questions
Avo is categorized under Data Platforms and uses a remote HTTP/SSE transport. MCP Superset belongs to Data Platforms and uses a local stdio subprocess. Pick Avo for data platforms work and MCP Superset 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.
Avo has no declared pricing — check the project's own site. Auth: oauth 2.0. MCP Superset is listed as free. Auth: other. 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 avo and bintocher-mcp-superset as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Avo has a quality signal of 44/100 (Fair) with 65 views, 0 installs and 1 GitHub stars. MCP Superset has 63/100 (Good) with 5 views, 0 installs and 59 GitHub stars.