Raptor MCP packages are distributed from the licensed web portal, not public marketplaces or public source repositories. Sign in, make sure your Raptor MCP license is active, then use Dashboard > Raptor MCP License to choose the module group and client package.

Client packages are generated per licensed module. Qlik Cloud, Qlik Sense, QlikView Migration, and PBI Migration each provide Codex, generic stdio, Claude, VS Code, Windsurf, Cursor, Antigravity, Gemini CLI, GitHub Copilot Enterprise, and JetBrains variants where supported. The Qlik SSE Tools download is a separate Python SSE toolkit package for Qlik Sense Client-Managed servers.

• Create an MCP API token from Dashboard > Account before configuring a package.
• Download the package from Dashboard > Raptor MCP License.
• Choose the top-level module first, then the client package for that module.
• Extract the zip to a stable local folder that will not be deleted or moved.
• Update the included config example with the extracted package path.
• Set RAPTOR_MCP_TOKEN and keep the package-provided RAPTOR_MCP_DOMAIN and RAPTOR_MCP_MODULE values.
• Restart the target client and ask it to list the available Raptor MCP tools.
• For Power BI to Qlik migration, configure the separate Power BI Migration MCP beside Raptor MCP so source extraction and Qlik rebuilds stay separated.

The Codex plugin artifact is module-specific, for example raptor-mcp-qc-codex-plugin.zip or raptor-mcp-qv-migration-codex-plugin.zip. It contains the bundled MCP runtime, the relevant skills catalog for that module, icon assets, license, and notices.

• Install the plugin artifact in Codex.
• Create an MCP API token in Dashboard > Account.
• Set RAPTOR_MCP_TOKEN in the MCP environment.
• Keep the package-provided RAPTOR_MCP_DOMAIN and RAPTOR_MCP_MODULE values so Codex exposes only the intended module surface.
• Configure Qlik Cloud, QSEoW, QlikView, QV2QS, or Power BI/Fabric variables only for the module you are installing.

Use the dashboard package picker as a two-level menu: first choose Qlik Cloud, Qlik Sense, QlikView Migration, or PBI Migration, then choose the target client package. If a client is not listed, start with the module's generic stdio config and copy the command, args, and env shape into that client's MCP settings.

• Raptor QC MCP: Qlik Cloud development, administration, governance, Reporting, Predict, and Cloud-safe extension workflows.
• Raptor QS MCP: Qlik Sense Client-Managed / QSEoW development, operations, QRS/admin, extension, connection, and SSE helper workflows.
• Raptor QV Migration MCP: QlikView inventory, QV2QS conversion, temp Cloud cleanup, and focused post-conversion validation.
• Raptor PBI Migration MCP: Power BI/Fabric source evidence extraction and migration manifest creation.
• Enterprise Streamable HTTP Gateway: Streamable HTTP package for customer-network deployments with Qlik-hosted user and admin pages.
• Qlik SSE Tools: Python Server-Side Extension toolkit for Qlik Sense Client-Managed forecasting, machine learning, NLP, and document workflows. It is licensed through Qlik Sense module access.

Use the Codex plugin and stdio runtime for local Codex workflows. Use the enterprise Streamable HTTP gateway when an MCP client needs a network endpoint inside the customer environment.

• Codex plugin: stdio runtime started from .mcp.json.
• Enterprise gateway: Streamable HTTP endpoint at /mcp with bearer-token access.
• Both modes share the same domain gating model. The package or request domain controls which tools and skills are exposed.

Use only the variables needed for the target workflow. Cloud, QSEoW, QlikView inventory, and QV2QS export settings can coexist, but they serve different jobs.

• RAPTOR_MCP_TOKEN: entitlement token for MCP clients.
• RAPTOR_MCP_DOMAIN and RAPTOR_MCP_MODULE: package-provided module selectors such as qc, qs, qv-migration, or pbi-migration.
• RAPTOR_MCP_WEB_URL: license portal URL when not using the production default.
• QLIK_BASE_URL and QLIK_API_KEY: Qlik Cloud access when QLIK_PLATFORM=cloud.
• QSEOW_*: QSEoW server, certificate, proxy, and header-auth settings when QLIK_PLATFORM=qseow.
• QLIKVIEW_APP_FOLDERS: one or more QVW source folders for inventory.
• QV2QS_*: local QV2QS and Cloud export settings for conversion workflows.