Here's what I found while triaging this issue:

This looks like an MCP OAuth regression around gallery-template updates, but the GitHub report does not include concrete reproduction details yet.

I have a few follow-up questions before I can narrow this down:

Which MCP gallery server did you update when the OAuth credentials reset?
What visible behavior indicated the OAuth reset after the update?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that the report likely concerns an MCP gallery-template update causing OAuth credentials to be invalidated or re-requested, but the GitHub issue currently lacks reproduction details beyond the Linear link..

Triage summary

This appears to be a bug in the MCP gallery/OAuth update flow, but the GitHub report is underspecified: it only links Linear APP-3774 and does not include reproduction steps or the affected gallery server.

Relevant code paths:

app/src/ai/mcp/gallery.rs refreshes gallery items from UpdateManagerEvent::MCPGalleryUpdated.
app/src/settings_view/mcp_servers/list_page.rs handles MCPServerUpdate::Gallery by creating a new template from the gallery item, preserving the existing template UUID, updating the cloud template, and reinstalling the local installation.
app/src/ai/mcp/templatable_manager/native.rs deletes and recreates local MCP installations during template updates, then respawns the server; OAuth credentials are normally looked up by template UUID.
app/src/ai/mcp/templatable_manager/oauth.rs persists OAuth credentials under the templatable MCP credential map, while the spawn failure path in native.rs deletes credentials from secure storage.

Likely root-cause area: gallery template update/reinstall plus OAuth credential reuse on server restart. The code suggests credentials should survive a normal gallery update because the template UUID is preserved, so the reset may depend on a changed gallery template/resource URL, a failed token refresh, or a failed post-update spawn that clears credentials.

Duplicate check: I enumerated all open issues and found related MCP/OAuth issues, especially #9211 (Warp requests Figma MCP OAuth every time Warp is invoked.), #8863, and #8020. None clearly describe OAuth reset specifically triggered by MCP gallery updates, and fewer than two likely duplicates were found, so this should remain a separate issue for now.

Question reasoning

Which MCP gallery server did you update when the OAuth credentials reset? — The affected gallery item determines whether this is server-specific, gallery-template-specific, or a general update/reinstall bug.
What visible behavior indicated the OAuth reset after the update? — Distinguishing a browser OAuth prompt from an auth error or disconnected server card helps determine whether credentials were deleted, refresh failed, or the updated server requested a new authorization.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Investigate MCP gallery updates causing oauth reset #9791

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions