feat: User Session and Authorization Management for MCP Servers #359
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add Okta as social authentication provider with OKTA_ISSUER support - Add Google/Microsoft force account selection flags - Respect DISABLE_EMAIL_SIGN_IN and DISABLE_SIGN_UP environment variables - Update OAuth documentation with Okta setup and configuration options - Implement secret tainting for enhanced security
This PR introduces User Session and Authorization Management for MCP servers, enabling per-user authentication isolation and governance for MCP tool access. Key Changes: - Added userSessionAuth toggle to MCP server configuration for per-user session isolation - Integrated Okta as identity provider with support for both Authorization Server and Org Authorization Server modes - Extended database schema with userId tracking in mcp_oauth_session table - Added toolCallWithUserAuth() method for user-context-aware tool execution - Created inline authentication prompt UI for seamless in-chat authorization flow Impact: - Each user maintains isolated OAuth sessions per MCP server - User access tokens are properly relayed to MCP tools for downstream authorization - Administrators can enable/disable authentication requirements per MCP server - Supports enterprise Okta deployments without API Access Management feature
|
@Aveerayy is attempting to deploy a commit to the cgoinglove's projects Team on Vercel. A member of the Team first needs to authorize it. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces User Session and Authorization Management for MCP servers, enabling per-user authentication isolation and governance for MCP tool access. When enabled, each user maintains their own OAuth session per MCP server, ensuring proper access control and session isolation.
Key Changes
userSessionAuthfield to MCP server configuration allowing administrators to enable per-user session isolationmcp_oauth_sessiontable withuserIdtracking and added new indexes for efficient user-scoped queriestoolCallWithUserAuth()method that checks user authentication status before executing MCP toolsMcpAuthRequiredCardcomponent for seamless in-chat authorization prompts when tools require authenticationImpact & Benefits
Configuration
To enable User Session Authorization for an MCP server:
Files Changed
src/lib/db/pg/schema.pg.ts- Schema extensions for user session trackingsrc/lib/ai/mcp/- OAuth provider and client manager updatessrc/app/api/mcp/user-oauth/- New API routes for user OAuth flowsrc/components/mcp-editor.tsx- UI for configuring user session authsrc/components/mcp-auth-required-card.tsx- Inline auth prompt componentsrc/lib/auth/- Okta configuration with Org Authorization Server support