Source: Quick-sync-up-AgentZ call, 20 Jul 2026 (Atharva Shah, Murtaza Udaipurwala, Rahul Jadhav)
Suggested labels from the call: mcp ux p1
This is closely related to the notification bell idea from the same call, but it's specifically about connection health rather than run failures. Right now, if an MCP connection breaks or a credential expires, nothing surfaces that anywhere except the MCP page's status column, and only if you happen to go look. Credentials in particular tend to expire quietly, with no warning before or after.
The fix. Add a banner on the main dashboard whenever something in the workspace needs attention, and build a consolidated view where you can see the health of every connection at a glance instead of checking them one at a time. This pairs naturally with the notification bell idea, since they're both about surfacing problems the user isn't actively looking for.
Source:
Quick-sync-up-AgentZcall, 20 Jul 2026 (Atharva Shah, Murtaza Udaipurwala, Rahul Jadhav)Suggested labels from the call:
mcpuxp1This is closely related to the notification bell idea from the same call, but it's specifically about connection health rather than run failures. Right now, if an MCP connection breaks or a credential expires, nothing surfaces that anywhere except the MCP page's status column, and only if you happen to go look. Credentials in particular tend to expire quietly, with no warning before or after.
The fix. Add a banner on the main dashboard whenever something in the workspace needs attention, and build a consolidated view where you can see the health of every connection at a glance instead of checking them one at a time. This pairs naturally with the notification bell idea, since they're both about surfacing problems the user isn't actively looking for.