mcp-server-sigma
Related Servers
Alternatives to mcp-server-sigma
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server for Apache Superset. Gives AI assistants full control over your Superset instance — dashboards, charts, datasets, SQL Lab, users, roles, RLS, and more — through 137 tools.MIT
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade MCP server providing 102 production-ready tools for Jira, Confluence, and Bitbucket, enabling AI agents to manage issues, pages, repositories, and more via natural language.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that wraps the Tableau REST API and VizQL Data Service to expose tools for listing workbooks/datasources and querying datasources, enabling LLM agents to interact with Tableau Server/Cloud through natural language.-
- FlicenseNot gradedqualityDmaintenanceA modular MCP server exposing tools for integrating with services like GitHub, Redash, Jenkins, Figma, Jira, Confluence, Teams, Datadog, PagerDuty, Slack, and Presto, enabling users to manage these platforms through natural language via an MCP client.-
- AlicenseNot gradedqualityDmaintenanceComprehensive MCP server providing 89 tools and 13 React UI apps for complete Zendesk Support API integration, enabling ticket, user, organization, and automation management.MIT
- AlicenseAqualityAmaintenanceFull-featured MCP server for Apache Superset — 135+ tools for dashboards, charts, datasets, SQL Lab, security (users, roles, RLS, groups), audit, and more. Built-in safety validations.1001,258 PyPI60MIT
TDQS
Scored across 172 tools
Heavy duplication: list_workbooks vs list_all_workbooks, list_reports vs list_all_reports, list_members vs list_all_members, list_teams vs list_all_teams, and list_tenants vs list_tenants_paginated create near-identical pairs. Grant tools are scattered across workbooks_, workspace_, datasets_, and admin_ prefixes with overlapping semantics, and update_user_attribute_for_teams vs set_user_attribute_for_teams vs delete_user_attribute_for_team are hard to tell apart.
Names consistently use snake_case with a module prefix (workbooks_, datasets_, elements_, workspace_, admin_) plus verb_noun, which is predictable and readable. Minor deviations exist (e.g. workbooks_run_workbook_agent, admin_api_capabilities, arbitrary choice between workbooks_ and elements_ for workbook element tools).
172 tools is an extreme mismatch for any server scope, far beyond the 3-15 sweet spot. The surface is bloated with pagination variants, redundant list tools, and granular admin operations that should be consolidated or split into separate servers.
Coverage is remarkably broad: workbooks, reports, templates, data models, connections, elements, workspaces, tags, deployments, tenants, teams, user attributes, IP allowlists, and webhooks. A few gaps are self-documented, e.g. the direct POST to assign user attributes for users is not exposed and must be worked around.