Hive MCP — A Summary of Everything That Shouldn't Still Be Broken in Mid-2026
in progress
L
Luis Alcalá Mascareño
[CONTEXT]
we are a digital agency that relies on Hive daily. We've been trying to make the MCP IA integration work reliably with Claude since early May. What follows is a brief and only mildly bitter summary.
[SECURITY PROBLEM]
The connector requires embedding an API key directly in the URL. Since Claude.ai shares connectors org-wide, this meant our director-level key was accessible to every team member — a significant privacy and security issue. Your server supports OAuth 2.0, which would solve this entirely, but Claude.ai's connector UI doesn't support OAuth discovery yet. So our workaround? We hired an additional Hive seat just to create a restricted account with a safer key. In 2026, we paid for an extra license to work around an authentication model that belongs in 2018.
[STABILITY PROBLEM WE CAN´T WORK AROUND]
Even with that workaround in place, the connector has now stopped loading its tools altogether in Claude.ai sessions. We're seeing this regularly:
* getProjects failing while other calls succeed
* Full MCP session dropping mid-workflow
* Inconsistent tool availability across sessions
* Generic error messages that provide zero debugging value
* insertActions working while getProjects fails — which is a special kind of chaos
[MID-2026 AND STILL NOT PRODUCTION-READY]
MCP as a technology has been heavily pushed by Anthropic and the broader AI ecosystem since late 2025. It's been positioned as the standard for AI-tool integration going forward. We adopted it early, invested time, documented workarounds, opened support tickets, bought extra seats — and today, in the middle of 2026, our most critical business integration still can't reliably load its tools in a web session.
There is a real possibility that by the time this is fully stable, the ecosystem will have moved on to something else entirely. That would be a remarkable achievement.
What we're actually asking for
* Investigate why the connector is failing to load tools in Claude.ai right now — this is a blocker for our daily operations.
* Prioritize OAuth support for claude.ai so we can stop paying for a workaround seat.
* Improve error messages and session diagnostics so failures are actually debuggable.
* Consider project-scoped API keys as a mid-term solution.
We genuinely like Hive and believe in the potential of this integration. We just need it to work.
Log In
L
Luis Alcalá Mascareño
MCP will not work with TASK LINKS
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 Luis, thank you again for documenting these issues so thoroughly.
We have now resolved the OAuth and reliability problems affecting Hive's Claude integration. The connection no longer requires an API key in the connector URL, and Hive now uses OAuth authentication tied to your existing Hive permissions. We also fixed the tool-loading and session reliability issues described in this request.
Please remove the previous connector and reconnect using the updated setup flow. Instructions and a direct connection link are available here:
Thank you for pushing us to improve this experience.
C
Carole Pfarr
The persistent notifications still aren't working
A
Arran Cudbard-Bell
and, please, please, add the ability to log time via the MCP!
A
Amy Collins
My company is in the same boat! Thank you for raising this Luis Alcalá Mascareño
John Furneaux
updated the status to
in progress
John Furneaux
updated the status to
under review
John Furneaux
100 thanks Luis. Mortified that your experience has been so bad... raising immediately as P1 with the team.
We will get this sorted with total priority as fast as we can (certainly addressing your issues within 1 week from today).
John