Skip to content

Conversation

@johnolven
Copy link

Description

Adding @hiveflow/mcp-server to the community servers list. This is the official Model Context Protocol server for HiveFlow, an automation platform that enables AI assistants to create, manage, and execute workflows.

Server Details

  • Server: @hiveflow/mcp-server (new community server)
  • Changes to: README.md - adding new entry to community servers section

Motivation and Context

HiveFlow MCP server provides a production-ready integration between AI assistants (Claude, Cursor, etc.) and the HiveFlow automation platform. This allows users to:

  • Create and manage automation workflows directly from their AI assistant
  • Execute flows with custom inputs
  • Monitor execution history and status
  • Manage MCP server configurations

The server is published on npm, well-documented, and actively maintained by the HiveFlow team.

How Has This Been Tested?

✅ Tested extensively with:

  • Claude Desktop - All 9 tools working correctly
  • Cursor IDE - Full integration tested and verified
  • Production environment - Connected to https://api.hiveflow.ai
  • Authentication - API key authentication working properly
  • Error handling - Proper error messages and fallbacks

Breaking Changes

No breaking changes. This is a new addition to the community servers list.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Package Information:

Features:

  • 9 MCP tools: flow management, execution control, server administration
  • 3 MCP resources: flows, mcp-servers, executions
  • Production-ready with proper authentication
  • Comprehensive error handling and logging
  • Simple configuration (only requires API key)

Installation:

{
  "mcpServers": {
    "hiveflow": {
      "command": "npx",
      "args": ["-y", "@hiveflow/mcp-server"],
      "env": {
        "HIVEFLOW_API_KEY": "your-api-key"
      }
    }
  }
}

This server enables powerful workflow automation capabilities directly from AI assistants, making it valuable for the MCP community.

## Add @hiveflow/mcp-server to Community Servers

### Package Information
- **Name**: @hiveflow/mcp-server
- **Version**: 1.0.7
- **npm URL**: https://www.npmjs.com/package/@hiveflow/mcp-server
- **GitHub**: https://github.com/hiveflowai/hiveflow-mcp-server

### Description
Official MCP server for HiveFlow automation platform. Provides 9 tools for creating, managing, and executing AI workflows directly from AI assistants like Claude and Cursor.

### Features
- ✅ Flow management (create, list, get, execute)
- ✅ Flow control (pause, resume)
- ✅ MCP server administration
- ✅ Execution history tracking
- ✅ Production-ready with proper authentication
- ✅ Comprehensive documentation

### Installation
```json
{
  "mcpServers": {
    "hiveflow": {
      "command": "npx",
      "args": ["-y", "@hiveflow/mcp-server"],
      "env": {
        "HIVEFLOW_API_KEY": "your-api-key"
      }
    }
  }
}
```

This server is actively maintained and follows MCP best practices.
@olaservo
Copy link
Member

olaservo commented Jul 3, 2025

Thanks for your contribution to the servers list. This has been merged in this combined PR: #2264

This is a new process we're trying out, so if you see any issues feel free to re-open the PR and tag me.

@olaservo olaservo closed this Jul 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants