Reconnect SheetBase OAuth

SheetBase has moved interactive MCP authorization to the stable Better Auth OAuth Provider.

As part of this security migration, old OAuth clients and tokens are intentionally invalidated. Interactive clients such as Claude, Cursor, or ChatGPT must connect to SheetBase again once.

Your SheetBase user remains. Your connected Google account remains. Existing API keys remain and continue to work. Spreadsheet data is not affected.

Reconnect

1. Open your MCP client’s connector or server settings.

2. Remove the existing SheetBase OAuth connection.

3. Add SheetBase again using this exact endpoint:

   https://sheetbase.flonest.app/api/mcp

4. Complete the browser sign-in.

5. Review the requesting client and choose Allow.

6. Return to the MCP client and run a harmless check such as listing available tools or spreadsheets.

Do not use beta.sheetbase.flonest.app, an old Vercel preview address, or an /api/auth/mcp/ URL.

API-key clients

No reconnect is required when a script or client uses an existing x-api-key. API keys are not replaced by this OAuth migration.

Never paste an API key into the OAuth setup screen. OAuth clients should use the endpoint above and complete the browser flow.

When reconnect does not complete

Try these steps in order:

1. Confirm the endpoint is exactly https://sheetbase.flonest.app/api/mcp.
2. Remove the incomplete SheetBase connection from the MCP client.
3. Sign out of https://sheetbase.flonest.app/dashboard, then sign in again.
4. Add the SheetBase connection again and approve the new consent request.
5. Confirm the Google account shown in the dashboard is the account that owns or can access the spreadsheets you need.

A reconnect creates a fresh OAuth client and fresh tokens. It does not create a new SheetBase user and does not delete API keys.