Support OAuth-based MCP connections

[malhotra5]

Feature Request: Support OAuth-based MCP connections

Problem

Currently, connecting to MCP services like Slack and Notion requires users to manually provide API keys or tokens. This is friction-heavy compared to the OAuth-based authentication experience available in other applications (e.g., Claude App, which uses OAuth to authenticate with official MCP servers).

Proposed Solution

Add support for OAuth-based MCP connections, allowing users to authenticate with official MCP providers (Slack, Notion, etc.) using OAuth flows rather than manual token entry.

User Experience Goal

Similar to how you can "Log in with OAuth" to grant Claude access to Slack or Notion, users should be able to:

1. Navigate to the MCP settings page in agent-canvas
2. Click "Connect" on an official MCP provider (Slack, Notion)
3. Be redirected through the provider's OAuth flow
4. Return to agent-canvas with the connection established

Benefits

• Reduced friction: No need to manually generate/copy API tokens
• Better security: OAuth tokens are managed by the provider, not stored directly
• Familiar UX: Matches what users expect from other MCP-capable applications
• Automatic token refresh: OAuth handles token lifecycle

Scope Considerations

• Focus on official MCP integrations (Slack, Notion) first
• Custom stdio MCP servers would remain token-based
• Consider supporting the MCP OAuth spec as defined by the MCP spec

References

• MCP Protocol OAuth documentation: https://modelcontextprotocol.io/
• Similar implementations in Claude, Cursor, and other MCP-compatible applications