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

# ultra reconnect

> Re-authenticate an OAuth MCP server from the terminal

Re-authenticate one configured OAuth MCP server from the terminal. This is the CLI equivalent of the [`ultra_reconnect`](/getting-started/ultra-mcp-tools#ultra_reconnect) tool — useful when you're working in a terminal or your MCP client can't surface the in-app [Reconnect](/getting-started/mcp-app#reconnecting-a-server) link.

## Usage

```bash theme={null}
ultra reconnect <server>
```

The `<server>` must be an enabled HTTP upstream that authenticates with OAuth.

## How It Works

1. Resolves `<server>` to a configured, enabled HTTP upstream
2. Opens your browser to sign in, and always prints the authorize URL as a headless fallback
3. Waits for you to finish signing in (press `Ctrl+C` to cancel)
4. Saves the new token to Ultra's shared credential store

Because the CLI can't refresh a client that is already running, **restart your MCP client** (or `ultra start`) afterward so its Ultra gateway process loads the new token.

## Examples

```bash theme={null}
# Re-authenticate an OAuth server after its sign-in expired
ultra reconnect notion
```

<Note>
  `ultra reconnect` only applies to OAuth servers. If the server authenticates with a token or API key instead, update its credential with `ultra config set-token <server>` (see [Authentication](/configuration/upstream-servers#authentication)). Ultra returns a clear error if the server is unknown, disabled, uses stdio transport, or doesn't use browser-based OAuth.
</Note>