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
ChatGPT plugin: one public MCP URL on the cloud root domain (workspace-independent OAuth clients + root-domain discovery)
0 votes · 0 comments
ChatGPT plugin, step 2: inline UI cards via MCP Apps (document list and document preview)
0 votes · 0 comments
ChatGPT plugin, step 1: make the MCP server plugin-ready (securitySchemes, profile tool, structuredContent, manifest)
0 votes · 0 comments
Support OAuth Client ID Metadata Documents (CIMD) for MCP clients
0 votes · 0 comments
No comments yet.