Expose a flow as an MCP tool

Your automations don't have to live only inside HiveFlow. With one node, a flow becomes a tool any MCP-speaking assistant can call — Claude Desktop, Cursor, other agents.

The pattern

MCP client (Claude / Cursor / agent) → MCP Server node → your flow logic → response

Step by step

1. Build the flow that does the work — for example the scheduled report logic, or a lookup against your Database.
2. Add an MCP Server node (MCP) — it exposes the flow over HTTP as an MCP endpoint. Configure:
   • Tool name and description — write them for a model: what the tool does, what inputs it expects. This text is what the client LLM reads to decide when to call you.
   • Auth — require a key so only your clients can execute.
   • Rate limiting — protect your credits from runaway clients.
3. Register the endpoint in the client (e.g. Claude Desktop's MCP config or Cursor settings) and ask the assistant to use it.
4. Every call appears as a normal flow execution — debug it with the node Consoles.

Prefer a guided setup? Dashboard → MCP Generator scaffolds the MCP exposure for an existing flow.

Variations

• Expose several related flows as one toolbox: one MCP Server node per flow, same auth key.
• Combine directions: a flow that is an MCP tool can itself call MCP integrations as tools.
• Human gate for sensitive tools: put Human in the Loop inside the flow — the MCP client waits for the approval.

Genius prompt: "Expose my inventory lookup flow as an MCP tool with an auth key so I can call it from Claude Desktop."