Step 1 of 4
⚙️ Show all settings
Editing existing configuration — pre-loaded from `config.toml`.

### Google Workspace — OAuth Setup

Follow these 4 steps to generate your refresh token. You only need to do this once.

1. 1
   Enable APIs in Google Cloud Console
   Open console.cloud.google.com/apis/library, create or select a project, then enable all six APIs:
   Google Drive API, Gmail API, Google Calendar API, Google Docs API, Google Sheets API, Google Slides API.
2. 2
   Configure OAuth Consent Screen & Credentials
   Go to APIs & Services → Credentials.
   • OAuth consent screen → External → add your Google account as a Test user.
   • + Create Credentials → OAuth Client ID → Application type: Web application.
   • Under Authorised redirect URIs add exactly:
   `https://developers.google.com/oauthplayground`
   Save and copy your Client ID and Client Secret.
3. 3
   Authorise Scopes in OAuth Playground
   Open developers.google.com/oauthplayground.
   • Click the ⚙ gear icon (top-right) → tick "Use your own OAuth credentials" → paste your Client ID and Client Secret.
   • In the scope input, paste each scope below and click Add to scopes, then click Authorise APIs:
   - https://www.googleapis.com/auth/drive
   - https://www.googleapis.com/auth/gmail.modify
   - https://www.googleapis.com/auth/calendar
   - https://www.googleapis.com/auth/documents
   - https://www.googleapis.com/auth/spreadsheets
   - https://www.googleapis.com/auth/presentations
   Sign in with the Google account you added as a test user.
4. 4
   Exchange Code & Copy the Refresh Token
   After authorising, click "Exchange authorization code for tokens".
   Copy the value of Refresh token and paste it into the `GOOGLE_WORKSPACE_REFRESH_TOKEN` field below.

Missing even one scope causes 403 errors. If you see "insufficient authentication scopes", repeat from Step 3 with all six scopes included and generate a new refresh token.

### Meta Threads — Access Token Setup

Follow these 4 steps to get your long-lived access token. You only need to do this once.

1. 1
   Create a Meta Developer App
   Go to developers.facebook.com/apps and click Create App.
   Choose the Business app type, give it a name, and complete the creation flow.
2. 2
   Add the Threads API Product
   In your app dashboard, click Add Product and find Threads API.
   Click Set Up to add it to your app.
3. 3
   Configure Permissions
   Under Threads API → Permissions, request all four permissions:
   - threads_basic
   - threads_content_publish
   - threads_manage_replies
   - threads_read_replies
   Add your Instagram/Threads account as a Test User under App Roles → Roles so you can generate a token before app review.
4. 4
   Generate a Long-Lived Access Token
   Under Threads API → Access Tokens, click Generate Token for your test user account.
   Copy the token — it is valid for approximately 60 days.
   Paste it into the `THREADS_ACCESS_TOKEN` field below.
   To refresh it before expiry, use the Graph API Explorer or call the token-refresh endpoint documented in the Threads API docs.

Missing permissions cause publishing errors. If you see "permissions error" when posting, ensure all four permissions above are approved for your test user and regenerate the token.

### Notion — OAuth 2.0 Setup

Notion's official MCP server at `https://mcp.notion.com/mcp` requires an OAuth 2.0 access token, not a static integration token. Click Connect with Notion below to authorize automatically — no manual token copying needed.

1. 1
   Click "Connect with Notion"
   In the MCP Tools step, enable the notion server, then click the 🔐 Connect with Notion button that appears below it.
2. 2
   Authorize in the popup
   A Notion authorization page opens in a popup window.
   Sign in with your Notion account and click Allow access.
3. 3
   Token is filled automatically
   The popup closes and the `NOTION_TOKEN` field is populated with your OAuth access token. Save the config and you're done.

HTTP transport — no local server needed. RustFox passes the OAuth token as a `Bearer` header to `https://mcp.notion.com/mcp`. The old `@notionhq/notion-mcp-server` npm package is deprecated.