Most of our MCP documentation is about connecting. This page is about the opposite: cutting off an AI assistant's access to your Sitebulb data, cleanly and completely. You'll want it when someone leaves the team, a laptop goes missing, a contract ends, or your security team simply asks "and how do we turn it off?"
The answer is reassuringly short. There's one step, it takes under a minute, and it works even if Sitebulb Desktop is closed or you're nowhere near your Cloud workspace.
The one step that revokes access
Remove the Sitebulb connector from inside the AI client it was added to. That's the complete revocation path: once the connector is gone, that AI client can no longer call any Sitebulb tool, full stop. Revocation happens entirely inside the AI client, so you don't need Sitebulb Desktop open, your workspace reachable, or a word with support.
Two things to know before you start:
If you connected both Sitebulb Cloud and Sitebulb Desktop, they appear as two separate connectors. Removing one doesn't affect the other, so remove both if you want a clean break.
A removed connector doesn't remember your previous approval. If you reconnect later, you'll go through the full sign-in flow again from the start - the guides are all linked from Sitebulb MCP: Start Here.
Removing the connector in Claude
Head to Claude's Connectors page at https://claude.ai/new#settings/customize-connectors - the same page you used to add Sitebulb. Find the Sitebulb Cloud or Sitebulb Desktop connector, open its options menu, and remove or disconnect it (Claude renames menus from time to time; if the labels don't match, look for whichever control on that page lets you manage or remove a connected app).
On a Team plan, there are two levels:
A Claude Owner can remove the Sitebulb connector at the organisation level, which removes it for everyone in the workspace at once. Use this when the whole team should lose access, for example if you're switching workspaces or winding down a trial.
An individual team member can disconnect just their own sign-in from the same Connectors page, without touching anyone else's access. Because every person authorises Sitebulb individually, cutting one person's access never requires deleting the shared connector.
Removing the plugin in ChatGPT
On an Individual plan, go to https://chatgpt.com/plugins, find the Sitebulb plugin, and delete it using its options menu (the same three-dot menu you'd find Publish under on a Business plan).
On a Business plan:
An Admin or Owner can unpublish or delete the Sitebulb plugin from the workspace, which removes it for the whole team.
An individual Member can remove the Sitebulb plugin from their own plugin list to cut just their own access, leaving it available for teammates.
What revoking does, and doesn't do
Removing the connector stops all future reads immediately. The AI client loses its authorisation and every Sitebulb tool with it.
It's just as important to know what it doesn't do:
It doesn't touch your Sitebulb data. Projects, audits, settings and your Sitebulb login are all unaffected. The MCP is read-only, so there was never anything for it to change in the first place.
It doesn't pull back data an assistant has already fetched. Anything Sitebulb returned into earlier conversations stays in those conversations, under the AI client's own data controls. If that matters (say, a leaver's chats contain client crawl data), delete the relevant chats in the AI platform too.
It doesn't deactivate anyone's Sitebulb account. Removing an MCP connection and removing a Sitebulb seat are separate jobs - see the offboarding checklist below.
Revoking a workspace or machine target
During sign-in you chose a 'target': your Cloud workspace, or a specific Desktop machine. If you revoke the target itself rather than removing the whole connector, you may find you can't simply add it back. The fix is to go back into your AI client and restart the connect flow from the beginning - you'll then be able to select the workspace or machine as the target again.
Offboarding a team member
When someone leaves, their Sitebulb MCP access is one line on a bigger checklist. Because every connection is tied to the individual who approved it, the reliable path runs through their own accounts:
Before their access ends, have them remove the Sitebulb connector(s) from their own Claude or ChatGPT account, following the steps above. Check for both Cloud and Desktop entries.
Remove their Sitebulb seat through your normal Sitebulb account admin. This is the belt-and-braces step: a fresh MCP connection always requires a working Sitebulb sign-in, so a deactivated account can't be reconnected.
Deal with what's already in their chats. Past conversations may contain Sitebulb data that was fetched while they had access. Handle those through your AI platform's own admin controls, per your organisation's policy.
If their Desktop machine passes to someone else, the new user sets up their own connection with their own Sitebulb sign-in - connections don't transfer between people.
Check it worked
Ask the assistant a Sitebulb question, for example "list my Sitebulb projects". If it no longer offers Sitebulb tools at all, or tells you it can't reach Sitebulb, the connection is gone. Either answer confirms the revocation took.
Note: Worried about what data was shared while the connection was live? The Sitebulb MCP: security and privacy overview explains exactly what moves, when, and where it goes.