Product knowledge
Docs
Gateway architecture
Follow the connection from an approved AI client through Gateway access controls to the user’s permitted Qlik environment.
On this page
Request flow
An AI client connects to the Gateway’s Streamable HTTP endpoint. Gateway authentication identifies the caller; the licence, assigned seat and Raptor role restrict the available tools. The Gateway then uses the configured Qlik connection and identity to perform the permitted operation.
The diagram shows the runtime path and customer security responsibilities. The external Raptor Portal is a separate service for accounts, agreements, licence administration and downloads.
Architecture diagram
Use this view when agreeing the Gateway host, client route, Qlik endpoints and operational ownership. Customer infrastructure can include an approved partner-managed host; the network boundary depends on your actual deployment.
Architecture view
Raptor MCP inside the organization domain
This architecture view shows the customer-hosted Raptor MCP Gateway as the controlled bridge between approved AI tooling and customer-approved Qlik access inside the organization's security boundary.
Organization domain / security boundary
The organization controls users, AI tooling, identity, network policy, gateway hosting, credentials, and operational logs.
- Customer user
- Customer AI / IDE / LLM
- Identity, network and security controls
- Customer Qlik access credentials / service account / OAuth
- Customer logging, monitoring and incident response
Customer-hosted Raptor MCP Gateway
The gateway validates access and routes approved MCP capabilities through the Qlik connector layer.
- Streamable HTTP Gateway
- Access key / token validation
- Policy / entitlement check
- MCP tool routing
- Qlik connector layer
- Audit / event logging
Customer-approved Qlik environment
The customer's Qlik estate remains governed by customer-approved Qlik permissions.
- Qlik Cloud
- Qlik Sense Client-Managed / QSEoW
- Qlik apps
- Qlik data connections
- Qlik automation / migration / metadata operations
Approved AI-to-gateway route
Customer AI / IDE / LLMCustomer-hosted Raptor MCP Gateway
Qlik MCP capability routing
Customer-hosted Raptor MCP GatewayQlik Cloud and QSEoW
Customer-approved Qlik access
Qlik connector layerCustomer Qlik access credentials / service account / OAuth
Operational evidence
Audit / event loggingCustomer logging, monitoring and incident response
Three separate access checks
The Portal establishes commercial entitlement. Gateway administration assigns named users and their local access. Qlik controls the apps, data and operations available to the resolved Qlik identity.
Changing a Qlik role or custom property does not create a local Gateway seat. Assign access through Raptor Administration > Seats, then verify the user’s sign-in and effective tools. A domain-specific endpoint narrows tool discovery; it does not grant a licence, seat or Qlik permission.
Data and secret handling
Qlik credentials are configured in the Gateway environment rather than pasted into an AI conversation. Personal Gateway credentials authenticate the client; the installation licence token is not a user credential.
The Gateway stores operational state and feature-specific content in its configured database and repository. Requested Qlik results are returned to the calling client. Where an LLM, delivery channel, report destination or other external service is configured, its processing and retention must also be covered by your organization’s controls.
Network and TLS
Fresh Windows Setup uses HTTPS on 7443 and a loopback HTTP listener on 7331. Reverse proxies and administrator-managed deployments can use different external addresses. Distribute the exact HTTPS address and establish trust for its certificate on each client.
A cloud-hosted client such as Copilot Studio must be able to reach that address from its own execution environment. A URL that opens on the Gateway machine does not establish remote reachability.
Operations and recovery
Use the organization’s controls for hosting, secrets, access review, logging, certificate renewal and incident response. Database-aware backups must include the repository and the encryption material needed to restore the service.
Raptor MCP is independent software from Modern Management. Qlik Cloud, Qlik Sense and related marks are trademarks of QlikTech International AB or its affiliates; Raptor is not owned, operated, endorsed or sponsored by Qlik.
Previous
Raptor Gateway
Next