2
MCP: Allow API-key auth other than just OAuth
Source: outline/outline#11797 · opened by @bottledpills
OAuth tokens expire every 60 minutes and require a browser to authenticate. For headless servers, automations, and stability over long term, only allowing OAuth doesn't make sense. MCP servers are unstable enough, letting it expire every hour is a bad idea, and having to script the auth refresh call via cron or similar tools is just a bad workaround. Third-party MCP Outline servers already support API keys and are far more stable than the official one. The current implementation makes it unusable in production environments.
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
Allow configurable session expiration for MCP server authentication
2 votes · 0 comments
Official Outline MCP Server
3 votes · 0 comments
No comments yet.