Hive

@Hive show me all open actions in the Q1 Launch project that are overdue or due this week

Found 7 open actions in Q1 Launch matching your criteria. 3 are overdue: 'Finalize pricing page copy' (due Jan 15, assigned to Sarah), 'Complete API integration tests' (due Jan 17, assigned to Marcus), and 'Submit App Store screenshots' (due Jan 18, unassigned). 4 are due this week: 'Review legal terms' (due Jan 23), 'Schedule launch webinar' (due Jan 24), 'Prepare support docs' (due Jan 25), and 'Final QA pass' (due Jan 26). All actions include assignee names, due dates, and current status from your Hive workspace.

This example demonstrates list-and-filter capabilities using date ranges and project scope. Requires read access to the workspace. The MCP returns action metadata (assignees, dates, status) but does not fetch full descriptions or comments—useful for quick triage, less so for deep context on each task.

@Hive create an action called 'Draft release notes for v2.3' in the Marketing project, assign it to Jordan, and label it 'Content' with a due date of February 5

Created action 'Draft release notes for v2.3' in the Marketing project. Action ID: act_8x3k9m2p. Assigned to Jordan Chen with due date February 5, 2025. Applied label 'Content' (existing label ID lbl_4n7q). The action is now visible in your Hive workspace under Marketing and will appear in Jordan's action list. No description or attachments were added; you can edit those details directly in Hive.

This write example shows task creation with assignment, labeling, and scheduling in one prompt. Requires write permissions in the workspace. The MCP confirms the action was created but does not validate whether Jordan has workspace access or whether the label color matches your intent—verify assignments in Hive if team membership is fluid.

@Hive list all projects with 'Design' in the name, then summarize how many open actions each one has and flag any that haven't been updated in over 30 days

Found 4 projects matching 'Design': Design System Refresh (12 open actions, last updated 3 days ago), Mobile App Design (5 open actions, last updated 8 days ago), Brand Design Guidelines (2 open actions, last updated 47 days ago—flagged as stale), and Design Ops Tooling (archived, 0 open actions). Brand Design Guidelines shows low recent activity; consider reviewing whether those 2 actions are still relevant or need reassignment. The other active projects have recent updates and healthy action counts.

This synthesis example pairs Hive's project and action listing with AI reasoning to surface stale work. The MCP provides raw counts and timestamps; the AI interprets staleness. Useful for portfolio health checks, but 'last updated' reflects any field change (not necessarily meaningful progress)—combine with manual review for accuracy.

When Hive MCP wins for agency project handoffs

A 6-person creative agency runs three client projects in parallel, each with its own Hive project and color-coded labels for deliverable type. The team uses Switchy to hand off tasks during weekly check-ins: the account lead asks the AI to pull all actions tagged 'design-review' due this week, reassign two to the junior designer, and create follow-up actions for client feedback rounds. The MCP's label and project filters make this fast. The trade-off: Hive's action hierarchy isn't exposed in list results, so if your team nests tasks more than one level deep, you'll need to fetch actions individually to see parent-child structure. If your handoff ritual is under 20 tasks per session and you rely on labels more than subtasks, this MCP closes the loop in one conversation.

Using Hive MCP to archive completed sprint work

A 4-person product team wraps two-week sprints in Hive and wants to bulk-archive completed actions without clicking through the UI. At retro, the PM asks Switchy to list all actions in the 'Sprint 12' project with status 'complete', then soft-delete the ones marked 'spike' or 'research'. The MCP's delete tool respects Hive's soft-delete semantics, so nothing is permanently lost. The catch: the MCP doesn't expose bulk operations or batch endpoints, so deleting 40 actions means 40 sequential tool calls. If your sprint closes with fewer than 15 actions to clean up, the MCP saves five minutes of UI work. Beyond that threshold, the API rate limits and latency make the Hive web app faster.

When Hive MCP helps customer success standardize labels

A 3-person customer success team uses Hive to track support requests, but label sprawl has created duplicates like 'bug', 'Bug', and 'bug-report'. The CS lead uses Switchy to list all workspace labels, identify the duplicates, and delete the redundant ones in a single session. The MCP returns label IDs and color codes, so the AI can surface conflicts the team didn't notice. The limitation: the MCP can't bulk-retag actions when you delete a label, so if 'Bug' was applied to 30 actions, you'll need to manually reassign them in Hive's UI after cleanup. If your label audit is a quarterly task affecting fewer than 10 labels, the MCP turns a 20-minute chore into a two-minute conversation.