QOps 3.1.0

October 2026

QOps and your AI assistant: the QOps MCP server

QOps now includes an MCP server, so an AI assistant can work with your QOps repositories and Qlik applications in plain language. It runs on your own machine, uses the connection profiles and licence you already have, and never passes your Qlik credentials to the assistant.

  • Chat in the Portal. A Chat panel, opened from the Dashboard or docked beside the editor in Studio, talks to Claude or Gemini with the QOps tools and nothing to connect. Under Settings → Global → Chat you pick the provider and model and store your own API token, encrypted on this machine. Prompt caching is on by default, so long chats use fewer full-price tokens, and Show token usage adds a line with the tokens each answer used. The provider and model can also be changed for the chat you are in, from the provider's own model list.
  • Your own assistant. Claude Desktop, Claude Code, Cursor and other MCP clients connect through a launcher that QOps-StartPortal writes to a fixed place, so the connection keeps working across updates.
  • QOps operations. The assistant reads your repositories (apps, objects, lineage, load scripts) and runs Prepare, Build, Publish and Reload in a repository folder, exactly as the commands do.
  • Qlik objects. It creates and changes sheets, charts, master items, variables and load scripts in a live application, with a read-only mode, a preview before a change, and one save for several changes. After each write it reads the result back and reports a broken expression, a chart that cannot draw, or a change that was not stored as sent. Charts cover bar, line, combo, pie, table, KPI, scatter, gauge, treemap and pivot table. A catalogue of chart settings lets it change legends, labels, axes, sorting, colours, combo series and donut or area styles exactly as Qlik does when you change them yourself. On Qlik Cloud it can make a sheet public with publish_sheet.
  • The MCP-QOps licence. An MCP-QOps licence includes all of QOps and adds the analytic tools, which return the data in an application: values, calculated expressions and selections. With a QOps licence every other tool works and data values are left out. Settings → Global → License shows the licence tier. A tool call takes a licence slot only while it runs, so QOps commands can run while the assistant keeps an application open.

Git panel: remote branches, fetch and a 3-way merge editor

The Branches card lists the branches of every remote. You can merge a remote branch into the current one without switching, check one out as a tracking branch, and Fetch to see how far each branch is behind. A conflicted file opens in a 3-way merge editor, with Current and Incoming side by side and an editable Result, a choice to accept either side or both for each conflict, and Save marking the file resolved and staged once no conflict is left.

Release notes and updates from the Versions panel

The Versions panel, opened from the version badge, opens these notes at your installed version, runs QOps-Update after you confirm, and restarts the Portal on the new version at the same address. It shows the date and hour each Portal was built. QOps-Update can use your own GitHub token to stay clear of GitHub's shared request limit, set with QOps-SetConfig -GitHubToken or in the Portal. QOps-SetVersion -RestartPortal restarts a running Portal on the version you switch to, and the Portal shortcut starts the version QOps last settled on.

Building into new and existing applications

A folder with no Id is built into a new application, and the folder records it, so the next build updates that application. QOps-Build -UpdateOnly builds only into applications that already exist on the server you are connected to and never creates one, which is the safe first build after a fresh clone. In the Portal it is Update only on Build.

How-to guides in Help

The Help panel has How-to Guides: pages written around a task, such as connecting a fresh clone to existing applications or setting the applications up on another environment, each with the commands in order, how to check the result, and what to do when it did not work.

QOps-Reload saves the task log to a file

On Qlik Sense, QOps-Reload -LogPath writes the full log of each task's last run to a file, and the Portal's Reload status can download it.

App files are written with only the Space key by default

A repository without a StreamSerialization setting now writes only the Space key into its app files. Set StreamSerialization: Both to keep writing the older Stream key as well. Reading is unchanged.

Fixes

  • QOps-Release on Qlik Cloud publishes every sheet marked Published: true.
  • QOps-Build on Qlik Sense saves again when the Engine reloads the application during the save.
  • Uploads that Qlik Sense refuses because too many arrive at once are sent again.
  • Publishing to a Qlik Cloud managed space keeps the application's description, and -Sort Space works on Qlik Cloud.
  • Setting a new licence key works when a previous key is still activated, and on machines where the Windows user name differs from the profile folder name.
  • QOps runs under PowerShell 7.4, and installing over an older version completes when the Portal was not stopped cleanly.

Work on the Portal and the MCP server continues, and more will come in the next releases.