2
Allow configurable session expiration for MCP server authentication
Source: outline/outline#11832 · opened by @TheophileDiot
Description: Hi team, I’d like to propose a feature that would allow configuring the session expiration duration for the MCP server. Currently, the session lifetime appears to be quite short, which leads to frequent reauthentication. This becomes disruptive, especially in workflows involving persistent or long-running interactions with the MCP server. Proposed improvement: Add a configurable setting for session expiration directly in the MCP settings page. This would make it easily accessible and manageable from the UI without requiring manual configuration changes. Use case: In development or controlled environments, longer-lived sessions would reduce friction and improve productivity by minimizing repeated authentication steps. Additional considerations: • Keep a secure default value. • Optionally define a maximum allowed duration. • Provide clear UX indications about security implications of longer sessions. Question: Is this something…
No pledges yet. Be the first to back this.
Comments
Similar requests
Add admin controls for MCP tools when using OAuth
3 votes · 0 comments
Add `get_attachment` MCP tool for downloading attachment content
2 votes · 0 comments
MCP — support end-to-end attachment upload (not just presign) so clients don't need a separate API key
1 vote · 0 comments
Feature Request: Support @user mentions and integration mentions when creating/updating documents via MCP
1 vote · 0 comments
Official Outline MCP Server
3 votes · 0 comments
No comments yet.