World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Agent tools for Qlik Sense Enterprise on Windows: troubleshoot, govern, query and build.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 11/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 14/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Qseow MCP. Follow https://mcp.popnx.com/i/rmterenzi-qseow-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qseow MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "qseow": { "command": "npx", "args": [ "-y", "qseow-mcp" ], "env": { "QSEOW_HOST": "your-value", "QSEOW_CERT_PATH": "your-value", "QSEOW_JWT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For QSEOW_JWT, QSEOW_HOST, QSEOW_CERT_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Qseow MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
QSEOW_HOST Hostname of the Qlik Sense node, no scheme (e.g. sense.example.com).QSEOW_CERT_PATH Path to the QMC-exported client certificate (PEM). Required in certificate mode; also enables the Proxy-API session tools in jwt mode.Descriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"qseow": {
"command": "npx",
"args": [
"-y",
"qseow-mcp"
],
"env": {
"QSEOW_HOST": "your-value",
"QSEOW_CERT_PATH": "your-value",
"QSEOW_JWT": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Qseow MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Qseow MCP or shows a Qseow MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
QSEOW_AUTH_MODE 'certificate' (service identity via QMC-exported certs) or 'jwt' (per-user, through a JWT virtual proxy). Defaults to certificate.QSEOW_CERT_KEY_PATH Path to the client certificate private key (PEM).QSEOW_ROOT_CERT_PATH Path to the Qlik root CA (PEM). Supply it to keep TLS verification on.QSEOW_VP_PREFIX Virtual proxy prefix for jwt mode, e.g. 'jwt'. · default jwtQSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default falseQSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,adminQSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default trueDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Qseow MCP yet
Qseow MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Qseow MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Qseow MCP key (create it on the maker’s site) · 2 setting(s) to fill in (QSEOW_HOST, QSEOW_CERT_PATH) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qseow MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user qseow --env QSEOW_HOST=your-value --env QSEOW_CERT_PATH=your-value --env QSEOW_JWT=your-value -- npx -y qseow-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For QSEOW_JWT, QSEOW_HOST, QSEOW_CERT_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Qseow MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
QSEOW_HOST Hostname of the Qlik Sense node, no scheme (e.g. sense.example.com).QSEOW_CERT_PATH Path to the QMC-exported client certificate (PEM). Required in certificate mode; also enables the Proxy-API session tools in jwt mode.Descriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user qseow --env QSEOW_HOST=your-value --env QSEOW_CERT_PATH=your-value --env QSEOW_JWT=your-value -- npx -y qseow-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Qseow MCP listed as connected
Use Qseow MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Qseow MCP or shows a Qseow MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
QSEOW_AUTH_MODE 'certificate' (service identity via QMC-exported certs) or 'jwt' (per-user, through a JWT virtual proxy). Defaults to certificate.QSEOW_CERT_KEY_PATH Path to the client certificate private key (PEM).QSEOW_ROOT_CERT_PATH Path to the Qlik root CA (PEM). Supply it to keep TLS verification on.QSEOW_VP_PREFIX Virtual proxy prefix for jwt mode, e.g. 'jwt'. · default jwtQSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default falseQSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,adminQSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default trueDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Qseow MCP key (create it on the maker’s site) · 2 setting(s) to fill in (QSEOW_HOST, QSEOW_CERT_PATH) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qseow MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "qseow": { "command": "npx", "args": [ "-y", "qseow-mcp" ], "env": { "QSEOW_HOST": "your-value", "QSEOW_CERT_PATH": "your-value", "QSEOW_JWT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For QSEOW_JWT, QSEOW_HOST, QSEOW_CERT_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Qseow MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
QSEOW_HOST Hostname of the Qlik Sense node, no scheme (e.g. sense.example.com).QSEOW_CERT_PATH Path to the QMC-exported client certificate (PEM). Required in certificate mode; also enables the Proxy-API session tools in jwt mode.Descriptions are as written by the maker.
In the Qseow MCP settings, QSEOW_JWT, QSEOW_HOST, QSEOW_CERT_PATH is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Qseow MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Qseow MCP or shows a Qseow MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
QSEOW_AUTH_MODE 'certificate' (service identity via QMC-exported certs) or 'jwt' (per-user, through a JWT virtual proxy). Defaults to certificate.QSEOW_CERT_KEY_PATH Path to the client certificate private key (PEM).QSEOW_ROOT_CERT_PATH Path to the Qlik root CA (PEM). Supply it to keep TLS verification on.QSEOW_VP_PREFIX Virtual proxy prefix for jwt mode, e.g. 'jwt'. · default jwtQSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default falseQSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,adminQSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default trueDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Qseow MCP key (create it on the maker’s site) · 2 setting(s) to fill in (QSEOW_HOST, QSEOW_CERT_PATH) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qseow MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "qseow": { "type": "stdio", "command": "npx", "args": [ "-y", "qseow-mcp" ], "env": { "QSEOW_HOST": "your-value", "QSEOW_CERT_PATH": "your-value", "QSEOW_JWT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For QSEOW_JWT, QSEOW_HOST, QSEOW_CERT_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Qseow MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
QSEOW_HOST Hostname of the Qlik Sense node, no scheme (e.g. sense.example.com).QSEOW_CERT_PATH Path to the QMC-exported client certificate (PEM). Required in certificate mode; also enables the Proxy-API session tools in jwt mode.Descriptions are as written by the maker.
In the Qseow MCP settings, QSEOW_JWT, QSEOW_HOST, QSEOW_CERT_PATH is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Qseow MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Qseow MCP or shows a Qseow MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
QSEOW_AUTH_MODE 'certificate' (service identity via QMC-exported certs) or 'jwt' (per-user, through a JWT virtual proxy). Defaults to certificate.QSEOW_CERT_KEY_PATH Path to the client certificate private key (PEM).QSEOW_ROOT_CERT_PATH Path to the Qlik root CA (PEM). Supply it to keep TLS verification on.QSEOW_VP_PREFIX Virtual proxy prefix for jwt mode, e.g. 'jwt'. · default jwtQSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default falseQSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,adminQSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default trueDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user qseow --env QSEOW_HOST=your-value --env QSEOW_CERT_PATH=your-value --env QSEOW_JWT=your-value -- npx -y qseow-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"qseow": {
"command": "npx",
"args": [
"-y",
"qseow-mcp"
],
"env": {
"QSEOW_HOST": "your-value",
"QSEOW_CERT_PATH": "your-value",
"QSEOW_JWT": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"qseow": {
"command": "npx",
"args": [
"-y",
"qseow-mcp"
],
"env": {
"QSEOW_HOST": "your-value",
"QSEOW_CERT_PATH": "your-value",
"QSEOW_JWT": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"qseow": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"qseow-mcp"
],
"env": {
"QSEOW_HOST": "your-value",
"QSEOW_CERT_PATH": "your-value",
"QSEOW_JWT": "your-value"
}
}
}
}QSEOW_HOST required envQSEOW_AUTH_MODE secret envQSEOW_CERT_PATH required envQSEOW_CERT_KEY_PATH envQSEOW_ROOT_CERT_PATH envQSEOW_JWT secret required envQSEOW_VP_PREFIX envQSEOW_ALLOW_MUTATIONS envQSEOW_TOOL_GROUPS envQSEOW_TLS_VERIFY envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account rmterenzi, which owns the repo
Code last changed 3 months ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for qseow-mcp@0.5.2
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/rmterenzi-qseow-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: QSEOW_JWT
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 months ago, and the latest version (0.5.2) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Qseow MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server for Qlik Sense Enterprise on Windows (client-managed).
The glue layer for a Qlik support agent. Qlik Cloud ships a native MCP endpoint; the client-managed estate — where a large share of enterprise Qlik still runs — has nothing equivalent. This server exposes the on-prem API surface (Repository/QRS, Engine/QIX, Proxy) as Model Context Protocol tools, so an agent can do what a support engineer does when a number is wrong: walk KPI → object → sheet → app → script → source, evaluating definitions at every step — plus govern, query, and build against the site.
Status: 0.5.2, pre-release. All 44 tools exercised end-to-end against Qlik Sense May 2026 (15.13.8) on a single-node site, in BOTH certificate and JWT auth modes (including the full mutation lifecycle: copy → set_script → reload → publish → delete, and task start-to-finish). Tool names and shapes may still change.
qseow-mcp is an independent open-source project by Terenzi LLC. It is not affiliated with, endorsed by, or sponsored by QlikTech International AB. Qlik®, Qlik Sense®, and related marks are trademarks of QlikTech International AB, used here only to identify the software this server interoperates with.
Claude Desktop — one-click. Download qseow-mcp- .mcpb from the latest release and double-click it. Claude Desktop prompts for your hostname and certificate paths; there is no JSON to edit and no npm install to run.
Any MCP client — via npx. No clone, no build:
{
"mcpServers": { "qseow": { "command": "npx", "args": ["-y", "qseow-mcp"], "env": { "QSEOW_HOST": "sense.example.com", "QSEOW_CERT_PATH": "/absolute/path/to/client.pem", "QSEOW_CERT_KEY_PATH": "/absolute/path/to/client_key.pem", "QSEOW_ROOT_CERT_PATH": "/absolute/path/to/root.pem" } } } }
Claude Code, same thing in one line:
claude mcp add qseow --scope user \
-e QSEOW_HOST=sense.example.com \ -e QSEOW_CERT_PATH=/absolute/path/to/client.pem \ -e QSEOW_CERT_KEY_PATH=/absolute/path/to/client_key.pem \ -- npx -y qseow-mcp
Certificates come from QMC → Certificates → Export (choose PEM). For JWT instead of certificates, see Authentication.
It starts read-only. Mutating tools are not registered at all until you set QSEOW_ALLOW_MUTATIONS=true, so the tool list a client sees is genuinely read-only until you decide otherwise.
Expose only what a given deployment needs with QSEOW_TOOL_GROUPS.
Analyst — ask questions of data (Engine/QIX)
| Tool | Purpose |
|---|---|
list_engine_apps | Apps visible to the session |
get_app_data_model | Tables, fields, row counts, cardinality |
evaluate_expression | Evaluate a Qlik expression in the current selection state |
create_hypercube | Group-by query: dimensions × measures → rows |
get_field_values | Distinct values with selection state, optional search |
select_field_values / clear_selections / get_current_selections | Drive and inspect selection state |
crosscheck_expression | Adversarial self-check: total vs sum-of-groups — flags non-additive measures and scoping bugs before a number reaches a user |
Every value-returning analytics tool ships a trust envelope: expression validation warnings (a misspelled field returns null/0 *without erroring* — the engine's worst habit) and the active selections the value was computed under, so a filtered number can never masquerade as the unfiltered truth.
Inspector — the troubleshooting loop (ships with the analyst group)
| Tool | Purpose |
|---|---|
list_sheets / get_sheet_objects | Walk the UI layer: sheets and the objects on them |
get_object_properties | Full qProps of any object — the definition layer |
search_expressions | Find a field, KPI, or expression fragment across ALL objects (with owning sheet), master items, variables, and the script |
list_master_measures / list_master_dimensions | The governed definition inventory |
evaluate_master_measure | Evaluate a master measure by id or title (sidesteps the [Name]-resolves-to-a-field trap) |
get_app_lineage | Every LOAD/STORE source and target, classified (qvd, database, inline, resident, store) |
Published-app caveat: the engine hides a published app's *script* and *lineage* from user identities (internal certificate identities bypass this). The support-agent pattern is copy_app → trace the owned copy — the copy carries the same script and definitions.
Developer — build and ship apps (Engine + QRS)
| Tool | Purpose |
|---|---|
create_sheet / add_sheet_object | Build the UI layer: sheets and visualizations. Creation runs the render-validation gate and returns its verdict |
validate_sheet | Quality gate (read-only): will these objects actually render? Definition errors, unknown fields/types, empty cubes, pivot qMode traps, missing nebula property blocks, cell-placement lint |
get_script / set_script | Read and replace an app's load script |
check_script | Syntax-check without reloading |
reload_app | Reload and save, returns progress tail |
create_app | Create app, optionally set script and reload |
copy_app / publish_app / delete_app | Duplicate; publish to a stream; delete |
Admin — govern the site (QRS)
| Tool | Purpose |
|---|---|
qrs_about / service_status | Version; health of every service on every node |
license_summary | Serial, edition, expiry, professional/analyzer allocations |
list_apps / list_streams / list_tasks / list_users | Inventory, all filterable |
start_task | Trigger a reload task |
list_extensions / list_data_connections | Extension and connection inventory |
qrs_search | Any QRS entity + filter expression — the governance power tool |
get_reload_log | Why did a reload fail? Last execution result + detail timeline + script-log tail |
engine_healthcheck | Engine version, saturated flag, memory/CPU, loaded apps, session counts |
security_rule_audit | Every security rule with decoded actions + lint findings (disabled defaults, wildcard filters, unconditional write grants) |
list_user_sessions / end_user_sessions | Active proxy sessions per user; force logout. Certificate-backed — see note below |
Mutating tools (set_script, reload_app, create_app, copy_app, publish_app, delete_app, start_task, end_user_sessions, create_sheet, add_sheet_object) are gated at registration: unless QSEOW_ALLOW_MUTATIONS=true, they are never registered, so a read-only deployment advertises a genuinely read-only tool surface in tools/list. Default is read-only.
Every tool carries MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) so clients that honor them can apply their own policy — e.g. reload_app/set_script/start_task are flagged destructive; selection tools are non-destructive session-state mutations.
Credential redaction applies to every QRS egress path: list_data_connections and generic qrs_search (any entity type, condensed or full:true) recursively mask credential-bearing fields (password, passphrase, clientsecret, ...) and secrets embedded in connection strings (PWD=..., apikey=...). Empty/null credential fields pass through unmasked — "no credential present" is a legitimate signal.
All list tools are paged (offset/limit, envelope {total, offset, returned, truncated, items}) so a site with thousands of apps or users cannot blow the client's context window.
Modern Sense visualizations are nebula.js supernovas rendered by the client, not the engine — a hypercube the engine accepts and evaluates perfectly still renders blank if the supernova's default property blocks are missing (it throws Cannot read properties of undefined in the browser; the engine never knows). The builder ships those blocks per type, and validate_sheet flags objects that lack them.
Because engine-side validation cannot prove pixels, two scripts close the loop: scripts/viz_matrix.mjs builds one of every supported type against a live site, and scripts/render_proof.mjs drives a real headless browser over the result at sheet-tile sizes and reports what actually drew.
All 12 supported types are render-verified on Qlik Sense May 2026, at sheet-tile sizes, in a real browser client: kpi, gauge, barchart, linechart, combochart, piechart, scatterplot, treemap, table, pivot-table, listbox, text-image.
When a supernova refuses to draw, do not reverse-engineer its properties from error messages — some charts throw nothing useful. Instead ask the client what it writes:
node scripts/harvest_client_props.mjs treemap ./truth.json
This scans every readable app for client-authored objects of that type and dumps their properties. Qlik's shipped monitoring apps (Content / Operations / License Monitor) are a good source. This is how the last two broken types were fixed, each in a single pass after repeated guesswork had failed:
qMode: "K" (tree mode — the same class of trap as pivot-table needing "P") plus a far leaner property set than the generic builder produced. Harvested from Qlik's shipped Content Monitor app.gaugetype, angle, autoOrientation, paletteProgressColor and segmentInfo — properties no error message ever named, because gauge fails silently. Harvested from a gauge authored in the Sense client for the purpose.If a chart you build renders blank or errors, author one in the client, harvest it, and mirror it. That loop is minutes; reverse-engineering from crash messages is hours and does not terminate when the chart fails quietly.
Three methodology notes worth stealing if you build something similar:
render_proof.mjs with SHOTS= and look at the images.Two modes, both standard QSEoW patterns. Header-authentication virtual proxies are deliberately not supported: any client that can reach the proxy can assert any identity, which is not a footing to build an agent tool on.
`certificate` — QMC-exported client certificates against QRS :4242 and Engine :4747. The service-to-service path; full tool coverage. Export via QMC, or POST /qrs/certificatedistribution/exportcertificates.
`jwt` — a signed, expiring token through a JWT virtual proxy on :443. Carries a real per-user identity, so it's the right mode when the agent should act as a person and inherit that person's section-access and security rules.
One platform exception: the Proxy Service REST API (:4243, behind list_user_sessions/end_user_sessions) only speaks certificate auth — Qlik exposes no JWT route to it. Those two tools register whenever certificate material is configured (QSEOW_CERT_PATH/QSEOW_CERT_KEY_PATH), in either auth mode, and are absent from tools/list otherwise. Every other tool has identical coverage in both modes.
Both modes have full tool coverage apart from the two certificate-only QPS session tools noted