analytics-data

Qlik Sense

bintocher

by bintocher

Integrate with Qlik Sense for automated BI workflows, data model queries, app management, and efficient data extraction

Integrates with Qlik Sense Enterprise through Repository and Engine APIs to enable querying data models, managing applications and users, extracting table data, and automating reload tasks for business intelligence workflows.

github stars

24

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

10 comprehensive toolsCertificate-based authenticationUnified Repository and Engine API access

best for

  • / Business intelligence analysts working with Qlik Sense
  • / Data engineers automating BI workflows
  • / Developers integrating Qlik Sense with other systems

capabilities

  • / Query data models and create hypercubes
  • / Extract table data from applications
  • / Manage applications and user permissions
  • / Automate data reload tasks
  • / Extract application scripts and metadata
  • / Analyze fields and master items

what it does

Connects to Qlik Sense Enterprise to query data models, manage applications and users, and automate business intelligence workflows through Repository and Engine APIs.

about

Qlik Sense is a community-built MCP server published by bintocher that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with Qlik Sense for automated BI workflows, data model queries, app management, and efficient data extraction It is categorized under analytics data.

how to install

You can install Qlik Sense in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

Qlik Sense is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

Qlik Sense MCP Server

PyPI version PyPI downloads License: MIT Python versions

Model Context Protocol (MCP) server for integration with Qlik Sense Enterprise APIs. Provides unified interface for Repository API and Engine API operations through MCP protocol.

Table of Contents

Overview

Qlik Sense MCP Server bridges Qlik Sense Enterprise with systems supporting Model Context Protocol. Server provides 10 comprehensive tools for complete Qlik Sense analytics workflow including application discovery, data analysis, script extraction, and metadata management.

Key Features

  • Unified API: Single interface for Qlik Sense Repository and Engine APIs
  • Security: Certificate-based authentication support
  • Performance: Optimized queries and direct API access
  • Analytics: Advanced data analysis and hypercube creation
  • Metadata: Comprehensive application and field information

Features

Available Tools

ToolDescriptionAPIStatus
get_appsGet comprehensive list of applications with metadataRepository
get_app_detailsGet compact app overview (metadata, fields, master items, sheets/objects)Repository
get_app_sheetsGet list of sheets from application with title and descriptionEngine
get_app_sheet_objectsGet list of objects from specific sheet with object ID, type and descriptionEngine
get_app_scriptExtract load script from applicationEngine
get_app_fieldReturn values of a field with pagination and wildcard searchEngine
get_app_variablesReturn variables split by source with pagination and wildcard searchEngine
get_app_field_statisticsGet comprehensive field statisticsEngine
engine_create_hypercubeCreate hypercube for data analysisEngine
get_app_objectGet specific object layout by ID (GetObject + GetLayout)Engine

Installation

Quick Start with uvx (Recommended)

The easiest way to use Qlik Sense MCP Server is with uvx:

uvx qlik-sense-mcp-server

This command will automatically install and run the latest version without affecting your system Python environment.

Alternative Installation Methods

From PyPI

pip install qlik-sense-mcp-server

From Source (Development)

git clone https://github.com/bintocher/qlik-sense-mcp.git
cd qlik-sense-mcp
make dev

System Requirements

  • Python 3.12+
  • Qlik Sense Enterprise
  • Valid certificates for authentication
  • Network access to Qlik Sense server (ports 4242 Repository, 4747 Engine)
  • Ensure your MCP client model can handle large JSON responses; prefer small limits in requests during testing

Setup

  1. Setup certificates
mkdir certs
# Copy your Qlik Sense certificates to certs/ directory
  1. Create configuration
cp .env.example .env
# Edit .env with your settings

Configuration

Environment Variables (.env)

# Server connection
QLIK_SERVER_URL=https://your-qlik-server.company.com
QLIK_USER_DIRECTORY=COMPANY
QLIK_USER_ID=your-username

# Certificate paths (absolute paths)
QLIK_CLIENT_CERT_PATH=/path/to/certs/client.pem
QLIK_CLIENT_KEY_PATH=/path/to/certs/client_key.pem
QLIK_CA_CERT_PATH=/path/to/certs/root.pem

# API ports (standard Qlik Sense ports)
QLIK_REPOSITORY_PORT=4242
QLIK_ENGINE_PORT=4747

# Optional HTTP port for metadata requests
QLIK_HTTP_PORT=443

# SSL settings
QLIK_VERIFY_SSL=false

Optional Environment Variables

# Logging level (default: INFO)
LOG_LEVEL=INFO

# Engine WebSocket timeouts and retries
QLIK_WS_TIMEOUT=8.0     # seconds
QLIK_WS_RETRIES=2       # number of endpoints to try

MCP Configuration

Create mcp.json file for MCP client integration:

{
  "mcpServers": {
    "qlik-sense": {
      "command": "uvx",
      "args": ["qlik-sense-mcp-server"],
      "env": {
        "QLIK_SERVER_URL": "https://your-qlik-server.company.com",
        "QLIK_USER_DIRECTORY": "COMPANY",
        "QLIK_USER_ID": "your-username",
        "QLIK_CLIENT_CERT_PATH": "/absolute/path/to/certs/client.pem",
        "QLIK_CLIENT_KEY_PATH": "/absolute/path/to/certs/client_key.pem",
        "QLIK_CA_CERT_PATH": "/absolute/path/to/certs/root.pem",
        "QLIK_REPOSITORY_PORT": "4242",
        "QLIK_PROXY_PORT": "4243",
        "QLIK_ENGINE_PORT": "4747",
        "QLIK_HTTP_PORT": "443",
        "QLIK_VERIFY_SSL": "false",
        "QLIK_HTTP_TIMEOUT": "10.0",
        "QLIK_WS_TIMEOUT": "8.0",
        "QLIK_WS_RETRIES": "2",
        "LOG_LEVEL": "INFO"
      },
      "disabled": false,
      "autoApprove": [
        "get_apps",
        "get_app_details",
        "get_app_script",
        "get_app_field_statistics",
        "engine_create_hypercube",
        "get_app_field",
        "get_app_variables",
        "get_app_sheets",
        "get_app_sheet_objects",
        "get_app_object"
      ]
    }
  }
}

