Qlik MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QLIK_API_KEY | No | API key from Qlik Cloud hub (required for Qlik Cloud) | |
| QLIK_USER_ID | No | Username to act as (e.g., 'admin') for Qlik Sense Enterprise On-Premise | |
| QLIK_CERT_PATH | No | Folder containing client.pem, client_key.pem, root.pem (required for Qlik Sense Enterprise On-Premise) | |
| QLIK_DEPLOYMENT | No | Deployment type: 'cloud' (default) or 'on-premise' | cloud |
| QLIK_TENANT_URL | No | Qlik Cloud URL or Qlik Sense Enterprise server URL | |
| QLIK_VIRTUAL_PROXY | No | Virtual proxy prefix (if configured) for Qlik Sense Enterprise On-Premise | |
| QLIK_USER_DIRECTORY | No | Windows domain (e.g., 'COMPANY') for Qlik Sense Enterprise On-Premise |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qlik_searchA | Unified search for Qlik resources across Cloud and On-Premise deployments. Replaces: qlik_search_apps, qlik_get_space_items Supported resource types:
Platform differences:
Search examples:
Response ID fields:
Parameters:
|
| qlik_trigger_app_reloadA | Triggers a reload for a Qlik Cloud app. Can optionally wait for completion and poll for status. Usage scenarios:
Parameters:
|
| qlik_get_reload_statusA | Gets the current status of a reload task in Qlik Cloud. Returns information about:
Use this to monitor ongoing reloads or check historical reload results. |
| qlik_cancel_reloadA | Cancels a running reload task in Qlik Cloud. Use cases:
Note: Only running or queued reloads can be cancelled. Completed or already failed reloads cannot be cancelled. |
| qlik_get_spaces_catalogA | Get comprehensive catalog of spaces in Qlik Cloud tenant. Provides detailed information about:
Filter by:
Use cases:
|
| qlik_get_tenant_infoB | Get Qlik Cloud tenant information |
| qlik_get_user_infoC | Get detailed user information |
| qlik_search_usersC | Search for users by name or email |
| qlik_health_checkB | Check server status and service health including governance capabilities |
| qlik_get_license_infoB | Get license information including type, allocated seats, and usage. Works on both Cloud and On-Premise (QRS license endpoint). |
| qlik_apply_selectionsC | Apply selections/filters to a Qlik app |
| qlik_clear_selectionsB | Clear all selections in an app |
| qlik_get_current_selectionsC | Get current selections in an app |
| qlik_get_available_fieldsC | Get all fields in an app |
| qlik_generate_appA | Create or update a Qlik Sense app with load script and data connections. Cloud workflow:
On-Premise workflow (Engine API):
On-Premise Data Connections:
On-Premise Discovery (no appName/appId needed):
Cloud Load Script - File from Space: IMPORTANT: Use format [lib://:DataFiles/]
On-Premise Load Script Examples:
Returns: appId, appName, appLink, reloadStatus, connections, odbcDsns |
| qlik_insight_advisorA | Ask natural language questions about Qlik data using Insight Advisor. Flow (no Claude API key needed): Option A - With appId (recommended, works on all tenants):
Option B - Auto app detection (requires Qlik Answers enabled):
Example: Step 1: { "text": "show sales", "appId": "abc123" } → Returns model with fields like "Revenue", "Sales Region" Step 2: { "appId": "abc123", "refinedQuestion": "show Revenue by Sales Region" } → Returns actual data and visualizations If you get 405 error: Use qlik_search_apps first to find the app ID. |
| qlik_get_reload_infoC | Get app reload history and status |
| qlik_get_lineageA | Get lineage information for a dataset or resource. REQUIRES QRI from dataset.rawDataset.secureQri IMPORTANT: The nodeId must be a QRI (Qlik Resource Identifier), not a regular ID.
|
| qlik_get_dataset_detailsC | Get detailed information about a dataset from the data catalog. |
| qlik_answers_list_assistantsB | List Qlik Answers AI assistants |
| qlik_answers_get_assistantC | Get details of a specific assistant |
| qlik_answers_ask_questionA | Ask a question to a Qlik Answers AI assistant. What is Qlik Answers?
When to use this tool:
Workflow:
Parameters:
|
| qlik_alert_listA | List all Qlik Cloud data alerts with optional filtering. Cloud-only feature - Not available for on-premise deployments. Supports filtering and pagination:
Returns:
Example: { "enabled": true, "limit": 20, "spaceId": "space-id-here" } |
| qlik_alert_getA | Get detailed information about a specific Qlik Cloud data alert. Cloud-only feature - Not available for on-premise deployments. Parameters:
Returns:
Example: { "alertId": "alert-id-here" } |
| qlik_alert_triggerA | Manually trigger a Qlik Cloud data alert. Cloud-only feature - Not available for on-premise deployments. Forces immediate execution of the alert to check conditions and send notifications if triggered. Parameters:
Returns:
Example: { "alertId": "alert-id-here" } |
| qlik_alert_deleteA | Delete a Qlik Cloud data alert. Cloud-only feature - Not available for on-premise deployments. Parameters:
Example: { "alertId": "alert-id-here" } |
| qlik_automl_get_experimentsC | List AutoML experiments |
| qlik_automl_get_experimentC | Get experiment details |
| qlik_automl_list_deploymentsC | List all ML deployments |
| qlik_automl_get_deploymentC | Get deployment details |
| qlik_automation_listA | List all automations that the user has access to. Supports filtering, sorting, and pagination:
Returns:
|
| qlik_automation_get_detailsA | Get full details of a specific automation including its workflow definition. Parameters:
Returns:
|
| qlik_automation_runB | Execute an automation (queue a new run). Parameters:
Returns:
Note: The automation must be enabled before it can be run. |
| qlik_automation_list_runsA | List all runs (executions) for a specific automation. Supports filtering and sorting:
Returns:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 34 tools
Most tools are clearly distinct with specific resource-action pairs, such as qlik_alert_delete vs. qlik_alert_get. However, some overlap exists in search and data retrieval tools (e.g., qlik_search and qlik_get_spaces_catalog both help find resources), which could cause minor confusion. The descriptions generally help clarify boundaries, but the high tool count increases the risk of misselection.
All tool names follow a consistent snake_case pattern with a clear 'qlik_' prefix and verb_noun structure, such as qlik_alert_delete, qlik_automation_run, and qlik_get_license_info. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions across the 34 tools.
With 34 tools, the set feels overly heavy for a single server, bordering on excessive. While Qlik's domain is broad (alerts, automations, apps, searches, etc.), the count suggests fragmentation rather than a well-scoped surface. A more focused grouping into subdomains or fewer, more versatile tools would improve coherence.
The tool set provides comprehensive coverage for Qlik Cloud and on-premise operations, including CRUD for alerts, automations, and data interactions, plus utilities like search and health checks. Minor gaps exist, such as missing update tools for some resources (e.g., alerts only have delete/get/list/trigger), but agents can work around these with the available tools.