Open-source MCP server for Qlik Sense Enterprise on Windows (client-managed) — agents that troubleshoot the estate
Years ago I wrote the QlikView Systems Monitor (ugly but one of the most downloaded apps of its era). This is the same itch, scratched with 2026 tools.
Qlik Cloud has a native MCP endpoint for AI agents. Client-managed Qlik Sense on Windows has no official equivalent, so at Terenzi LLC we built one and open-sourced it under Apache-2.0. qseow-mcp exposes the QRS, Engine, and Proxy APIs as 44 agent tools across analyst, troubleshooting, developer, and admin personas. There is other community work in this space, and more of it is a good thing; our focus is the support and troubleshooting surface, full JWT-mode coverage, and a hard security posture.
The part we care most about is the troubleshooting loop. When a number is wrong, an agent can walk KPI to object to sheet to app to script to source, evaluating the governed definition at every step. In our demo estate it traces a $50M reconciliation mismatch to a double-loaded batch and ties it back out in seconds of tool time.
Two practical notes for anyone who tries it:
Published-app caveat: the engine hides a published app's script and lineage from user identities (GetScript returns empty, GetLineage denies, even for RootAdmin under a user identity). The workaround is copy_app and trace the owned copy. This is documented platform behavior, not a bug in the server, and it will bite any agent integration you build yourself.
The engine validates expressions but never proves pixels. A hypercube the engine accepts can still render a blank chart client-side (nebula.js default property blocks). The server ships a validate_sheet gate and all 12 supported chart types are render-verified against a real browser.
Read-only by default, mutating tools gated at registration, credential redaction on every output path, certificate and JWT auth both covered. Independent project by Terenzi LLC (we are a Qlik partner; this is not a Qlik product). Issues and PRs welcome, especially reports from multi-node sites — everything so far is validated on single-node May 2026.
