health

---
name: health
description: Reports Cowork Tasks health - which connectors are wired up, board task counts, and any errors. Use when the user asks about Cowork Tasks status or whether it is working.
---

# Cowork Tasks health

## Steps

1. Read the local task store via the MCP `list_tasks` tool with no
   `since` cursor. Note the `version` and the count by column.

2. Check which Cowork connectors are mounted in this session by listing
   available MCP tools. For each declared connector, report whether at
   least one tool is callable.

   The plugin declares these connectors in `.mcp.json`:

   - `gmail`, `google calendar`, `ms365`
   - `slack`
   - `atlassian`, `linear`, `asana`, `monday`, `clickup`, `github`
   - `notion`, `guru`
   - `fathom`, `fireflies`, `granola`, `gong`
   - `intercom`, `hubspot`, `close`
   - `pagerduty`, `datadog`
   - `box`, `egnyte`, `docusign`
   - `figma`, `canva`

3. Format as a short grouped table:

   ```
   Email/Calendar
     gmail              connected
     google calendar    connected
     ms365              not connected

   Chat
     slack              connected

   Issue trackers
     atlassian          connected
     linear             not connected
     ...

   Board: 23 active tasks (Inbox 5 / Todo 12 / In progress 4 / Blocked 1 / Done 1)
   MCP version: 47
   ```

4. If popular ones (gmail, slack, atlassian) are missing, suggest
   `/cowork-tasks:setup`.

## Constraints

- Don't fabricate status. If a tool call fails or isn't available, just
  say "not connected" - never invent uptime or error rates.
- Group connectors by category to keep the table scannable.