Qseow MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 66 installs a week from npm. Last commit 12 Aug 2026.
Agent tools for Qlik Sense Enterprise on Windows: troubleshoot, govern, query and build.
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const run = (cmd, args, cwd) => execFileSync(cmd, args, { cwd, stdio: "inherit" });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add qseow-mcp -e 'QSEOW_HOST=<QSEOW_HOST>' -- npx -y qseow-mcp
{
"mcpServers": {
"qseow-mcp": {
"command": "npx",
"args": [
"-y",
"qseow-mcp"
],
"env": {
"QSEOW_HOST": "<QSEOW_HOST>"
}
}
}
}
[mcp_servers.qseow-mcp]
command = "npx"
args = ["-y", "qseow-mcp"]
env = { QSEOW_HOST = "<QSEOW_HOST>" }
{
"mcpServers": {
"qseow-mcp": {
"command": "npx",
"args": [
"-y",
"qseow-mcp"
],
"env": {
"QSEOW_HOST": "<QSEOW_HOST>"
}
}
}
}
{
"servers": {
"qseow-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"qseow-mcp"
],
"env": {
"QSEOW_HOST": "<QSEOW_HOST>"
}
}
}
}
Put your own value in place of
<QSEOW_HOST> (Hostname of the Qlik Sense node, no scheme (e.g. sense.example.com)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
QSEOW_AUTH_MODE ('certificate' (service identity via QMC-exported certs) or 'jwt' (per-user, through a JWT virtual proxy). Defaults to certificate), 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), 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_JWT (Signed JWT for the virtual proxy (jwt mode only)), QSEOW_VP_PREFIX (Virtual proxy prefix for jwt mode, e.g. '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), QSEOW_TOOL_GROUPS (Comma-separated personas to expose: analyst, developer, admin), QSEOW_TLS_VERIFY (Set false only for self-signed lab certificates. Leave on in production).
Read-only MCP server for 1C:Enterprise via OData with metadata and query builder tools.
Durable, build-scoped reverse-engineering evidence memory and query tools for AI agents.
One place to build, share, and govern the skills and tools your AI agents use at work.
On-demand tool discovery for all your MCPs and per-subagent MCP controls to preserve context window.
Plonk gives agents local macOS tools for windows, workspaces, screenshots, OCR, and more.
46-tool PowerPoint MCP server. Build, edit, and export .pptx files. Windows-first.
Govern GitHub Enterprise orgs, repos, rulesets, security alerts & Actions for AI agents.
1C Enterprise MCP: 20 real tools to read, check, lint, scaffold, build and run 1C Enterprise code.
Answers built from our own checks of this server.