Freek Van der Herten1 min readintro
Flare now uses OAuth for MCP, the CLI, and API
Summary
Flare has replaced its legacy token‑based authentication with OAuth for its MCP clients, CLI, and API, introducing scoped permissions and a unified management UI. The change simplifies setup and enables fine‑grained read‑only or project‑level access.
- Flare switched from long‑lived tokens to OAuth for MCP, CLI, and API access.
- OAuth scopes provide read‑only and project‑level permissions.
- Setup is faster because credentials are managed centrally.
- All connections are now managed from a single place in the Flare UI.
Anyone integrating with Flare needs to update their authentication flow to use OAuth and can now enforce tighter permission boundaries.
4/10





