Set up Qnaat in your Qlik Cloud tenant

Last updated: July 29, 2026

Qnaat connects to your own Qlik Sense Cloud tenant through an OAuth client that your tenant admin registers once. No shared credentials, and nothing sits between the extension and Qlik. Setup has two parts: a one-time step for thetenant admin (about 10 minutes) and a quick connection foreach user (about 2 minutes).

Before you start — the two tenant-side requirements. Qnaat reads and writes through Qlik's own MCP server, so two things must be true in your tenant: theModel Context Protocol (MCP) permission has to be Allowed for every role that will use Qnaat (Part 1, Step 2), and your tenant needs the Qlik capability behind that permission — see Step 2 if the setting is not there. A missing role permission is the most likely setup failure, and Qnaat may report it as an expired Qlik session: if a session-expired banner keeps coming back right after a connection that succeeded, check the role permission before anything else.

Part 1 — Tenant admin (once)

Step 1. Create the OAuth client

1. In Qlik Cloud, open the Administration activity center and go toOAuth → Create new.
2. Client type: Single-page app. Name it e.g. Qnaat.
3. Scopes: select user_default and mcp:execute.Do not select offline_access — Qlik rejects it for single-page app clients and creation will fail.
4. Redirect URL: paste the URL shown in the extension's Options page (see the note below). It looks like https://…chromiumapp.org/ — paste it exactly, including the trailing slash.
5. Allowed origins: add the same chromiumapp.org URL. This step is required — without it, connecting fails with an origin error.
6. Create the client and copy the Client ID. Your users will need it, together with your tenant URL.

Where do I find the Redirect URL? Install the Qnaat extension from the Chrome Web Store, right-click the Qnaat icon and choose Options. Step 3 of the "Conexión a tenant Qlik" section shows the exact Redirect URL. It is the same value for every Chrome Web Store install, so you only need to look it up once.

Your role may be named AI Feature Access MCP, as in our tenant. Role names are customizable. Search for MCP in the permission editor and assign the role to the user connecting Qnaat.

Step 2. Enable the Qlik MCP permission

Qnaat talks to Qlik through the Qlik MCP server, which is part of Qlik Cloud's Agentic AI capability and is gated per user role. In the Administration activity center, edit the roles of the users who will use Qnaat and, underFeatures and actions → Model Context Protocol, set Model Context Protocol (MCP) toAllowed.

Cannot find the setting? Qlik's public documentation describes the MCP server as available across Qlik Cloud subscriptions, while Qlik's support material presents it as a capability for paying Qlik Cloud customers on specific plans. We have not been able to confirm which subscriptions include it, so we do not claim it is included in all of them. If Agentic AI or Model Context Protocol (MCP)does not appear in your role editor, that is a question about your tenant's Qlik subscription, not a fault in Qnaat: ask your Qlik account team or Qlik Support whether your plan includes the Qlik MCP server. Write to[email protected]and we will help you check.

What Qnaat consumes on the Qlik side. Every question you ask Qnaat is answered through several calls to the Qlik MCP server, and Qlik meters that traffic against your tenant's Qlik Answers question allowance — roughly one Qlik question per five MCP calls. In our own use a single Qnaat question typically triggers six to eleven calls, so budget for about two Qlik Answers questions per Qnaat question. These are approximate figures from our own observations, not a guarantee: the real count varies with the question and with your data model. This usage is separate from, and in addition to, your Qnaat plan credits or your own Anthropic API spend. We would rather you know this before you start than find it in a usage report later.

Part 2 — Each user

1. Install Qnaat from the Chrome Web Store.
2. Right-click the Qnaat icon → Options.
3. Paste your tenant URL(https://your-tenant.region.qlikcloud.com) and theClient ID from your admin, then click Conectar.
4. Approve Qlik's consent screen.
5. In the same Options page, choose your AI source: a Qnaat plan(sign up at app.qnaat.com) or your own Anthropic API key.

First chat

Open any app in Qlik Sense Cloud — a sheet or the Data Load Editor — and open the Qnaat side panel. Ask about your data in plain language.

Building dashboards: for Qnaat to create sheets and charts, the sheet must be in edit mode (click Edit in Qlik's toolbar). In analysis mode Qlik's creation tools do nothing, and Qnaat can only answer questions about your data.

Troubleshooting

• Error when clicking Conectar (origin error) — the chromiumapp.org URL is missing from Allowed origins in the OAuth client. Ask your admin to add it (Part 1, Step 1).
• 401 error when chatting — the OAuth client is missing themcp:execute scope, or your user role doesn't have theModel Context Protocol (MCP) permission (Part 1, Step 2).
• "Sesión con Qlik expirada" banner — normal after about an hour; Qlik session tokens expire. Click Reconectar a Qlik.
• Consent window doesn't open, or shows a redirect error — the Redirect URL doesn't match exactly. Copy it again from Options, including the trailing slash.

References

Qlik's official articleConnecting to the Qlik MCP servercovers the same OAuth-client setup and includes a walkthrough video. Note: the pre-registered client ID mentioned there applies only to Anthropic's Claude connector — Qnaat requires its own OAuth client, as described above.

Qnaat is an independent tool for Qlik Sense and is not affiliated with, endorsed by or sponsored by QlikTech International AB.