Hiveflow in Claude and Claude Code
Connect Hiveflow to Claude with the MCP connector, or install the Claude Code plugin to run flows, work kanban boards and supervise workers from your terminal.
Hiveflow speaks MCP, so Claude can operate your workspace in conversation: list and run flows, read and edit kanban boards, and check the local workers that turn cards into pull requests. There are two ways in, and they authorize with your own Hiveflow account.
Option 1 — Add the connector (claude.ai, Desktop, mobile)
- Open Settings → Connectors → Add custom connector.
- Paste the URL:
https://mcp.hiveflow.ai - Press Connect. Hiveflow's sign-in page opens — use email and password, Google, GitHub, or an API key from your profile.
- Authorize. The tools appear in the chat's tool menu under Hiveflow.
Nothing else to configure: authorization is OAuth 2.1, so no keys live in a config file, and you can revoke it whenever you want from your Hiveflow account.
Option 2 — Install the Claude Code plugin (terminal)
The plugin bundles the same connection plus commands and knowledge about how Hiveflow works:
/plugin marketplace add hiveflowai/hiveflow-claude-plugin
/plugin install hiveflow@hiveflowThe first use opens the browser to authorize, the same way as above.
/hiveflow:status | Summary of flows, boards and workers, and what needs attention |
/hiveflow:new-flow <what it should do> | Designs a flow against your account's conventions, then creates it |
It also ships skills that load themselves when relevant: node types and entry points when building flows, how columns hand work to workers, and how to drive the Hiveflow CLI on your machine.
What Claude can do once connected
Flows — list them with their execution state, inspect nodes and edges, create new ones, run one on demand, and activate, pause or stop it.
Kanban boards — list boards, read columns and cards, create cards, move them between columns and add comments.
Workers — see which agents are connected to a board, whether they are paused, and when they last checked in.
Agents — list your AI agents and what each one is doing (working, waiting for your approval, scheduled), read an agent's objective, team members and pending work, talk to it in the same conversation you see in the app, read its audit log, and halt or resume one agent — or all of them at once.
Approvals — list the actions your flows and agents are waiting on you to approve, with what they want to do and why, and approve or reject them from the chat.
Organizations and workspaces — list what you belong to, and scope any operation to one of them.
Try it with plain requests: "which of my flows are active?", "create a card in Sales to follow up with Acme, high priority", "why isn't the onboarding card being picked up?", "what is waiting for my approval?", "ask the collections agent how many invoices are overdue".
What it can and cannot touch
The connection acts strictly as you: it sees only the organizations and workspaces your account belongs to, and every action obeys your role's permissions. Tools that only read are marked read-only; the ones that change your account — running a flow, pausing it, moving a card — are marked as such, so Claude asks before acting.
Two things worth knowing before you run a flow from a chat: its side effects are real (a flow with email or WhatsApp nodes will send), and it consumes execution credits exactly as it would from the app. The same goes for talking to an agent — it may use its tools — and for approving a request: the paused flow or agent carries out the action it asked for.
Other MCP clients
The same URL works in any client that supports remote MCP servers:
| Client | Setup |
|---|---|
| Claude Code (without the plugin) | claude mcp add --transport http hiveflow https://mcp.hiveflow.ai |
| ChatGPT | Settings → Apps & Connectors → add a connector with https://mcp.hiveflow.ai |
| Cursor | ~/.cursor/mcp.json: { "mcpServers": { "hiveflow": { "url": "https://mcp.hiveflow.ai" } } } |
| VS Code | .vscode/mcp.json: { "servers": { "hiveflow": { "type": "http", "url": "https://mcp.hiveflow.ai" } } } |
| stdio-only clients | npx -y mcp-remote https://mcp.hiveflow.ai |
For scripts or CI, skip OAuth and pass an API key: npx -y mcp-remote https://mcp.hiveflow.ai --header "Authorization: Bearer $HIVEFLOW_API_KEY".
Platform vs. your machine
The connector reaches the platform: flows, boards, workers. The CLI reaches your machine: repositories, branches, tests, pull requests. A CLI Agent node inside a flow is the bridge — a cloud flow delegating a step to the computer where your code lives.
Troubleshooting
"Account mismatch" when connecting from Claude Desktop. The browser is signed in with a different Claude account than the app. Sign out in the browser, sign in with the same account, and connect again.
Boards come back empty. The query ran against your active organization. Ask Claude to list your organizations and retry pointing at the right one.
A card sits still after moving it. The worker runs on your own machine — check that the Hiveflow CLI is running there, that the worker is not paused, and that the card is in the column that worker watches.