> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superdata.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Update or remove

> Update the Superdata plugin, rotate credentials, disconnect a client, or remove the integration.

Use the least disruptive action that solves the problem. Updating a plugin does
not require revoking a healthy credential, while removing a machine or exposed
secret should include revocation.

## Update Superdata

<Tabs>
  <Tab title="Codex">
    Update the Superdata plugin through the Codex plugin manager, then fully
    quit and reopen the desktop app or start a new CLI session. Reauthenticate
    only if the connection asks you to sign in again.
  </Tab>

  <Tab title="Claude">
    Update Superdata from **Customize → Plugins** in Desktop or Cowork. In
    Claude Code, update the installed plugin and run `/reload-plugins` before
    checking `/mcp`.
  </Tab>

  <Tab title="Other clients">
    Keep the MCP endpoint at `https://api.superdata.so/mcp`, update the client
    normally, restart it, and verify that it can list the Superdata tools.
  </Tab>
</Tabs>

## Rotate an API key

1. Open **Connections** in Superdata.
2. Create a replacement key with a name that identifies its client.
3. Copy and store the complete secret while it is visible.
4. Replace the old credential in the client and verify a tool call.
5. Revoke the old key from its action menu.

Revocation is immediate and cannot be undone. The complete secret for an
existing key cannot be recovered.

## Disconnect OAuth

Remove or disconnect Superdata from the client's connection settings. If you
plan to reconnect, restart the client and complete browser sign-in again with
the Superdata account that should own the usage.

## Remove the integration

1. Uninstall or disable the Superdata plugin in every client where it is used.
2. Remove direct MCP server entries from other clients.
3. Revoke API keys that are no longer needed.
4. Delete local environment variables or secret-manager entries after
   confirming they are unused.
5. Restart the client and confirm that Superdata tools are no longer listed.

<Warning>
  Do not post a credential in a support request. If exposure is possible,
  revoke it first and share only the key's safe display name and approximate
  last-used time.
</Warning>

If the client still shows stale tools after an update or removal, follow
[Troubleshooting](/help/troubleshooting).