home / mcp / hiveflow mcp server
Bridges AI assistants to HiveFlow, enabling flow management, execution, and MCP server configuration.
Configuration
View docs{
"mcpServers": {
"punkpeye-hiveflow-mcp-server": {
"url": "https://api.hiveflow.ai",
"headers": {
"HIVEFLOW_API_KEY": "your-api-key-here",
"HIVEFLOW_API_URL": "https://api.hiveflow.ai",
"HIVEFLOW_INSTANCE_ID": "instance-123"
}
}
}
}You set up and run the HiveFlow MCP Server to bridge your AI assistants with HiveFlow automation. This server lets you connect clients like Claude or Cursor to HiveFlow, enabling you to manage flows, execute automations, and configure MCP endpoints from a single, centralized server.
You interact with the MCP server through your MCP client configuration. Start the server locally or point your client to the remote HiveFlow MCP endpoint. When your client is configured, you can manage flows, execute automations, and administer MCP servers using the available MCP tools. All communications are authenticated and carried over HTTPS when using remote endpoints.
Prerequisites: ensure you have Node.js installed on your system. You also need npm to install or enable the MCP server runner.
Install the MCP server globally so you can run it from any project directory.
npm install -g @hiveflow/mcp-serverConfigure your MCP client to connect to either a remote HiveFlow API or run the MCP server locally. Use the following example configurations as guidance.
{
"mcpServers": {
"hiveflow": {
"command": "npx",
"args": ["-y", "@hiveflow/mcp-server"],
"env": {
"HIVEFLOW_API_KEY": "your-api-key-here",
"HIVEFLOW_API_URL": "https://api.hiveflow.ai"
}
}
}
}API keys are transmitted securely over HTTPS. All requests are authenticated and authorized. The MCP server does not store data locally.
If you encounter issues, verify your API key and API URL, ensure the HiveFlow API is reachable, and check firewall settings. If the MCP server cannot be found, restart your AI assistant, verify the MCP configuration file location, and confirm the MCP package is installed.
For detailed logs during development, enable debug logging by setting the DEBUG environment variable to hiveflow-mcp:*.
Create new automation flows to define how data and actions move through your system.
List all configured automation flows in your HiveFlow instance.
Retrieve detailed information about a specific flow.
Run a flow with provided inputs or triggers.
Pause an active flow.
Resume a paused flow.
Inspect the execution history of flows.
List configured MCP servers in your environment.
Register a new MCP server configuration.