Disconnecting a Connector

Disconnecting removes a connector's stored credentials from StackJack. Use it when you're retiring a vendor product, rotating to a completely different credential set, or off-boarding a tool you no longer want your AI assistant to reach.

Disconnect acts on one connection, not on the connector. Where a connector holds several named connections, each one is removed on its own, and the connector stays connected until the last one is gone.

How to disconnect

1. Open Connectors and find the connector's card.
2. Select Disconnect to remove the connector's default connection, or open the card's connections list and remove one named connection from there.
3. Review the confirmation. Read the title first: Disconnect ? means this is the last connection and the whole connector is going; Remove ? means the other connections keep working.
4. If this is the last connection and the connector is on a live Free plan, choose whether its tools should also be removed. The checkbox is selected by default.
5. Confirm. When that was the last connection, the card returns to Not Configured. When other connections remain, the card stays connected and only the removed connection disappears from the list.

You are told what happens to the default before you confirm. If the connection you are removing is the default and others remain, the dialog names the connection that inherits the role.

What disconnecting does

• Deletes the stored credentials for the connection you removed.
• Stops that connection from executing — calls naming it fail from then on. Calls that named no connection fall to whichever connection is default afterwards. If this was the last connection, every call for the connector fails until you reconnect.
• Removes the team's personal sign-ins that belonged to that connection. A member's HaloPSA, NinjaOne or Microsoft sign-in is a sign-in on one connection, so it goes with the connection and the member has to sign in again if you recreate it. N-able N-central is the exception: a member's own N-central token is theirs and StackJack does not delete it, because the token cannot be recovered without them pasting it again.
• Clears endpoint pins that named that connection. Any AI endpoint pinned to it becomes unpinned rather than pinned to something it never chose.
• Keeps your MCP clients. Your AI tools stay connected to StackJack; only this connector stops working.
• Leaves an automation's own enrolled credential alone. Where an administrator enrolled a dedicated sign-in for one automation, that credential belongs to the automation rather than to this connection, so disconnecting does not remove it. Remove it from the automation itself if that is what you meant to do.

Removing the default connection

If you remove the connection currently marked default and others remain, the oldest remaining working connection becomes the new default, so calls that name no connection keep working. The dialog names it before you confirm. Check that it is the one you want; if not, set a different default from the connections list afterwards.

Free connector: tool removal is your choice

This choice is offered only when you are removing the last connection of a live Free connector — removing one of several would take the tools away from the connections that remain. In that case the dialog includes Also remove this connector's tools from tool lists and MCP setup. It starts selected:

• Leave it selected to deactivate the Free subscription and remove the connector's tools from tool lists and MCP Setup. Reconnecting puts the tools back.
• Clear it to keep the Free subscription and its tools listed. Calls still fail until you reconnect because the credentials are gone.

Nothing is billed either way.

Paid connector: plan and tools stay

For a paid connector, there is no tool-removal checkbox. Disconnecting removes the credentials, but the paid subscription stays active, its tools stay in tool lists, and billing continues. The dialog says so on the spot. Use Manage on Billing on the connector card separately if you also want to end the plan; it opens this connector's removal dialog on the Billing page. A legacy website subscription reads Cancel Plan instead and cancels on the spot.

What disconnecting does NOT do

⚠ Disconnecting never cancels a paid subscription. Billing continues until you end the plan. On a paid connector, Manage on Billing on the connector card takes you to the Billing page with that connector's removal dialog open; a legacy website subscription uses Cancel Plan on the card. Connector rows on the Billing page no longer carry a hosted cancellation link, because it ended every connector on the subscription rather than the one whose row it sat on. See Canceling, downgrades, and payment issues.

Your team members, their tool assignments, your other connectors and your usage history are untouched. What it does reach beyond the credential is listed above: the personal sign-ins made on that connection, and the endpoint pins that named it.

Reconnecting later

Reconnect any time by selecting Configure and entering credentials again. An existing active subscription applies immediately; a disconnected Free subscription that was removed is reactivated; and a connector without a subscription receives a Free plan.

Two things do not come back on their own after you reconnect. Team members re-sign-in on the connectors that use a personal sign-in, and any endpoint you had pinned to the removed connection has to be pinned again on the Endpoints page.