Product knowledge

Docs

Docs
User guide
View Markdown

Connect an AI client

Connect your approved MCP client to the correct Gateway endpoint using your own assigned identity.

On this page

Use the endpoint supplied by your Gateway

Raptor Gateway exposes MCP over Streamable HTTP. Use the public HTTPS address and connection details supplied by your administrator or generated by the Gateway. A client must support the transport and authentication method selected for that installation.

Keep the domain query in the endpoint. Each domain exposes a different tool set, subject to the Gateway licence, your seat and your Raptor roles. Connecting only to the Hub endpoint does not provide Qlik development or analytics tools.

Examples only. Use the exact addresses and any platform selector returned by your installation.
https://your-gateway.example.com/mcp?domain=qc
https://your-gateway.example.com/mcp?domain=qs
  • qc: Qlik Cloud; qs: Qlik Sense Enterprise on Windows.
  • insights: analysis and insight delivery; writeback: approved writeback workflows; admin: administration.
  • qv-migration and pbi-migration: their respective migration workflows.
  • hub: Experience Hub and shared knowledge workflows.

Native OAuth, where enabled

An administrator can enable native MCP OAuth on a suitably configured local gateway-managed HTTPS installation. When your client supports this flow, add the supplied endpoint and follow its browser sign-in. The Gateway displays the requesting client and endpoint before you connect it.

Sign in with the Qlik identity assigned to your Raptor seat. Review the requested connection and approve it only when it matches the client you are setting up. Let the client store and refresh its own OAuth credentials for that resource. Do not copy browser credentials or reuse a Hub grant for another endpoint.

If OAuth is not offered, ask which connection method the installation supports. An external Raptor Portal sign-in is not a substitute for Gateway or Qlik authentication.

Personal Gateway tokens

For clients configured with a bearer token, open /raptor/ on your Gateway. The page guides you through the configured Qlik sign-in and can generate an MCP token for your existing assignment. A user who has not been assigned in Seats must contact the Gateway administrator.

  1. Sign in with the intended Qlik account, then give the token a recognisable label for the client or device.
  2. Select Generate MCP token and copy the displayed connection details into the client's secure credential settings. The token is shown once.
  3. Configure the Authorization header with the complete Bearer value. Keep Qlik API keys, certificates and the Gateway licence token out of the client.
  4. Discover the available tools, then test a connection or list accessible apps before attempting changes.
Set this in the client's protected credential field, not in a prompt, shared file or URL.
Authorization: Bearer <your-personal-gateway-token>

Client features and long-running work

The Gateway enables Tasks, approval exchanges and MCP Apps by default, with separate administrator opt-outs. Clients must negotiate the features they support. Their availability does not grant additional roles or override a tool's confirmation requirements. MCP Apps include analytical charts and a reload monitor; a chart can also return an SVG fallback where an interactive App is unavailable.

Task support covers supported Qlik Cloud reloads and task-based Qlik Sense reloads, rather than every tool operation. For a reload returned as a task, inspect its status and final result. A submitted operation or a disconnected client is not proof that the reload completed or failed. Preserve the returned identifiers and check the outcome before repeating a change.

Copilot Studio users should use the appropriate custom connector definition supplied by the Gateway and create their own connection. Microsoft Entra/OBO requires additional administrator configuration and a verified seat binding; it is not an interchangeable replacement for a personal token.

Previous

Users, seats and roles

Next

Copilot Studio integration