Qlik MCP

What jwaxman19/qlik-mcp MCP server does

The jwaxman19/qlik-mcp MCP server exposes selected Qlik Cloud API operations through MCP. It is designed for clients such as Claude Desktop and Cursor that need to navigate Qlik content and read data from visualizations.

The server supports four main operations:

• List applications available in the Qlik Cloud workspace, with limit and offset pagination.
• List sheets belonging to a selected application.
• List charts on a selected sheet, including chart IDs, types, and positions.
• Retrieve chart data, including headers, rows, and optionally chart metadata.

Application, sheet, and chart identifiers can be passed through tool inputs. A default application ID can also be configured through the environment, reducing the need to provide it for every request.

How it works

The jwaxman19/qlik-mcp MCP server authenticates requests to Qlik Cloud with an API key and sends them to the configured tenant URL. An agent can first discover applications, then inspect a chosen application's sheets, enumerate the charts on a sheet, and request data from a specific chart.

Chart retrieval supports a maximum total row count and a per-request page size. The include_metadata option controls whether chart metadata is returned alongside the data. The configuration also includes retry and delay settings for managing request pacing and transient failures.

Setup and configuration

To run the jwaxman19/qlik-mcp MCP server, create a Qlik Cloud API key with suitable permissions and configure these environment variables:

• QLIK_API_KEY: The Qlik Cloud API key.
• QLIK_BASE_URL: The URL of the Qlik Cloud tenant.
• QLIK_APP_ID: An optional default application ID.
• MAX_ROWS_PER_REQUEST: Request-level row limit configuration.
• MAX_TOTAL_ROWS: Overall row limit configuration.
• REQUEST_DELAY_MS: Delay between requests.
• MAX_RETRIES: Maximum retry count.
• RETRY_DELAY_MS: Delay used between retries.

The repository provides a .env.example template. The README documents local execution with Deno using deno task dev, and also describes running the project in Docker with an environment file. Claude Desktop and Cursor configurations invoke the local Deno entry point from the cloned repository.

Tools and capabilities

The MCP tools are:

• qlik_get_apps: Returns applications and their IDs and information; accepts limit and offset.
• qlik_get_app_sheets: Returns sheet IDs, titles, and metadata for an application.
• qlik_get_sheet_charts: Returns chart IDs, types, and positions for a sheet.
• qlik_get_chart_data: Returns chart headers and rows, with optional metadata and row controls.

Sheet and chart discovery require identifiers for the relevant resources. Chart data extraction requires both a sheet ID and chart ID. The application ID can be supplied to the relevant tools or taken from QLIK_APP_ID.

Limitations and notes

Access depends on the Qlik Cloud API key's permissions and the tenant URL being correct and reachable. Invalid or inaccessible application, sheet, or chart IDs can produce not-found errors. The README also calls out unauthorized, forbidden, and rate-limit responses as issues to check through credentials, permissions, and request pacing.

This server reads data from Qlik visualizations; the provided material does not describe operations for creating or modifying Qlik applications, sheets, charts, or source data. Its documented scope is discovery and chart-data retrieval.