Flare has switched its MCP client, CLI, and API connections from broad, long-lived tokens to OAuth-based authentication. The new flow supports scoped permissions, including read-only and project-level access control, and centralizes management of all connections in one place, while also simplifying initial setup.
Questions this post answers
How does Flare handle authentication for MCP clients now?
Flare now uses OAuth instead of broad, long-lived tokens to authenticate MCP clients, the CLI, and the API. The OAuth flow supports scoped permissions, including read-only access and project-level restrictions, and centralizes management of all connections in one place, replacing the previous token-based setup. Track how tools like Flare adopt OAuth over static tokens by following authentication changes on daily.dev.