Connecting to the Qlik MCP server | Qlik Cloud Help
Skip to main content Skip to complementary content

Connecting to the Qlik MCP server

Last updated: 11/3/2026

Connect your LLM client to the Qlik MCP server.

Prerequisites

To connect your LLM client to the Qlik MCP server, you need the following:

  • The Qlik MCP permission set to Allowed. A tenant administrator grants this permission through the default permissions or a custom role.

  • An LLM client that can connect to remote MCP servers, such as Claude or ChatGPT.

  • The Qlik MCP server URL for your tenant: https://<tenant address>/api/ai/mcp.

  • An OAuth client for your LLM client. Your tenant administrator creates the OAuth client or sets up registration with one of the supported methods. For more information, see Creating an OAuth client.

  • For each LLM client, a tenant administrator must connect to the Qlik MCP server first. After that, other users can connect with the same LLM client.

Connecting your LLM client

Follow the directions in the following topics to connect your LLM client to the Qlik MCP server:

These steps provide general guidance for configuring connections in your own LLM applications. Qlik does not own these applications and cannot guarantee the accuracy of all steps. Steps are subject to change by your application provider.

Limitations

Qlik MCP server has the following limitations:

  • Authentication to the Qlik MCP server is governed by the OAuth client configuration and your identity provider (IdP) configuration:

    • If the OAuth client does not include the offline_access scope, or your IdP does not issue refresh tokens, users must re-authenticate when the access token expires, after 6 hours.

    • If the OAuth client includes the offline_access scope (and is not a single-page application client) and your IdP issues refresh tokens, the MCP client can renew its access token without user interaction. Users must re-authenticate when the refresh token expires, after 30 days.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!