Back to home

    Business Perspective

    RaptorMCP Gateway: Business Overview

    A governed access layer for AI-assisted Qlik work, backed by a central enterprise knowledge base.

    Audience
    Customer stakeholders
    Platform
    Qlik Cloud and QSEoW (client-managed)
    Purpose
    Gateway overview and setup alignment

    What The Gateway Is

    The RaptorMCP Gateway is a controlled integration layer that allows approved AI agents and automation clients to work with a customer's Qlik estate in a governed way. For Qlik Sense Enterprise on Windows, the Gateway is normally hosted inside the customer's network or an approved partner-managed environment so that access, credentials, monitoring and operational controls remain under the customer's governance model. Qlik Cloud customers can also use Modern Management hosting.

    The Gateway does not replace Qlik. It sits alongside the existing Qlik platform and provides a secure, managed path for AI-assisted workflows such as app analysis, script support, reload investigation, data model review, writeback, approvals and operational insight generation.

    Business summary

    Qlik User Licence + RaptorMCP licence + the user's chosen AI agent. Qlik remains the analytical estate; the Gateway connects permitted knowledge and capabilities to the agent while the customer keeps control of access, scope and oversight.

    Shared Knowledge Across Teams

    Standards, business definitions, templates, workflow definitions and reusable agent Skills can be kept in a central enterprise Qlik AI knowledge base. Each user's agent only sees the knowledge their folder permissions allow, and only the Qlik content their Qlik access allows. That keeps answers consistent across teams and makes handovers less dependent on individuals.

    What It Provides

    • A single governed access point between approved AI agents and the Qlik estate.
    • Controlled access to Qlik apps, sheets, objects, scripts, reloads, fields, metadata and supporting operational information, within each user's permissions.
    • A central enterprise knowledge base of standards, definitions, templates and Skills that agents use in context.
    • Support for faster app review, data discovery, reload troubleshooting, expression support and insight preparation.
    • Governed writeback, approvals and workflows with recorded outcomes.
    • A deployment pattern that can align with the customer's security, network, identity, logging and support policies.
    • A path to advanced analytical use cases where optional Qlik SSE or Python analytics services are part of the scope.

    Typical Business Use Cases

    • Reviewing existing Qlik apps to understand data models, measures, dimensions and sheet logic.
    • Helping business and analytics teams ask deeper questions of existing reporting assets, using agreed definitions.
    • Reducing manual effort in app documentation, handover, issue investigation and analytical preparation.
    • Capturing planning input and decisions in Qlik and routing them for approval.
    • Supporting governed automation around reload support, reporting checks and delivery evidence.

    Governance Position

    The recommended approach for an on-prem Qlik Sense customer is a customer-hosted gateway. This keeps the gateway within the customer's approved infrastructure boundary and allows the technical team to apply its normal controls for hosting, certificates, firewall rules, service monitoring, backup, and incident response.

    Users and clients should be approved before access is granted. The gateway should be configured so that available actions match the customer's subscription, assigned roles, and Qlik permissions.

    Implementation View

    AreaRequirement
    Deployment modelCustomer-hosted inside the approved network boundary, partner-managed, or Modern Management hosted.
    Primary connectionSecure connectivity from the Gateway to Qlik Sense Enterprise on Windows services, Qlik Cloud, or both.
    User accessApproved AI agents and users connect through the Gateway rather than directly to Qlik services.
    AI processingWhere prompts and data are processed depends on the AI model, provider and configuration the customer chooses. Hosting the Gateway internally does not by itself make inference local.
    Security ownershipCustomer security and infrastructure teams retain control of hosting, network exposure, certificates, credentials and monitoring.
    Advanced analyticsOptional Qlik SSE/Python analytics services can be added where forecasting, machine learning, NLP or enrichment use cases are required.

    Recommended Next Step

    Confirm the Qlik Sense environment in scope, the preferred hosting location, the approved authentication approach, and the initial AI-assisted workflows the customer wants enabled. Once agreed, the technical team can validate network access, service identity, certificate handling, monitoring, and gateway operations before production use.