Skip to main content
Qubit and AI

StackJack

StackJack gives Qubit and automations tools across your MSP platforms. You add it as an MCP source, and each person connects their own StackJack account so Qubit offers only what that account may use.

Last updated 24 days ago

StackJack gives Qubit and your automations tools across the MSP platforms you use, and StackJack keeps adding platforms. You set it up as an MCP source: there is nothing to activate, and QuantumOps shares no PSA credentials with StackJack. Each person connects their own StackJack account, so Qubit only offers the tools that account may use.

Before you start:

  • The plug button in the header (MCP Sources) opens the page, and so does MCP Sources in the sidebar. Every signed-in person sees both.
  • Each person needs their own StackJack account to sign in with.
  • An Administrator adds StackJack once. After that, each person connects.
TaskWho can do it
Add the StackJack preset, change the catalog, switch it off, manage Tool GovernanceAdministrator
Connect, test or disconnect your own accountAny signed-in user

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. Choose MCP Sources in the header or 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 checked 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:

SettingValue
Aliasstackjack
Sign-inOAuth, per person
ApprovalsDestructive tools always need approval
YouYour own state: Connected, Not connected, or "Add it first, then connect your account."

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, uncheck 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.

Ticket Autopilot and StackJack

Ticket Autopilot uses StackJack in two ways. When an agent runs a plan, each StackJack step uses that agent's own connection, the one made through the preset under MCP Sources, and Autopilot never falls back to a shared key; the browser extension asks the agent to connect before they lock a plan that needs it, see Connect StackJack before you lock. When a routine runs without a person, there is nobody to sign in, so Autopilot uses a connection of its own, a StackJack API key for a dedicated StackJack user, which an Administrator sets up on Autopilot settings. Only those unattended runs use the key, and the ticket pipeline once you turn stages on for it (see below). It is not a way for people to connect.

The ticket pipeline and StackJack

The ticket pipeline can read the connectors of a StackJack connection, such as IT Glue and Hudu, for every ticket: analysis, research, reply drafts and Autopilot plans can cite the client's documents and records. The pipeline runs without a person, so it uses a shared key, not each person's sign-in. It reuses the StackJack connection Autopilot already has, or a service connection you add on MCP Sources; the per-user preset above is never read by the pipeline.

  • On MCP Sources, the StackJack source that uses an API key has a Connectors button. The table lists the connectors your StackJack account holds, with one box per stage, and lets you pin a connector to one of its connections when it has several.
  • Each connector has its own monthly call allowance in StackJack, shared with chat and Autopilot. The page shows how much a connector has used, and the pipeline pauses a connector whose allowance is used up until its cycle resets.
  • The key's tool selection in StackJack decides which records the pipeline can reach, and everyone who works a ticket sees the same records. The pipeline only reads, and never reads passwords, credentials or one-time passwords, whatever the key allows.

See Pipeline sources.

Tool Governance

Administrators see Tool Governance at the bottom of MCP Sources. Choose Tool governance at the top of the page to jump to it. It covers every tool Qubit can call, not only StackJack's. See Tool Governance.

If you used the old StackJack Integration page

StackJack used to have a page of its own with an Activate StackJack button. It is gone, and its address now opens MCP Sources, so a bookmark still works.

  • Activating shared your HaloPSA credentials with StackJack and needed setup on TechPulse's side. The preset needs neither.
  • Add StackJack with the preset above. Nothing else creates the older kind of connection any more.
  • A connection made on the old page keeps serving Qubit's older StackJack tools until it is disconnected. While one is left, MCP Sources shows a card called Older StackJack connection. The card also appears if the old page saved your credentials but never verified them: they are not used, and the card says so, but they stay stored until you remove them. Choose Disconnect my older connection to remove yours. An Administrator can choose Switch off the older setup for everyone, which removes every stored StackJack credential. The preset is not affected, and the card disappears once nothing is left.
  • Tool Governance moved to MCP Sources.