MCP OAuth Issues

# Seats.aero MCP OAuth authentication does not initiate / refresh in BoltAI

## Environment

- macOS: 26.6.2

- BoltAI: 2.18.3

- MCP endpoint: https://seats.aero/mcp

## Issue

BoltAI detects the Seats.aero remote MCP server and initially loads its public tool set, but it does not successfully initiate or complete OAuth authentication for the Pro account.

The native Connector initially appears to run and shows 8 tools, but after roughly one minute it changes to this error:

“Authentication for this connector needs to be refreshed on this Mac. Please authenticate again.”

Selecting Reset Authentication… does not open a browser, embedded authorization window, or any visible OAuth sign-in flow. The same error returns.

## Expected behavior

Selecting Reset Authentication, or invoking a Seats.aero capability that requires Pro authentication, should start the browser-based OAuth authorization flow. After authorization, the connector should expose the authenticated Seats.aero Pro tool set and permissions.

## Actual behavior

- BoltAI remains on the public/anonymous Seats.aero tool set (8 tools).

- It never presents an OAuth login page.

- It eventually reports that authentication needs to be refreshed.

- It cannot access Pro-only long-range award searches, live searches, alert management, etc.

## Bridge test

I also tried configuring Seats.aero through mcp-remote as a local stdio MCP server:

```json

{

"mcpServers": {

"seats-aero-pro": {

"command": "/opt/homebrew/bin/npx",

"args": [

"-y",

"mcp-remote@latest",

"https://seats.aero/mcp",

"--debug"

"boltai": {

"enabled": true

}

```

mcp-remote connects successfully but remains anonymous and does not initiate a browser login. Its diagnostic output shows that it discovers Seats.aero’s authorization server and lists the public tools successfully:

```text

Using callback port derived from the server URL: 27031

Discovering OAuth server configuration...

Discovered authorization server: https://seats.aero

Connecting to remote server: https://seats.aero/mcp

Connected successfully!

Requesting tools list...

```

The public Seats.aero tools advertise both noauth and OAuth security schemes. My inference is that, because the server permits unauthenticated access to public tools, BoltAI / mcp-remote does not proactively initiate OAuth to upgrade the connection to the authenticated Pro scope.

## Control test: Seats.aero OAuth works in Claude Code

The same Seats.aero account authenticates successfully in Claude Code using Seats.aero’s documented commands:

```bash

claude mcp add --transport http --scope user seats-aero https://seats.aero/mcp

claude mcp login seats-aero

```

That launches OAuth successfully and yields 26 Seats.aero tools, including Pro-only capabilities. BoltAI only sees 8 anonymous/public tools.

This suggests the issue is specific to BoltAI’s remote MCP OAuth initiation, refresh, or token handling—not the Seats.aero account, endpoint, or macOS browser setup.

## Request

Could you please advise whether BoltAI supports forcing OAuth authorization for a remote MCP server that advertises both anonymous and OAuth security schemes?

If so, what is the correct configuration or UI flow? If not, please consider this a bug/feature request:

> Reset Authentication should reliably launch the provider’s OAuth authorization flow, and BoltAI should be able to upgrade an MCP connection from anonymous access to authenticated OAuth access.

I can provide sanitized BoltAI Console logs, the connector screenshot, and the full mcp-remote --debug output if useful.

```