Skip to main content
Glama
bintocher

Qlik Sense MCP Server

Related Servers

Alternatives to Qlik Sense MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for Qlik Sense Enterprise on Windows (client-managed) that exposes the on-prem Qlik API surface as MCP tools, enabling agents to query, govern, and build against the site.
      28 npm
      7
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Connects AI assistants like Claude to Qlik Cloud and Qlik Sense Enterprise environments, enabling natural language interactions for analytics, app management, reloads, user administration, and data governance across 34 tools.
      34
      16
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server providing 25 tools for search, alerting, KV Store management, and index administration in Splunk Enterprise and Cloud, enabling LLM-powered interaction.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides over 60 administrative tools for managing users, groups, roles, schedules, alerts, and content access within Looker through the Model Context Protocol. It enables full administration of Looker environments, including permission management and system configuration.
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI applications to interact with Power BI through the Model Context Protocol, supporting comprehensive API operations including data retrieval and management.
      -

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Qlik Sense resources like apps, fields, objects, sheets, variables, or hypercubes, with no overlap in functionality. The descriptions reinforce this by detailing unique operations such as retrieving field statistics versus field values, ensuring agents can easily differentiate between tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get_' or 'engine_' prefixes, using snake_case uniformly (e.g., get_app_details, get_app_field, engine_create_hypercube). This predictability makes the tool set easy to navigate and understand at a glance.

    Tool Count5/5

    With 10 tools, the server is well-scoped for interacting with Qlik Sense applications, covering essential operations like listing apps, retrieving details, fields, objects, sheets, variables, scripts, and creating hypercubes. Each tool serves a distinct role without redundancy, fitting the domain appropriately.

    Completeness4/5

    The tool set provides comprehensive read and analysis capabilities for Qlik Sense apps, including data retrieval, statistics, and hypercube creation, but lacks write operations (e.g., updating or deleting apps, fields, or objects). This minor gap may limit agents in full lifecycle management but supports core query and analysis workflows effectively.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive