HiveFlow MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_flowC | Crea un nuevo flujo de trabajo en HiveFlow |
| list_flowsC | Lista todos los flujos de trabajo del usuario |
| get_flowC | Obtiene detalles de un flujo específico |
| execute_flowC | Ejecuta un flujo de trabajo específico |
| pause_flowC | Pausa un flujo activo |
| resume_flowC | Reanuda un flujo pausado |
| list_mcp_serversB | Lista los servidores MCP configurados en HiveFlow |
| create_mcp_serverC | Registra un nuevo servidor MCP en HiveFlow |
| get_flow_executionsC | Obtiene el historial de ejecuciones de un flujo |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| HiveFlow Flows | List of all workflow flows |
| MCP Servers | List of configured MCP servers |
| Flow Executions | Flow execution history |
TDQS
Scored across 9 tools
Each tool has a distinct purpose with clear boundaries: create_flow vs. get_flow vs. list_flows for flow management, create_mcp_server vs. list_mcp_servers for server registration, and execute_flow vs. pause_flow vs. resume_flow for flow execution control. No overlap or ambiguity exists between tools.
All tools follow a consistent verb_noun naming pattern (e.g., create_flow, list_flows, pause_flow) using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.
With 9 tools, the server is well-scoped for managing workflows and MCP servers in HiveFlow. Each tool serves a clear function, and the count is neither too sparse nor bloated, fitting typical expectations for a domain-specific server.
The toolset covers core CRUD and lifecycle operations for flows (create, get, list, execute, pause, resume) and MCP servers (create, list), with get_flow_executions providing execution history. A minor gap exists in updating or deleting flows/servers, but agents can work around this for most workflows.