Security / Authentication
Authentication with clear intent.
IncidentFlow uses a browser-based authorization step so the person connecting an AI client can review the access path before work begins.
Access path
- 01AI client
- 02Browser authorization
- 03Workspace
- 04Production integrations
Authorization flow
A browser step keeps the connection understandable.
- 01
Start from your AI client
Add the IncidentFlow remote MCP server to a supported client.
- 02
Authorize in the browser
Complete browser-based authorization before the client can use the connection.
- 03
Choose the workspace
Continue with the workspace and integrations intended for the investigation.
Authorization is an operational checkpoint: the connection starts in your AI client and continues only after the browser-based step is complete.