💡 Conversational OAuth: Avatar-Guided MCP Service Connections

[github-actions[bot]]

Summary

The avatar guides non-technical users through connecting external services (Figma, Slack, Asana, GitHub) via MCP's OAuth 2.1 flow, explaining WHY access is needed and making the auth process feel like a natural conversation rather than a technical configuration step. This is a foundational enabler for all external integrations.

Market Signal

MCP's 2026 specification release candidate adopted OAuth 2.1 as the standard authorization mechanism. MCP Apps launched (January 2026) with 9 partners — Figma, Asana, Slack, Box, Canva, monday.com, and others — all requiring OAuth connections. The MCP ecosystem has grown to 5,000+ servers, many requiring authentication. Every major AI platform (Claude, ChatGPT, Codex) now supports MCP, but none guide non-technical users through service connections conversationally. The gap between "OAuth is technically available" and "a non-technical user can actually connect a service" remains wide.

User Signal

TalkTerm's Epic 11 (External System Writeback, FR48-FR56) and existing ideas like Enterprise Connector Hub (#230) and Conversational MCP Onboarding (#66) all depend on users successfully connecting to external services. For non-technical users, OAuth flows are a major friction point — they don't understand why an app needs access, what "scope" means, or whether clicking "Allow" is safe. This is the gate that blocks all external integrations for TalkTerm's primary persona.

Technical Opportunity

Electron can handle OAuth redirect flows via BrowserWindow (in-app browser) or shell.openExternal + custom protocol handler (talkterm://oauth/callback). The preload bridge (contextBridge) can expose a secure auth state manager. MCP OAuth 2.1 standardizes the flow across all servers, reducing per-service implementation to configuration. The avatar's confirm-plan pattern (FR20) already provides a natural interaction gate: "I need to connect to your Figma to pull design files. I'll open a browser — just click Allow."

Assessment

Dimension	Score	Rationale
Feasibility	high	Electron supports OAuth flows natively; MCP OAuth 2.1 standardizes the protocol; avatar narration uses existing confirm-plan UX
Impact	med	Foundational enabler — unlocks MCP Apps, Enterprise Connector Hub, writeback, and every external integration
Urgency	high	MCP Apps are live with 9 partners NOW; without conversational auth, TalkTerm's non-technical users can't access any of them

Adversarial Review

Strongest objection: OAuth is a solved engineering problem. Adding avatar narration to an auth flow is over-engineering. Enterprise SSO/SAML adds complexity that a conversational interface can't simplify.

Rebuttal: The engineering isn't hard — the UX is. Non-technical users abandon OAuth flows because they don't understand what they're approving or why. The avatar provides context ("I need Figma access because your design files are there") and reassurance ("I can only see your projects, not change anything"). This is foundational: without conversational auth, MCP Apps, Enterprise Connector Hub, and all external integrations remain gated behind a technical barrier that excludes TalkTerm's primary persona. Start with standard OAuth 2.1; enterprise SSO is a later enhancement.

Suggested Next Step

Implement: design the OAuth flow UX with avatar narration states (requesting → browser-open → waiting → connected → confirmed). Start with GitHub OAuth as proof-of-concept since it is well-documented and the workspace is already Git-aware (FR52).