Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Qseow MCP

by rmterenziversion 0.5.2i★ 8iRuns on your computerRepository ↗
Registry nameio.github.rmterenzi/qseow-mcp

How to install

What it does

Agent tools for Qlik Sense Enterprise on Windows: troubleshoot, govern, query and build.

  • Connects Runs on your computer
  • Account or key Needs QSEOW_JWT · 2 settings to fill in (QSEOW_HOST, QSEOW_CERT_PATH)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity11/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness3/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score14/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

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.

Works with Claude, 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) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Sign up and create a Qseow MCP key

    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

  3. Fill in 2 setting(s)

    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.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "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

  6. Quit Claude and open it again

  7. Try it

    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

7 optional setting(s) (works without them)

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 jwt
  • QSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default false
  • QSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,admin
  • QSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default true

Descriptions 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

What you can do instead

A · Use an app that can connect Qseow MCP

  • 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) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • 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)
  • 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)
  • 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)

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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Sign up and create a Qseow MCP key

    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

  3. Fill in 2 setting(s)

    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.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    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

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Qseow MCP listed as connected

  7. Try it

    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

7 optional setting(s) (works without them)

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 jwt
  • QSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default false
  • QSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,admin
  • QSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default true

Descriptions 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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Sign up and create a Qseow MCP key

    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

  3. Fill in 2 setting(s)

    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.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    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

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    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

7 optional setting(s) (works without them)

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 jwt
  • QSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default false
  • QSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,admin
  • QSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default true

Descriptions 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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Sign up and create a Qseow MCP key

    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

  3. Fill in 2 setting(s)

    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.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    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

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    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

7 optional setting(s) (works without them)

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 jwt
  • QSEOW_ALLOW_MUTATIONS Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only. · default false
  • QSEOW_TOOL_GROUPS Comma-separated personas to expose: analyst, developer, admin. · default analyst,developer,admin
  • QSEOW_TLS_VERIFY Set false only for self-signed lab certificates. Leave on in production. · default true

Descriptions 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.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Qseow MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

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-mcp

Claude 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"
      }
    }
  }
}

Values you fill in

  • QSEOW_HOST required env
    Hostname of the Qlik Sense node, no scheme (e.g. sense.example.com).
  • QSEOW_AUTH_MODE secret env
    'certificate' (service identity via QMC-exported certs) or 'jwt' (per-user, through a JWT virtual proxy). Defaults to certificate.
  • QSEOW_CERT_PATH required env
    Path to the QMC-exported client certificate (PEM). Required in certificate mode; also enables the Proxy-API session tools in jwt mode.
  • QSEOW_CERT_KEY_PATH env
    Path to the client certificate private key (PEM).
  • QSEOW_ROOT_CERT_PATH env
    Path to the Qlik root CA (PEM). Supply it to keep TLS verification on.
  • QSEOW_JWT secret required env
    Signed JWT for the virtual proxy (jwt mode only).
  • QSEOW_VP_PREFIX env
    Virtual proxy prefix for jwt mode, e.g. 'jwt'.
  • QSEOW_ALLOW_MUTATIONS env
    Set true to register write tools. Default false: mutating tools are never registered, so the tool list is genuinely read-only.
  • QSEOW_TOOL_GROUPS env
    Comma-separated personas to expose: analyst, developer, admin.
  • QSEOW_TLS_VERIFY env
    Set false only for self-signed lab certificates. Leave on in production.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
62/wk
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
0.5.2
Categoryi
Other
Published to registryi
Aug 12, 2026
Code last changedi
Aug 12, 2026
Maker
rmterenzi
Packages
npm: qseow-mcp
Registry status
Active

Which apps can use it

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

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account rmterenzi, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 months ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for qseow-mcp@0.5.2

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/rmterenzi-qseow-mcp.svg)](https://mcp.popnx.com/en/servers/rmterenzi-qseow-mcp)

Discussion

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.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 96% of the other 20749 servers in this category
  • Published to the registry more recently than 17% of the other 20749 servers in this category
  • Basic checks equal to or better than 99% of the other 20749 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Qseow MCP safe?

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.

What keys or codes does it need?

You need to fill in: QSEOW_JWT

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed 3 months ago, and the latest version (0.5.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Qseow MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseApache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

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.

qseow-mcp

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.

Install

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.

Tools by persona

Expose only what a given deployment needs with QSEOW_TOOL_GROUPS.

Analyst — ask questions of data (Engine/QIX)

ToolPurpose
list_engine_appsApps visible to the session
get_app_data_modelTables, fields, row counts, cardinality
evaluate_expressionEvaluate a Qlik expression in the current selection state
create_hypercubeGroup-by query: dimensions × measures → rows
get_field_valuesDistinct values with selection state, optional search
select_field_values / clear_selections / get_current_selectionsDrive and inspect selection state
crosscheck_expressionAdversarial 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)

ToolPurpose
list_sheets / get_sheet_objectsWalk the UI layer: sheets and the objects on them
get_object_propertiesFull qProps of any object — the definition layer
search_expressionsFind a field, KPI, or expression fragment across ALL objects (with owning sheet), master items, variables, and the script
list_master_measures / list_master_dimensionsThe governed definition inventory
evaluate_master_measureEvaluate a master measure by id or title (sidesteps the [Name]-resolves-to-a-field trap)
get_app_lineageEvery 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)

ToolPurpose
create_sheet / add_sheet_objectBuild the UI layer: sheets and visualizations. Creation runs the render-validation gate and returns its verdict
validate_sheetQuality 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_scriptRead and replace an app's load script
check_scriptSyntax-check without reloading
reload_appReload and save, returns progress tail
create_appCreate app, optionally set script and reload
copy_app / publish_app / delete_appDuplicate; publish to a stream; delete

Admin — govern the site (QRS)

ToolPurpose
qrs_about / service_statusVersion; health of every service on every node
license_summarySerial, edition, expiry, professional/analyzer allocations
list_apps / list_streams / list_tasks / list_usersInventory, all filterable
start_taskTrigger a reload task
list_extensions / list_data_connectionsExtension and connection inventory
qrs_searchAny QRS entity + filter expression — the governance power tool
get_reload_logWhy did a reload fail? Last execution result + detail timeline + script-log tail
engine_healthcheckEngine version, saturated flag, memory/CPU, loaded apps, session counts
security_rule_auditEvery security rule with decoded actions + lint findings (disabled defaults, wildcard filters, unconditional write grants)
list_user_sessions / end_user_sessionsActive 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.

Render verification

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.

Getting a chart's real property contract

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:

  • treemap needed 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.
  • gauge needed 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:

  1. Objects render at sheet-tile size, not full viewport — a chart that paints at 900×620 can refuse in a 640×150 tile.
  2. Counting painted SVG nodes is not proof. A broken chart still draws its legend; that is how an earlier version of this proof reported a false PASS for treemap.
  3. Automated verdicts are advisory; the screenshot is the authority. Qlik draws some error states as SVG text inside a shadow root that neither DOM scraping nor Playwright text locators matched reliably — treemap displayed "This chart cannot be displayed." while every automated probe called it rendered. Run render_proof.mjs with SHOTS= and look at the images.

Authentication

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.

JWT and the engine WebSocket (CSWSH)

Both modes have full tool coverage apart from the two certificate-only QPS session tools noted

Only the beginning is shown; read the rest in the repo