Add MCP Connector for Claude Cowork Integration
under review
A
Amy Collins
I'd like to request a Hive MCP (Model Context Protocol) connector to enable native integration with Claude Cowork, Anthropic's desktop AI tool for automating file and task management.
MCP is an open protocol that lets AI assistants like Claude connect directly to external tools and services. With a Hive MCP connector, Claude Cowork users could interact with their Hive workspace hands-free — without copy-pasting, switching tabs, or manual data entry.
What this would enable:
- Read and update tasks, projects, and assignees directly from Claude
- Automatically create tasks or subtasks based on meeting notes, emails, or documents
- Query project status and generate summaries or reports
- Pull action items from conversations and log them to Hive instantly
- Trigger Hive automations from natural language prompts
How to build it:
Hive would publish an MCP server (open spec at modelcontextprotocol.io) that exposes its core API actions as MCP tools. Anthropic and the Cowork team handle the rest. This is a relatively lightweight lift with a high-visibility payoff for AI-forward teams.
Log In
L
Luis Alcalá Mascareño
Subject: Working with Hive "task links" not possible
Issue:
The Hive MCP server (hive-mind.hive.com) does not return any field named actionViewId in the response of getProjects — not even when fullFields: true is passed. However, building a working task deep link in the Hive web app requires exactly 3 parameters:
Without a valid actionViewId, the link either 404s (https://app.hive.com/action/{actionId}) or fails to resolve correctly.
Workaround found:
The containerId field returned by getProjects appears to serve the same purpose as actionViewId in the URL. Confirmed working in production for project NdEYwqEKXwMXgBqtB (GSFE - Farmaten): containerId: "tQgjRn9Bcet447CvC" → link opens correctly when used as actionViewId.
Requested fix (pick one):
Either rename/alias containerId as actionViewId in the getProjects response so field names match what's documented for deep-linking, or
Add an explicit actionViewId field to the Project type returned by getProjects (and ideally to insertActions's response too, so a valid deep link can be constructed in a single round trip without a second lookup call).
Why it matters:
Every integration built on top of this MCP (ours included) has to discover this mapping empirically and hardcode a workaround, which breaks silently if the two fields ever diverge for some workspaces/projects. A documented, stable field name would remove that guesswork.
E
Eric Maciel
Hi Amy, Hive's Claude integration is now live through our MCP connection and works with Claude Cowork.
Claude can work with live Hive content, summarize projects, create actions and follow-ups, update statuses, draft comments, and assign owners. The connection uses OAuth authentication and respects existing Hive workspace permissions.
Setup instructions and a direct connector link are available here:
Thank you for the detailed request and examples. They helped shape the integration.
John Furneaux
updated the status to
under review
John Furneaux
Good news Amy! https://hive.com/blog/hive-mcp-server/
A
Amy Collins
John Furneaux, exciting! However, I'm trying to connect to the MCP server at hivemind.hive.com and getting a DNS resolution failure. I'll contact support for help.
J
Jaasiel Huerta
John Furneaux Hi! thank you so much for your attention to this. Would it be possible to add Time in the MCP? We do not see that available and my team would love to help us add time automatically from our Google Calendar into Hive using Claude Cowork.
We tested the MCP and these are our findings. What we worried the mos twas the time issue:
What Claude Cannot Do with Hive
Log time / add time entries — the API returns time data but the MCP has no write tool for it
Set time estimates — same issue, read-only
Update deadlines or dates — no update ActionsDeadline tool exists
Re-parent / move actions — must archive and recreate to change parent
Delete actions — only archive is available
Get workspace members by name — getUsersWorkspaces tool returns errors; member lookup requires workarounds