
It started with one Connect button in Claude. Then ChatGPT wanted Google Drive, Cursor got a GitHub server, and Claude Code and Codex each picked up a few more. Now you want to cut off the apps you no longer use, and you can't say which ones still have access.
Removing a connector in your AI assistant can leave the grant live at Google, GitHub, or wherever it was issued. So revoke in three layers, in order: list and remove in each assistant, revoke at each provider, then log out and remove on your own machine.
Arc0 publishes this blog and is the worked example near the end; everything before that works without it. You'll get the paths for five assistants and five providers, the files to check on disk, and a monthly routine that keeps the list short.
Removing a connector isn't the same as revoking it
Every connection lives in at least two records: the assistant's list, and the grant the provider issued when you clicked Allow. Those two can disagree, because deleting the first can leave the second live. Files on your own machine are a third place.
The second record is an OAuth grant. OAuth is how a provider like Google lets an app act for you without your password; the app keeps a token.
As of November 2026, the docs say this plainly, just on different pages.
- Claude Code says it outright. Removing a remote server deletes the OAuth tokens and client registration Claude Code stored, but doesn't revoke them at the authorization server. Where the server supports revocation, the docs tell you to run
claude mcp logout <name>beforeclaude mcp remove <name>. - ChatGPT: "Changing an app permission does not disconnect the app or revoke access already granted to a provider account." OpenAI's help names one provider, saying disconnecting iCloud does not revoke its password at Apple, and for the rest sends you to the provider's own account controls.
- Anthropic names both places: you can revoke permissions "by disconnecting the connector in Claude's settings or the third-party service's security settings."
- Google adds the part nobody likes. Once you remove access, the app can no longer reach your Google Account, but data it already copied stays with the app, and you would have to ask the developer to delete it.
So always finish at the provider. It issued the grant, so it is the one place that can take it back. There may be a token for an app you uninstalled months ago, still valid, patiently waiting for a request that never comes.
Layer 1: in each assistant
Every assistant keeps its own list, and each has its own word for taking something off it: Remove, Disconnect, a toggle, a logout. Start here, because this is where you see what you actually connected. As of November 2026, the menu paths here and in layers 2 and 3, and what the docs say about where tokens are stored, are as each vendor's own docs give them.
Coding agents list MCP servers rather than connectors. MCP, the Model Context Protocol, is the standard assistants use to call outside tools; a server is one plug-in that speaks it.
Claude (claude.ai and desktop)
Open Customize > Connectors to see your connected services. To remove one, click Remove or open the three-dot menu and follow the prompts. On Team and Enterprise plans, owners manage org connectors in Organization settings > Connectors.
Anthropic's Google connector page uses a different word: click the Google connector, choose Disconnect, and confirm Disconnect. Two pages, two verbs; press whichever one your screen offers.
Custom connectors built on remote MCP run from Anthropic's cloud, not your device. Local servers you added to Claude Desktop are another matter, and they come back in layer 3.
ChatGPT
Open Settings, then Apps or Plugins, "depending on which option is available." Choose the app, open the account's ••• menu or Connection, and select Disconnect.
Disconnecting stops future access through that account. It does not delete your conversations, saved files, or Memory, and other accounts connected to the same app can stay active. Uninstalling a plugin can disconnect every account connected through it, so read the warning before you confirm.
Cursor
Open Customize to see your MCP servers. The toggle disables a server and leaves it in place; to get rid of it, "Remove the server from Customize." A disabled server is one you've only asked to be quiet.
If a server also runs in Cloud Agents, sign out there too. Cursor's docs say "Signing out locally doesn't sign out Cloud Agents," and you log out on the server's Cloud row in Customize.
Claude Code
List what's configured, inspect anything you don't recognize, then log out before you remove:
claude mcp list
claude mcp get <name>
claude mcp logout <name>
claude mcp remove <name>Run remove alone and your list looks tidy while the authorization server never hears about it. Inside a session, the /mcp menu has Clear authentication, which the docs describe as the way "to revoke access."
Codex CLI
codex mcp list shows your servers. Then two commands do two different jobs. codex mcp logout <name> removes the stored OAuth credentials for a streamable HTTP server, and codex mcp remove <name> deletes the server definition. Run both:
codex mcp list
codex mcp logout <name>
codex mcp remove <name>Read the last column before you trust any of the remove buttons:
| Assistant | Where to list | How to remove | What the docs say about the provider side |
|---|---|---|---|
| Claude | Customize > Connectors | Remove, the three-dot menu, or Disconnect for Google | You can revoke by disconnecting in Claude or in the service's security settings |
| ChatGPT | Settings > Apps or Plugins | ••• or Connection > Disconnect | Stops future access through that account; check the provider's account controls |
| Cursor | Customize | Remove the server from Customize | Disable, remove, or sign out of Cloud Agents; check the provider yourself |
| Claude Code | claude mcp list | claude mcp logout, then claude mcp remove | logout first, where the server supports revocation |
| Codex CLI | codex mcp list | codex mcp logout, then codex mcp remove | logout removes the stored OAuth credentials |
Layer 2: at each provider
Every provider keeps its own page of apps you've let in, and that page is where a grant actually ends. It also lists grants you forgot, which is half the reason to visit. These are the paths in each provider's own help.
- Open
myaccount.google.com/linkedapps. - Filter by Access to your Google Account and select the app.
- Select See details, then Remove access, then Confirm.
If an app only uses your account to sign you in, the button is Stop using Sign in with Google instead.
Microsoft (work or school)
These steps are for work or school accounts; personal Microsoft accounts are out of scope here.
- Open
myapplications.microsoft.com. - Open the ... menu on the app and choose Manage your application.
- Select Revoke Permissions.
You can't revoke permissions your administrator consented to, and Microsoft warns that removing permissions may break the app.
Admins work from the Entra admin center: Entra ID > Enterprise apps > All applications, pick the app, then Permissions. The Admin consent tab offers Revoke permission to a Cloud Application Administrator or higher. The User consent tab can't be revoked in the portal; Microsoft points you to Microsoft Graph or PowerShell. And revoking does not stop users from consenting again to the same permissions. A revoke closes the door; it doesn't lock it.
GitHub
Go to your profile picture, then Settings > Integrations > Applications > Authorized OAuth Apps. Open the three-dot icon next to an app and choose Revoke, or use Revoke all.
GitHub Apps are two separate things, and this is the step people miss. Installed GitHub Apps > Configure > Uninstall removes the app's access in that account; de-authorizing it under Authorized GitHub Apps deactivates the tokens it was issued on your behalf. To cut it off fully, do both. For apps on an organization, the same review lives in the organization's Settings > GitHub Apps, under Third-party Access.
Slack
Slack's route runs through the workspace. Click the workspace name, then Tools & settings > Manage apps > Installed Apps, open the app's App Details > Configuration, and choose Remove App. To cut a single person's access instead, use Authorizations > Authorized members > See all > Revoke.
Slack's article doesn't say what happens to tokens on removal. By default every member except guests and Frontline Members can remove apps; with app approval on, only Workspace Owners and app managers can. In a workspace with app approval on, then, removing an app starts with a message to a Workspace Owner or an app manager.
Notion
Open Settings > Connections, select the connection or its ••• menu, and choose Disconnect. To cut one page loose, open the page's ••• menu, choose More, hover over the connection under Connections, and select Disconnect.
Notion MCP, Notion's own MCP server, has workspace controls under Settings > Notion MCP > Manage workspace clients, where admins can disconnect members and connections, and members then have to reconnect. Those controls are for Enterprise workspace owners and admins, so if you're a member, the article offers you no button of your own: ask your admin.
Layer 3: on your machine
Coding agents and Claude Desktop keep config files you can read. The files are documented. The credentials mostly aren't, and that shapes what you should do.
| Client | Config file | Scope |
|---|---|---|
| Claude Code | ~/.claude.json | Local and user servers |
| Claude Code | .mcp.json in the project root | Project servers |
| Cursor | ~/.cursor/mcp.json | Global |
| Cursor | .cursor/mcp.json | Project |
| Codex | ~/.codex/config.toml | Your user |
| Codex | .codex/config.toml | Trusted projects only |
| Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json | Local servers |
| Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json | Local servers |
| Claude Desktop (Linux) | ~/.config/Claude/claude_desktop_config.json | Local servers |
In Claude Desktop, Settings > Developer > Edit Config opens the file for you.
Open each one and look for three things:
- Servers you don't use. In Claude Code, Codex, and Cursor, remove them with the client's command or in Customize, as in layer 1, rather than by deleting lines. For Claude Desktop's local servers, edit the file through Edit Config.
- API keys in
envblocks. Local servers can carry keys there; the MCP project's own Claude Desktop example puts an API key in a server'senvblock. Any key you find, revoke or rotate in that service's dashboard, then remove the server. - A client secret in Codex config. For a pre-registered confidential client, Codex saves the secret as
mcp_servers.<name>.oauth.client_secretinconfig.toml.
Picture the API key you pasted into a config file for a weekend experiment. The experiment ended. The key didn't.
Tokens are the other half, and here the docs go quiet: none of the three clients names where its MCP OAuth tokens live. Codex does tell you how it stores them: mcp_oauth_credentials_store takes auto (the default), file, or keyring.
Don't go hunting for token files. Delete through the tool that wrote them (logout, then remove), and revoke upstream at the provider. A token file you find by guessing may not be the only one.
Keep it small from now on: one connection point
The sprawl comes from every assistant holding its own grants. Five assistants means five lists, and typically a separate grant per app for each of them. Fewer grants beats better auditing.
The general fix is one connection point between your assistants and your apps: one URL for all of them, each app connected once, scopes set per assistant, and one log of what happened. Arc0, our product, works that way:
- Connect each app once in Arc0. Start with Gmail, GitHub, Slack, Notion, or whatever you use. Your MCP endpoint is bound to you; the catalog has 1,484 apps, and one connection reaches hundreds of them.
- Add the same URL to each assistant. It works in Claude, ChatGPT, Cursor, Claude Code, Codex, VS Code, and any remote-MCP client.
- Set each assistant's scopes before you use it. Each assistant gets its own scopes on Personal, and every action is graded read, write, or destructive (scopes and actions).
- Read the audit log when something looks off. It records the calls that go through Arc0 and keeps 7 days on Personal, so read it soon rather than saving it for the monthly review (audit log).
- Disconnect an app in Arc0 when you stop using it. Disconnecting it there stops Arc0's use of that connection. Then open the provider's page and remove Arc0 if it's still listed, so the grant itself is gone too.
- Export your tokens if you ever leave. Token export works any time, on every plan (token export).
One honest limit: a connection point does not replace the provider pages. Arc0's own connection to Google, GitHub, or Slack is typically a provider grant too, so it shows on those pages, and anything you connect outside Arc0 still lives there.
Calls run server-side, and credentials never reach the agent or the model (security). So the provider credentials for the apps you connect stay server-side with Arc0 instead of sitting in each assistant. The Arc0 URL, token, or API key each assistant holds is a credential of its own, though, and it belongs in your review like any other key. Personal is free (pricing).
And the next assistant you try needs one URL, not another round of consent screens.
A monthly 10-minute review
Put a recurring date in your calendar and work in layer order. Ten minutes is a budget, not a promise.
- Check each assistant's list. Claude's Customize > Connectors, ChatGPT's Settings > Apps or Plugins, and Cursor's Customize.
- Run the coding-agent lists.
claude mcp listandcodex mcp list, thenlogoutandremoveanything you don't use. - Visit the five provider pages. Google's linked apps, Microsoft My Apps, GitHub's authorized and installed apps, Slack's Manage apps, and Notion's Connections. If you use Arc0, its own grant typically shows here too.
- Open the config files. Look for servers you removed elsewhere, keys in
envblocks, and any Arc0 URL or key an assistant no longer needs. - Review Arc0, if you use it. Disconnect any app you have stopped using there.
Cut anything you haven't used since the last review. If you can't remember what it was for, that's your answer.
If you'd rather keep one list than five, get a free personal MCP URL from Arc0, connect one app, and add the URL to your assistant with the MCP client setup guide. Next month, there are fewer lists to open.