StackJack

StackJack gives Qubit and your automations tools across the MSP platforms you use. The StackJack Integration page describes it as 400+ tools across HaloPSA, NinjaRMM, Hudu, CIPP and 12 more MSP platforms. Each person connects their own StackJack account, so Qubit only offers the tools that account may use.

There are two places to set it up. The StackJack preset under MCP Sources is the way to start, and it is what the Agents page needs for StackJack automations. The StackJack Integration page is the second place; it shares your HaloPSA credentials with StackJack and links each person's HaloPSA account.

Before you start:

• The plug button in the header appears when the StackJack Integration module is on. An Administrator switches modules in Module Management.
• To activate StackJack on the StackJack Integration page, TechPulse must have set up the StackJack connection for your instance. If activation reports an error, contact TechPulse.
• Each person needs their own StackJack account to sign in with.

Add the StackJack preset

With the preset, every person signs in with their own StackJack account, and StackJack decides what that account may see and do. Qubit then offers only what that person may use.

1. Open MCP Sources in the sidebar. Find the card StackJack for this tenant: each person signs in. Its status reads Not added.
2. Under Catalog, choose Full or Compact. Full gives Qubit every tool the person's account may use. Compact keeps the tool list small: StackJack's platform tools plus tools to search, describe and call the rest.
3. Leave Enabled ticked and choose Add StackJack.
4. Ask everyone who will use StackJack to connect. Each person opens My connections on the same page, presses Connect on the StackJack row and signs in with their own StackJack account in the new tab. They then press Test. An Administrator can also press Connect my account on the card.

The card also lists the settings the preset always uses:

You do not need a client ID. QuantumOps signs in to StackJack with its own client identity.

Change the catalog or switch StackJack off

To move between Full and Compact, pick the other one and choose Save. QuantumOps asks you to confirm first, because switching hosts signs everybody out of StackJack. Each person presses Connect again afterwards. If you decline, the page says the host was not changed.

To switch StackJack off without deleting it, untick Enabled and choose Save. A plain enable or disable keeps everyone's sign-in.

If the card reports that another source already uses the alias stackjack, rename or delete that source first. It may be a tenant source, or a colleague's personal source that you cannot see. Then add the preset again.

What people see

• The row under My connections tells each person that StackJack scopes their tool catalog by their identity, so they see the connectors and tools their account may use.
• A tool that StackJack marks as destructive always waits for approval. Other tools follow your rules in Tool Governance.
• Agent Runners cannot use a per-user StackJack connection, because a runner has no signed-in person. To automate with StackJack, build a StackJack automation with Qubit. See Agent Runners.

For the sign-in states and the other fields of a source, see MCP sources.

Use the StackJack Integration page

Choose the plug button in the header (StackJack integration) to open StackJack Integration. The button only appears when the module is on. Under the title, the page says it connects 400+ MSP tools to your AI chat via the StackJack MCP Server.

Activate StackJack

Only an Administrator can activate. Until then the page shows Activate StackJack, with a note that your existing HaloPSA credentials will be shared with StackJack.

1. Choose Activate StackJack. QuantumOps sets StackJack up for your organisation and registers your HaloPSA credentials with it.
2. When it finishes, the page shows StackJack is active for this tenant, the activation date and an Active badge.

If HaloPSA is not set up for your organisation, activation reports that and stops. Set up HaloPSA first.

Everyone else sees StackJack is not activated yet and is asked to contact an Administrator.

Connect your own account

Once StackJack is active, each person can link their own HaloPSA account here. This connection is separate from the StackJack preset: Qubit chat and the Agents page use the preset (see "The two connections are separate" below).

1. Under Connect your Halo account, choose Connect to Halo. The StackJack Portal opens in a new tab. If it does not open, use the Open StackJack Portal link under "Step 1 — Authorize in the StackJack Portal".
2. Finish authorising HaloPSA in the portal.
3. Come back to QuantumOps and choose I've finished — Verify status.

When StackJack accepts the connection, the page shows Your Halo account is connected, with a Disconnect button. If the page cannot confirm the connection yet, it says so and your status stays Pending. Finish the steps in the portal and verify again later, or choose Reconnect to start over. If StackJack rejects your credentials, the page shows an error status and asks you to reconnect.

You cannot connect in two situations. The page shows a notice in each:

• During a support access session, activating, connecting and verifying are switched off, so a connection is never created under another person's identity.
• When your sign-in identity cannot be determined in the current session, StackJack is switched off for that session. Sign out and sign in again.

See and disconnect users

An Administrator sees User Connections, with a column for each of User, Status, Connected and Last Used. The status is Connected, Pending or another state such as an error. A Connected row has a disconnect button, so you can remove one person's connection. Before anyone has connected, the table reads "No users have connected yet."

Deactivate StackJack

An Administrator can choose Deactivate. This clears every person's stored connection. If you activate StackJack again later, everyone connects again.

The two connections are separate

The preset under MCP Sources and the StackJack Integration page keep separate connections. Connecting on one page does not connect you on the other. For Qubit chat and for the StackJack automations list on the Agents page, connect through the preset.

Tool Governance

Administrators see Tool Governance lower on the StackJack Integration page. It covers every MCP source, not only StackJack, and it appears when StackJack is active or your organisation has any tenant-wide source. See Tool Governance.

Related pages

• MCP sources: the sources page, scopes and sign-in states.
• Tool Governance: which StackJack tools are allowed, need approval or are denied.
• Agent Runners: StackJack automations and the limits on unattended runs.
• What Qubit can use: tools and sources: how Qubit chooses tools.