Environment Variables Configuration

The server requires the following environment variables for configuration:

Required Variables

  • QLIK_SERVER_URL - Qlik Sense server URL (e.g., https://qlik.company.com)
  • QLIK_USER_DIRECTORY - User directory for authentication (e.g., COMPANY)
  • QLIK_USER_ID - User ID for authentication (e.g., your-username)

Certificate Configuration (Required for production)

  • QLIK_CLIENT_CERT_PATH - Absolute path to client certificate file (.pem format)
  • QLIK_CLIENT_KEY_PATH - Absolute path to client private key file (.pem format)
  • QLIK_CA_CERT_PATH - Absolute path to CA certificate file (.pem format). If not specified, SSL certificate verification will be disabled

Network Configuration

  • QLIK_REPOSITORY_PORT - Repository API port (default: 4242)
  • QLIK_PROXY_PORT - Proxy API port for authentication (default: 4243)
  • QLIK_ENGINE_PORT - Engine API port for WebSocket connections (default: 4747)
  • QLIK_HTTP_PORT - HTTP API port for metadata requests (optional, only used for /api/v1/apps/{id}/data/metadata endpoint)

SSL and Security

  • QLIK_VERIFY_SSL - Verify SSL certificates (true/false, default: true)

Timeouts and Performance

  • QLIK_HTTP_TIMEOUT - HTTP request timeout in seconds (default: 10.0)
  • QLIK_WS_TIMEOUT - WebSocket connection timeout in seconds (default: 8.0)
  • QLIK_WS_RETRIES - Number of WebSocket connection retry attempts (default: 2)

Logging

  • LOG_LEVEL - Logging level (DEBUG, INFO, WARNING, ERROR, default: INFO)

Usage

Start Server

# Using uvx (recommended)
uvx qlik-sense-mcp-server

# Using installed package
qlik-sense-mcp-server

# From source (development)
python -m qlik_sense_mcp_server.server

Example Operations

Get Applications List

# Via MCP client - get first 50 apps (default)
result = mcp_client.call_tool("get_apps")
print(f"Showing {result['pagination']['returned']} of {result['pagination']['total_found']} apps")

# Search for specific apps
result = mcp_client.call_tool("get_apps", {
    "name_filter": "Sales",
    "limit": 10
})

# Get more apps (pagination)
result = mcp_client.call_tool("get_apps", {
    "offset": 50,
    "limit": 50
})

Analyze Application

# Get comprehensive app analysis
result = mcp_client.call_tool("get_app_details", {
    "app_id": "your-app-id"
})
print(f"App has {len(result['data_model']['tables'])} tables")

Create Data Analysis Hypercube

# Create hypercube for sales analysis
result = mcp_client.call_tool("engine_create_hypercube", {
    "app_id": "your-app-id",
    "dimensions": ["Region", "Product"],
    "measures": ["Sum(Sales)", "Count(Orders)"],
    "max_rows": 1000
})

Get Field Statistics

# Get detailed field statistics
result = mcp_client.call_tool("get_app_field_statistics", {
    "app_id": "your-app-id",
    "field_name": "Sales"
})
print(f"Average: {result['avg_value']['numeric']}")

API Reference

get_apps

Retrieves comprehensive list of Qlik Sense applications with metadata, pagination and filtering support.

Parameters:

  • limit (optional): Maximum number of apps to return (default: 50, max: 1000)
  • offset (optional): Number of apps to skip for pagination (default: 0)
  • name_filter (optional): Filter apps by name (case-insensitive partial match)
  • app_id_filter (optional): Filter by specific app ID/GUID
  • include_unpublished (optional): Include unpublished apps (default: true)

Returns: Object containing paginated apps, streams, and pagination metadata

Example (default - first 50 apps):

{
  "apps": [...],
  "streams": [...],
  "pagination": {
    "limit": 50,
    "offset": 0,
    "returned": 50,
    "total_found": 1598,
    "has_more": true,
    "next_offset": 50
  },
  "filters": {
    "name_filter": null,
    "app_id_filter": null,
    "include_unpublished": true
  },
  "summary": {
    "total_apps": 1598,
    "published_apps": 857,
    "private_apps": 741,
    "total_streams": 40,
    "showing": "1-50 of 1598"
  }
}

Example (with name filter):

# Search for apps containing "dashboard"
result = 

---

FAQ

What is the Qlik Sense MCP server?
Qlik Sense is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Qlik Sense?
This profile displays 28 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.628 reviews
  • Ganesh Mohane· Dec 28, 2024

    Qlik Sense is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Fatima Thompson· Dec 28, 2024

    Strong directory entry: Qlik Sense surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Michael Martin· Dec 12, 2024

    We wired Qlik Sense into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Rahul Santra· Nov 19, 2024

    Strong directory entry: Qlik Sense surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Yusuf Chen· Nov 19, 2024

    Qlik Sense is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Fatima Martin· Nov 3, 2024

    Qlik Sense is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Fatima Dixit· Oct 22, 2024

    Qlik Sense has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Pratham Ware· Oct 10, 2024

    Useful MCP listing: Qlik Sense is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Yusuf Jackson· Oct 10, 2024

    Qlik Sense reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Benjamin Reddy· Sep 21, 2024

    I recommend Qlik Sense for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

showing 1-10 of 28

1 / 3