# Disconnect & revoke

Disconnect Load Factor from Claude, ChatGPT or Claude Code, and how an admin revokes MCP access.

You can disconnect Load Factor from your AI client at any time, and your Load Factor admin can switch off MCP access for your account. This page covers both, and what happens to access that is already in use.

## Disconnect in your client

**Claude**

Open [Customize → Connectors](https://claude.ai/customize/connectors) and select Load Factor. Disconnect it to sign out, or click **Remove** (or the **⋯** menu next to Load Factor) to delete the connector.

On Team and Enterprise plans, members can disconnect their own sign-in. Removing the connector for the whole organization is done by an Owner under [Organization settings → Connectors](https://claude.ai/admin-settings/connectors).

**ChatGPT**

Open [Plugins](https://chatgpt.com/plugins), select Load Factor, and disconnect or delete it. On Business, Enterprise and Edu workspaces, an app published for the workspace is managed by the workspace admins.

**Claude Code**

These commands use the name `load-factor`. If you added the server under another name, use that name instead; `claude mcp list` shows it.

Forget the sign-in but keep the server:

```bash
claude mcp logout load-factor
```

Remove the server (add `--scope user` or `--scope project` if you added it with that scope):

```bash
claude mcp remove load-factor
```

Inside Claude Code, `/mcp` also offers **Clear authentication** for Load Factor.

To connect again later, add the connector the same way as the first time; see the [Quickstart](https://loadfactorenergy.com/developers/mcp/quickstart).

## When an admin switches off access

Your Load Factor admin can switch off MCP access for your account at any time. The change applies within seconds, even in a conversation that is already connected: the next request is refused, and your client can no longer renew its sign-in. Blocking your Load Factor account or ending your access window has the same effect.

If your Load Factor sessions are revoked (for example, an admin signs you out everywhere), your current connection stops working. Disconnect and connect again to sign in afresh.

## What stays

Disconnecting stops new requests. The record of requests you already made stays with Load Factor; see [Privacy & request logging](https://loadfactorenergy.com/developers/mcp/privacy-and-logging).
