Error text / 报错原文
OAuth flow does not startNot authorizedLogin required
What it means
The app or remote MCP server reports an auth requirement, but ChatGPT does not launch the expected OAuth flow.
Most common causes
- Missing or invalid auth metadata
- Tool was not marked with the expected security scheme
- Callback URL or client registration mismatch
- Developer Mode session cached stale app metadata
Fastest fix
- Reproduce the smallest failing case outside the agent.
- Confirm auth, session, and transport before changing app code.
- Disable unrelated tools or servers and retry once.
- Capture the exact timestamp, client version, and raw error text.
Safe fix
- Keep secrets in environment variables or the platform secret store.
- Use least-privilege scopes and read-only tools by default.
- Add validation around manifests, schemas, and callback URLs.
- Document the working local and production configuration.
What not to do
- Do not paste OAuth tokens or session IDs into public logs.
- Do not bypass TLS, CSP, or permission prompts as a permanent fix.
- Do not enable every MCP tool globally just to make one task pass.
Diagnostic commands
node --version curl -I "$MCP_SERVER_URL" echo "$OAUTH_CLIENT_ID"