Add OAuth Support for MCP Connections in Chainlit

[vignesh69420]

trafficstars

Add OAuth Support for MCP Connections (ServiceNow, Confluence, etc.)

Description Problem Statement Currently, Chainlit's MCP connection UI only supports basic authentication methods, requiring users to manually enter credentials (username/password or API tokens) for each connection. This creates several issues:

Security Concerns: Sensitive credentials are being entered directly into the UI Poor User Experience: Users need to re-enter credentials for each session Limited Enterprise Integration: No support for modern authentication standards used in enterprise environments Credential Management: No secure way to store or refresh tokens Specific Examples ServiceNow MCP: Currently requires entering username/password or passing them as URL parameters Confluence/JIRA MCP: Requires API tokens to be manually entered or passed in URL parameters Other OAuth-capable services: Cannot leverage their built-in OAuth capabilities Proposed Solution Implement OAuth support for MCP connections in Chainlit, with the following features:

OAuth Flow Integration: Add support for standard OAuth 2.0 authorization code flow Token Management: Securely store and refresh OAuth tokens Connection Persistence: Allow users to maintain authenticated connections across sessions UI Improvements: Add OAuth login buttons for supported services Configuration Options: Allow developers to configure OAuth settings in the Chainlit config