Skip to main content
Glama
christianclaudio

mcp-server-sigma

Related Servers

Alternatives to mcp-server-sigma

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Comprehensive MCP server providing 89 tools and 13 React UI apps for complete Zendesk Support API integration, enabling ticket, user, organization, and automation management.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Full-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.
      100
      461 PyPI
      59
      MIT

    TDQS

    C2.9/5.0

    Scored across 155 tools

    Disambiguation2/5

    Many tools have overlapping purposes or are convenience wrappers that duplicate existing functionality. Examples include list_all_* vs list_* (pagination variants), materialize_element vs materialize_and_wait, export_workbook vs export_and_download, bulk_assign_team_members vs update_team_members, and update_user_attribute_for_users vs delete_user_attribute_for_user. These near-duplicates create significant ambiguity about which tool to use.

    Naming Consistency4/5

    Naming follows a consistent sigma_ prefix and snake_case verb_noun pattern (e.g., list_workbooks, get_connection, create_report). Minor deviations exist: sigma_api_capabilities and sigma_formula_pitfalls are noun phrases, and compound verbs like materialize_and_wait and export_and_download break the simple verb_noun structure. Overall, patterns are predictable and readable.

    Tool Count1/5

    With 155 tools, the server massively exceeds practical limits for agent tool selection. Many tools are redundant wrappers, pagination variants, or meta utilities (e.g., list_all_workbooks, materialize_and_wait, search_docs). This creates cognitive overload and makes it difficult for an agent to choose the correct tool efficiently.

    Completeness4/5

    The server provides highly extensive lifecycle coverage for most resources: workbooks, reports, data models, connections, members, teams, workspaces, deployments, tags, and user attributes all have comprehensive CRUD and auxiliary operations. Minor gaps include dedicated delete operations for workbooks/reports (workaround via sigma_delete_file) and deletion of report schedules, but these are easily circumvented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues