The Retool MCP server currently only supports OAuth 2.0 authentication. While OAuth works fine for interactive clients, it creates friction for headless/automated setups:
- Access tokens expire after 2 hours
- Refresh requires browser-based OAuth flow
- No way to use a static API token (Settings > API) with the MCP endpoint
We ended up using mcp-stdio as a local OAuth proxy, but even that requires an initial browser auth.
Question: Is there any plan to support Retool API tokens as an alternative auth method for the MCP endpoint? This would make CI/CD and headless agent setups much simpler.
Related: Claude Code users face the same issue (anthropics/claude-code#65036).