Connect your AI to Qlik Sense — without losing data governance.
An MCP server that lets Claude, ChatGPT and your agents ask Qlik in plain language — read-only, governed by each user's identity and by Section Access, running as a Windows service in your own infrastructure.
Try it 7 days free, no card.
Your teams want to ask the AI. Your data lives in Qlik.
Wiring a model straight into Qlik with no control is a risk: fuzzy identity, too much data, no audit trail. The connector closes that gap without opening your platform wide.
- Exposing Qlik to a model with no identity governance
- Integrations that see more data than they should
- No trace of who queried what, and when
- Admin credentials shared across users
- Fear of breaking Section Access or security rules
- Wanting AI over your BI, unsure how to start safely
The connector lives next to Qlik, in your trusted zone.
The AI client speaks MCP to the connector; the connector resolves the user's real identity and opens the Qlik session as that person. Qlik reduces the data. Nothing bypasses governance.
- The MCP client connects over Streamable HTTP (OAuth 2.1 or API key).
- The connector verifies identity and maps it to a Qlik user.
- It opens the QIX session as that user; Qlik applies Section Access.
- It returns governed data, with limits and audit.
Built for security, governance and real operation.
Not a script: an installable product, with identity, licensing, admin panel and audit.
Real identity, end to end
Every query opens the Qlik session as the real user. Qlik applies Section Access, security rules and the apps that person can see. The connector never picks identity from a model parameter — only from the verified credential.
Read-only and governed
Reads only already-modeled content (hypercubes from existing objects and master items), never raw QVDs or databases. Hard limits on rows, cells and payload. Write tools are off by default.
Turnkey install
An MSI orchestrator sets everything up on the Qlik server: full-auto certificates, JWT virtual proxy, firewall rule, Windows service and a secure .env. No manual certificate export.
Flexible authentication
OAuth federated to Qlik (the connector is its own Authorization Server, no external IdP), OAuth against your IdP, or API keys. Identity always comes from the credential, never the prompt.
Runs in your infrastructure
Self-contained executable (Node SEA) as a Windows service, in the same trusted zone as Qlik. Use it over the internal LAN or publish it to the internet with strict TLS against Qlik's CA.
Local admin panel
Web screen (127.0.0.1 + login only) to see service, port and license status, configure auth and limits, manage authorized users and load the license. Also available via CLI.
Context memories
Three levels, general to specific: connector methods, the Qlik environment of your install, and per-user memory. The agent reads context before querying, to answer with business sense.
Audit and limits
Every MCP call logged (app, tool, user, Qlik identity and timestamp). Allowlist of apps, streams and tasks. Metadata-only by default.
MCP tools, all read-only and governed.
Inventory of apps and already-modeled data — without touching raw sources. Plus resources (qlik://apps) and ready prompts like qlik_resumir_app and qlik_diagnosticar_recargas.
Inventory
qlik_list_appsList apps visible to the userqlik_get_appApp detail and sheetsqlik_list_reload_tasksReload tasksqlik_start_reload_taskTrigger reload (gated)qlik_pingCheck the Qlik connectionData layer
qlik_get_app_metadataData model metadataqlik_list_app_objectsObjects, charts and tablesqlik_get_object_dataData from an existing objectqlik_evaluate_measureEvaluate a measureqlik_master_itemsMaster dimensions and measuresqlik_apply_selectionsApply selectionsqlik_get_current_selectionsView current selectionsqlik_clear_selectionsClear selectionsLeast privilege, real identity, everything audited.
The data response depends on the verified user, never on a global admin account or a model parameter. That's how impersonation is prevented.
- Qlik identity tied to the end user (OAuth/OIDC, Ticket API or header behind a trusted proxy).
- Writes off by default; every action behind a gate, allowlist and audit.
- Strict TLS against Qlik's CA; secrets and certificates kept out of logs.
- Admin panel on 127.0.0.1 with login only: a second layer over loopback.
Your license, under your control
- Perpetual: Ed25519 signature locked to the machine, validated offline at each start.
- 7-day trial: signed against our license server, clock-proof.
- Subscription: activation and revocation via signed heartbeat.
Fail-closed gate: if the license isn't valid, the connector won't start.
What you need to get going.
One license per server. Choose how to pay for it.
Prices in US dollars (USD), tax excluded. Pay by card through a secure checkout. Start with 7 days free, no card.
Perpetual license
one-time, per server
To own it for good. Offline validation, ideal for environments with no internet access or air-gapped.
- Perpetual use, no expiration
- Offline validation (locked to the machine)
- Full connector: governed read-only, all auth modes, admin panel and MSI installer
- No external dependency to start
Monthly subscription
per server
To start light and scale. Activation and control via signed heartbeat.
- Cancel anytime
- Continuous updates included
- Same full connector
- Great for pilots and gradual growth
Multiple servers or special needs? Let's talk volume
What people usually ask.
Does it work with Qlik Cloud or QlikView?
This version is specific to Qlik Sense Enterprise on Windows (QSEoW). It installs on the Qlik server itself and talks to QRS and the Engine locally. Using Qlik Cloud or QlikView? Write to us and we'll take a look.
Does my data leave my server?
No. The connector runs inside your trusted zone, next to Qlik. The AI client only receives content that user could already see in Qlik, with row and payload limits. Qlik does the data reduction via Section Access.
Does it respect Section Access and each user's permissions?
Yes. Every query opens the session as the real user, so Qlik applies Section Access, security rules and app/object visibility. The connector doesn't filter on its own: it asks, Qlik reduces.
Can it modify or write to Qlik?
Read-only by default. Tools that change state (such as triggering a reload) sit behind an explicit gate, with allowlist and audit.
Does it need an internet connection?
The perpetual license validates offline and needs no internet to start. Trial and subscription use a signed heartbeat against our license server for activation and control.
What does 'per server' mean?
Each license is locked to the fingerprint of the machine running the connector (a combination of hardware identifiers). If you have several Qlik servers, you need one license per server. For volume, let's talk.
Which AI clients are supported?
Any MCP-compatible client over Streamable HTTP: Claude Desktop, ChatGPT, MCP-enabled IDEs and your own agents.
How is it installed?
With an MSI installer that provisions everything (certificates, JWT virtual proxy, firewall, Windows service and secure config) and leaves a shortcut to the admin panel. There's a deployment guide for LAN or internet.
How do I pay?
By credit card, through a secure checkout. The perpetual license is a one-time payment; the subscription is monthly and you can cancel anytime.
Ready for your AI to talk to Qlik?
Install it on your server in minutes and try it 7 days free. When you're ready, buy or subscribe by card.