Broken MCP connections and expired credentials are only visible if you go check manually
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 10
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 17
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the MCP page's status column and the main dashboard entry point. Trace how broken connections and expired credentials are represented, then define completion as a dashboard attention banner plus a consolidated view showing the health of every workspace connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100