You haven't loaded a token. Either:
- Run
wolai_use <profile>(after defining profiles in~/.wolai/tokens.env), or export WOLAI_MCP_TOKEN="sk-..."directly.
The current token's wolai App is not added as a collaborator on any top-level page.
Fix: in wolai, open the target top-level page (or the entire space if your plan supports it) → 分享 / Share → add the MCP App as a collaborator.
The page exists, but the current token's App can't see it.
Fix: same as above — add the App as a collaborator on that specific page or its ancestor.
Tool name mismatch. The actual MCP exposes *_doc / *_docs (e.g. list_docs, create_doc), not *_page / *_pages. Check wolai_tools for the live list.
curl got HTML (login page) or got rate-limited.
- Verify token:
echo $WOLAI_MCP_TOKEN | head -c 8 - Check rate-limit status: 429 means slow down.
GUI applications launched from Finder do not read ~/.zshrc. To make the token visible to GUI apps (e.g. Claude Code desktop), use:
launchctl setenv WOLAI_MCP_TOKEN "sk-..."This persists for the current login session. For a permanent solution, create a launch agent:
mkdir -p ~/Library/LaunchAgents
cat > ~/Library/LaunchAgents/com.user.wolaienv.plist <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key><string>com.user.wolaienv</string>
<key>ProgramArguments</key>
<array>
<string>/bin/launchctl</string><string>setenv</string>
<string>WOLAI_MCP_TOKEN</string><string>sk-YOUR-TOKEN</string>
</array>
<key>RunAtLoad</key><true/>
</dict>
</plist>
EOF
launchctl load ~/Library/LaunchAgents/com.user.wolaienv.plistpip3 install -r python/requirements.txtThe token belongs to an App that's been added but lacks the right role on the page. Re-share with at least "read" or "edit" role.
Define it in ~/.wolai/tokens.env:
export WOLAI_TOKEN_<UPPERNAME>="sk-..."Then source ~/.wolai/tokens.env (or open a new shell).