Overview
Provides a step-by-step guide for connecting the Drive·Notion·Higgsfield 3 connectors to Cowork. It covers the entire setup process, from the authentication flow, API key entry, and single-call verification to troubleshooting.
Setup Completion Checklist Drive·Notion·Higgsfield — Authentication success + single-call success (Drive: folder list / Notion: shared page read / Higgsfield: model list)
Trigger Keywords
MCP connector connection, Drive authentication, Notion Integration Token, Higgsfield API key, 3-connector installation, computer:// link, MAX_PATH error, Korean filename error, OAuth redirect URI
Workflow
Step 1 — Prerequisites
Create the accounts below in advance before connecting the connectors:
- Google account (Drive)
- Notion account
- Higgsfield account + workspace credit top-up
[HARD] API Key Security Rules: API keys are issued and stored by you personally. Do not paste the raw key into chat conversations or shared documents; enter it only in the API Key field of the connector settings screen.
Connector A — Google Drive
Purpose: Cowork folder mount + file access (drive.readonly, drive.file permissions)
Authentication Method: Cowork app → Add connector → Google Drive → OAuth login
Required Permissions
drive.readonly— File readingdrive.file— Access to files created by Cowork
Authentication Steps
- Cowork app → Settings → MCP connector → Select Google Drive
- Click "Connect with Google account"
- Select account + allow permissions on the Google OAuth screen
- After connection is complete, verify with a single Drive folder list call
Single-Call Verification: Success if the folder list appears in the response
Connector B — Notion
Purpose: Read and write Notion pages for work outputs
Authentication Method: Cowork app → Add connector → Notion → OAuth authentication
Authentication Steps
- Cowork app → Settings → MCP connector → Select Notion
- Click "Connect with Notion"
- Select workspace + allow page access permissions on the Notion OAuth screen
- After connection is complete, verify with a single shared page read call
Single-Call Verification: Success if the shared page content appears in the response
Connector C — Higgsfield
Purpose: Media tasks such as ad video generation (calling image/video generation models)
Authentication Method: API key method (not OAuth)
Pre-checks
- Check whether the Higgsfield workspace credits have been topped up (if the balance is insufficient, generation calls may fail even if authentication succeeds)
- Estimating expected usage: Check credit consumption in advance for one video (5-10 seconds)
- Cost limit: Set a usage limit in workspace settings to prevent unexpected charges
Authentication steps
- Cowork app → Settings → MCP Connector → Select Higgsfield
- Enter the issued key in the API Key field (issuer: higgsfield.ai → API Keys)
- After connection is complete, verify by calling the model list once
Verify with one call: If the list of available models appears in the response, it is successful
Troubleshooting
T1 — Windows MAX_PATH 260-character exceeded error
Symptoms: Cowork folder mount failure, path-related error message
Cause: Windows default MAX_PATH 260-character limit. Frequently occurs with long paths that include Korean filenames.
Solution
- Move the folder to a location close to the drive root (e.g.,
C:\cowork\orD:\cw\) - Korean filename 30-character rule: Keep folder names and filenames within 30 characters
- If necessary, remove the MAX_PATH limit via Windows Registry (administrator privileges required)
If difficult to resolve (alternative path): If the above methods do not resolve it, you can use a temporary path to access files via the Google Drive connector (Connector A) instead of mounting a local folder.
T2 — computer:// link does not open
Symptoms: Even when clicking the computer:// link provided by Cowork, it does not open
Solution
- Retry in Chrome incognito mode
- Check the browser default protocol handler (Settings → Default apps → Link handling)
- Retry after restarting the Cowork app
T3 — OAuth authentication failure (Drive·Notion)
Symptoms: "Access denied" or redirect error on the OAuth screen
Solution
- Retry in Chrome incognito mode (prevents cached session conflicts)
- If the Google account is a workspace account: Administrator approval may be required
- OAuth redirect URI issue: Retry after updating the Cowork app version
- Check that pop-up blocking is disabled (Browser settings → Allow pop-ups)
T4 — API key authentication failure (Higgsfield)
Symptoms: "Invalid API key" or "Unauthorized" error
Solution
- Check that the API key is copied and pasted exactly, with no leading or trailing spaces
- Higgsfield: Check whether the workspace is funded (authentication fails if the balance is insufficient)
- Reissue the key and retry
Slash command registration guide
After completing connector setup, registering slash commands like the following in the project CLAUDE.md allows you to quickly invoke frequently used skills:
## 슬래시 커맨드
- `/morning-brief` — 아침 브리핑 (commerce-morning-brief)
- `/detail-copy` — 상세페이지 카피 (detail-page-copy)
- `/channel-msg` — 채널 메시지 (commerce-channel-message)
In the project folder's CLAUDE.md, paste the above block to register it.
Pre-check checklist (--check option)
This option checks the sign-up and authentication status of the 3 connectors based on the prerequisites.
/mcp-connector-setup --check
Output example:
[✅] Google Drive — 계정 확인 완료
[✅] Notion — 계정 확인 완료
[⚠️] Higgsfield — 워크스페이스 크레딧 충전 미확인 (충전 후 재시도)
Usage example
Example 1
"Tell me how to connect Drive MCP"
→ Provide Connector A (Google Drive) authentication steps + guidance for one-call verification
Example 2
"Cowork mount doesn't work on Windows"
→ Provide solution for T1 (MAX_PATH error) + guidance on alternative paths
Output format
- Step-by-step authentication guide (Markdown)
- Troubleshooting solutions (numbered list)
--checkOption: 3-connector status checklist (.mdfile can be saved)
Setup completion checklist
| Connector | Authentication method | One-call verification |
|---|---|---|
| Google Drive | OAuth (drive.readonly, drive.file) | Folder list response |
| Notion | OAuth (workspace connection) | Shared page read response |
| Higgsfield | API Key | Model list response |
If all 3 connectors are successfully authenticated + one call succeeds, setup is complete.
Related skills
moai-commerce:commerce-morning-brief— After authentication is complete, morning briefing of store data + integrated summary of new orders (order summary mode)moai-media:higgsfield-image/moai-media:higgsfield-video— After Higgsfield connector authentication is complete, image/video generation
When not to use this skill
- If all 3 connectors are already connected →
moai-commerce:commerce-morning-briefCall directly (full briefing or order summary mode) - If the purpose is to generate MCP call results (morning briefing/order summary) →
moai-commerceUse skill - If the Cowork app itself cannot be installed → Contact Cowork official support channel (outside the scope of this skill)
- Connecting an advertising platform connector (Meta Ads, etc.) →
moai-marketing:meta-ads-managerRefer to skill