Sign in to Qlik Cloud as yourself, in your browser.

Opens your browser so you can authorize this server as your own Qlik Cloud account. Qlik shows an "authorize this application" consent screen the first time for an account - approve it. Everything this server does afterwards uses your identity and your permissions.

Call this when a tool says you are not signed in, or when the user asks to sign in or switch accounts. Do not call it speculatively: it opens a browser window.

Args: force: Sign in again even if a session already exists. switch_account: Ask Qlik to re-authenticate instead of reusing whatever account the browser is already signed in as. Use this when the user wants to sign in as somebody else; it implies force.

Sign out of Qlik Cloud and remove the stored session.

Revokes this server's token with the tenant and deletes the locally stored session. The next call will need qlikcloud_login again. This server holds no credential of its own and no permissions beyond the signed-in user's, so signing out removes its access to Qlik Cloud entirely.

Args: all_accounts: Also remove every other stored account for this tenant.

Check the connection, and report which Qlik Cloud account is in use.

Run this first when anything looks wrong. Reports the tenant, the signed-in identity and its roles, where the session is stored, and when the access token refreshes. Everything runs with that user's own permissions; a non-admin identity with few roles is normal and not a fault, because this server deliberately holds no elevated access.

Read anything from Qlik Cloud over REST: the only read tool in this server.

This is how you fetch an app's data model and field metadata, its load script and lineage, glossary terms and definitions, spaces, users, items, datasets, data products, reloads and audits — any GET endpoint on qlik.dev. Reach for it whenever you need to look something up, list, search, count or profile.

Named so a client that loads tool schemas on demand can find it: this tool is the retrieval, read, fetch, list, search, describe and inspect capability. If it is not in your visible tool list it is deferred, not absent — call it by name.

Runs as the signed-in Qlik Cloud user, with exactly their permissions. Results are already filtered to what that user can see, so a short list is their view, not an error.

Use this only when no tool in the official Qlik MCP Server covers the operation. Prefer Qlik MCP tools for analytics operations such as opening apps, searching fields, listing sheets, or reading app content.

Qlik list endpoints return one page at a time. Set fetch_all=True when the user asks for all of something (all spaces, all users, every app in a space) or asks for a count. Leave it off for lookups and single-record reads. When a cap is reached the result says so via "truncated" and "truncatedReason" — do not present a truncated list as complete.

Args: path: API path, e.g. /api/v1/spaces. See https://qlik.dev/apis/rest/. The older qlik-cli form (v1/spaces) is also accepted. query_params: Optional query string, e.g. "limit=10&type=shared" fetch_all: Follow pagination links and merge every page. max_pages: Maximum pages to fetch when fetch_all is set (ceiling 100).

Delete a Qlik Cloud resource, with governance rules enforced.

Runs as the signed-in Qlik Cloud user, with exactly their permissions: you can only retire resources you are allowed to move, and you must be able to see the Recycle Bin space. Retiring someone else's app is an admin action, performed by an admin being the one signed in.

Supported resources and their governance behaviour:

• Apps (/api/v1/apps/...): moved to the Recycle Bin shared space, never hard-deleted.

• Automations (/api/v1/automations/...): moved to the Recycle Bin shared space.

• Data files (/api/v1/data-files/...): moved to the Recycle Bin shared space.

• Spaces (/api/v1/spaces/...): blocked. Must be deleted manually in the Qlik Cloud Management Console.

• All other resource types: not supported by this tool.

Nothing can be deleted permanently through this server. Anything already in the Recycle Bin is refused outright — for every user, tenant admins included. Emptying the Recycle Bin is done by hand in the Qlik Cloud Activity Center in the hub. Do not look for another route: there is none, and offering one would be wrong.

IMPORTANT: Before calling this tool, tell the user exactly what will be deleted and wait for explicit confirmation.

Args: path: API path, e.g. /api/v1/automations/abc123

Send a message to a Qlik Answers assistant and get a response.

Runs as the signed-in Qlik Cloud user, with exactly their permissions: the assistant answers from the knowledge bases that user can access.

Maintains conversation context across calls by reusing the same thread. On the first call, omit thread_id and a new thread is created automatically. Pass the returned thread_id on subsequent calls to continue the conversation.

Args: assistant_id: ID of the assistant to query (use qlikcloud_get with path /api/v1/assistants to list them) message: The question or message to send thread_id: Optional thread ID from a previous call to continue the conversation