Skip to main content
Glama
punkpeye

HiveFlow MCP Server

create_mcp_server

Register a new MCP server in HiveFlow to connect AI assistants directly to the automation platform for managing and executing workflows through natural language commands.

Instructions

Registra un nuevo servidor MCP en HiveFlow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre único del servidor MCP
commandYesComando para ejecutar el servidor
argsNoArgumentos del comando
descriptionNoDescripción del servidor

Implementation Reference

  • Handler function that creates an MCP server by posting to HiveFlow API and returns success message.
    async createMCPServer(args) {
      const response = await this.hiveflowClient.post('/api/mcp/servers', {
        name: args.name,
        command: args.command,
        args: args.args || [],
        description: args.description || ''
      });
      
      return {
        content: [
          {
            type: 'text',
            text: `✅ Servidor MCP "${args.name}" registrado exitosamente.\nComando: ${args.command}\nEstado: registrado`
          }
        ]
      };
    }
  • TypeScript version of the handler function that creates an MCP server by posting to HiveFlow API.
    private async createMCPServer(args: any) {
      const response = await this.hiveflowClient.post('/api/mcp/servers', {
        name: args.name,
        command: args.command,
        args: args.args || [],
        description: args.description || ''
      });
      
      return {
        content: [
          {
            type: 'text',
            text: `✅ Servidor MCP "${args.name}" registrado exitosamente.\nComando: ${args.command}\nEstado: registrado`
          }
        ]
      };
    }
  • Tool schema definition including input schema for create_mcp_server in the list of tools.
    {
      name: 'create_mcp_server',
      description: 'Registra un nuevo servidor MCP en HiveFlow',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Nombre único del servidor MCP'
          },
          command: {
            type: 'string',
            description: 'Comando para ejecutar el servidor'
          },
          args: {
            type: 'array',
            items: { type: 'string' },
            description: 'Argumentos del comando'
          },
          description: {
            type: 'string',
            description: 'Descripción del servidor'
          }
        },
        required: ['name', 'command']
      }
    },
  • TypeScript tool schema definition for create_mcp_server.
    {
      name: 'create_mcp_server',
      description: 'Registra un nuevo servidor MCP en HiveFlow',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Nombre único del servidor MCP'
          },
          command: {
            type: 'string',
            description: 'Comando para ejecutar el servidor'
          },
          args: {
            type: 'array',
            items: { type: 'string' },
            description: 'Argumentos del comando'
          },
          description: {
            type: 'string',
            description: 'Descripción del servidor'
          }
        },
        required: ['name', 'command']
      }
  • src/index.js:227-228 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that routes to the handler.
    case 'create_mcp_server':
      return await this.createMCPServer(args);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Registra' implies a write/create operation, it doesn't specify permissions required, whether this is idempotent, what happens on duplicate names, or what the response contains. For a creation tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the tool's purpose without any wasted words. It's appropriately sized and front-loaded with the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after registration, what the server registration enables, or provide any context about the MCP server lifecycle. The agent lacks crucial information about this tool's behavior and outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 4 parameters thoroughly. The description doesn't add any additional meaning about parameters beyond what's in the schema, which meets the baseline expectation when schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Registra' - registers) and the resource ('un nuevo servidor MCP en HiveFlow'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its siblings like 'create_flow' or 'list_mcp_servers', which would require a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create_flow' or 'list_mcp_servers'. There's no mention of prerequisites, use cases, or exclusions, leaving the agent with minimal context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/punkpeye/hiveflow-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server