MCP connections stopped working
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 2.1k
- Forks
- 153
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
MCP connections stopped working
While running an automation (doesn't work on normal chat either). Other connections are also down (slack, etc) although they are reported as healthy in settings under mcp servers.
```
{
"entityUrls": "[\"/me/calendarView?startDateTime=2026-07-11T16:19:28Z&endDateTime=2026-07-25T16:19:28Z&$select=id,subject,start,end,isAllDay,showAs,isCancelled,categories,responseStatus,sensitivity&$top=200\"]"
}
Tool 'workiq-fetch' does not exist.
```
It shows up okay and connected in settings though.
---
| Field | Value |
| --- | --- |
| App version | 1.0.21 |
| OS | macOS 26.5.2 |
| Theme | GitHub |
| Path | /workflows |
| Tenure | Week 4 |
Beitragsleitfaden
Rechercherichtung
Reproduce the failure in app version 1.0.21 on macOS, using both a normal chat and an automation. Compare the MCP servers shown as healthy in Settings with the available tools, especially the missing workiq-fetch tool; done means MCP connections such as WorkIQ and Slack remain usable and their tools are available.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- macos
- Bereich
- desktop
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100