superset-mcp-server
An MCP server package that exposes Apache Superset functionality to AI agents via the Model Context Protocol (MCP).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No concrete repository/manifest details were provided to verify TLS enforcement, dependency health, secret handling, or auth/scoping in the MCP layer. Superset security ultimately depends on deployment configuration; ensure the MCP server does not log credentials and that Superset access controls are strictly enforced per agent/user.
⚡ Reliability
Best When
You want to connect Superset to an MCP-capable agent framework and can provide/secure any required Superset credentials and network access.
Avoid When
You cannot validate tool coverage, auth model, error behavior, or pagination for the specific Superset resources you need.
Use Cases
- • Allow an agent to query and interact with Superset resources (e.g., dashboards/queries) through MCP tools
- • Automate reporting workflows where the agent needs to retrieve Superset artifacts or run/query data exposed by Superset
- • Integrate Superset with agentic workflows using standardized MCP tool calling
Not For
- • High-volume automated production workloads without verifying Superset deployment behavior and performance
- • Security-sensitive environments where authentication/authorization and data access controls are not clearly documented for the MCP layer
- • Replacing Superset’s native web/REST APIs for all use cases
Interface
Authentication
Authentication specifics for the MCP server are not provided in the supplied input, so auth approach cannot be confirmed. Superset deployments may require session/token/SSO; verify how (and whether) MCP forwards credentials and enforces access controls.
Pricing
Pricing information not provided; MCP server is typically self-hosted, but costs depend on your Superset infrastructure.
Agent Metadata
Known Gotchas
- ⚠ MCP tool coverage may be incomplete for all Superset operations you expect; agents should be constrained to documented tools.
- ⚠ Superset permissioning is critical: agents may fail or receive errors if Superset roles/datasets/dashboards are not accessible.
- ⚠ If the MCP server performs state-changing actions (if any), idempotency and retry safety are unclear—avoid blind retries without guarantees.
- ⚠ If pagination exists in underlying Superset endpoints, the MCP interface may not expose stable paging parameters, leading to partial results.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for superset-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.