Your workflows become tools that Claude, Cursor and any MCP client can call. No server code, no deployment.
MCP (Model Context Protocol) is how AI assistants reach the outside world. HiveFlow flips the direction: instead of only consuming MCP tools, you publish your own. A flow that quotes shipping, checks inventory or files a ticket becomes a tool your team's AI assistants call directly.
Expose a flow as an MCP tool with typed inputs, HiveFlow generates the server and hosts it.
Claude Desktop, Claude Code, Cursor, Windsurf, if it speaks MCP, it can call your flows.
The tool isn't a stub: it's your full flow, agents, integrations, approvals and all.
Per-tool auth, usage tracking and the same execution history as any flow run.
Trigger in, result out, like any HiveFlow workflow.
Name, description and input schema so LLMs know when to call it.
Paste the MCP endpoint into Claude or Cursor, done.