Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_restartProjectV1

Restart Docker Compose project services while preserving data volumes and network configurations. Use to apply configuration changes or recover from service failures.

Instructions

Restarts all services in a Docker Compose project by stopping and starting containers in the correct dependency order.

This operation preserves data volumes and network configurations while refreshing the running containers.

Use this to apply configuration changes or recover from service failures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
virtualMachineIdYesVirtual Machine ID
projectNameYesDocker Compose project name using alphanumeric characters, dashes, and underscores only

Implementation Reference

  • Schema definition for the VPS_restartProjectV1 tool. This is an auto-generated OpenAPI tool definition that specifies the tool as a POST request to '/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/restart' with input parameters virtualMachineId (integer) and projectName (string).
    {
      "name": "VPS_restartProjectV1",
      "description": "Restarts all services in a Docker Compose project by stopping and starting\ncontainers in the correct dependency order.\n\nThis operation preserves data volumes and network configurations while refreshing the running containers. \n\nUse this to apply configuration changes or recover from service failures.",
      "method": "POST",
      "path": "/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/restart",
      "inputSchema": {
        "type": "object",
        "properties": {
          "virtualMachineId": {
            "type": "integer",
            "description": "Virtual Machine ID"
          },
          "projectName": {
            "type": "string",
            "description": "Docker Compose project name using alphanumeric characters, dashes, and underscores only"
          }
        },
        "required": [
          "virtualMachineId",
          "projectName"
        ]
      },
      "security": [
        {
          "apiToken": []
        }
      ],
      "group": "vps"
    },
  • src/servers/vps.ts:3-7 (registration)
    Server entry point that registers all VPS tools (including VPS_restartProjectV1) by importing the tools array from src/core/tools/vps.ts and passing them to the MCP server startup function.
    import { startServer } from '../core/runtime.js';
    import tools from '../core/tools/vps.js';
    
    startServer({ name: 'hostinger-vps-mcp', version: '0.1.41', tools });
  • Generic API call executor in the MCP server runtime. VPS_restartProjectV1 is not a 'custom' tool, so its execution is handled by executeApiCall(), which translates the tool definition (method=POST, path with path params) into an HTTP request to the Hostinger API, substituting path parameters (virtualMachineId, projectName) and sending remaining params as JSON body.
    async executeApiCall(tool, params) {
      // Get method and path from tool
      const method = tool.method;
      let path = tool.path;
    
      // Clone params to avoid modifying the original
      const requestParams = { ...params };
    
      // Replace path parameters with values from params
      Object.entries(requestParams).forEach(([key, value]) => {
        const placeholder = `{${key}}`;
        if (path.includes(placeholder)) {
          path = path.replace(placeholder, encodeURIComponent(String(value)));
          delete requestParams[key]; // Remove used parameter
        }
      });
    
      // Build the full URL
      const baseUrl = this.baseUrl.endsWith("/") ? this.baseUrl : `${this.baseUrl}/`;
      const cleanPath = path.startsWith("/") ? path.slice(1) : path;
      const url = new URL(cleanPath, baseUrl).toString();
    
      this.log('debug', `API Request: ${method} ${url}`);
    
      try {
        // Configure the request
        const config = {
          method: method.toLowerCase(),
          url,
          headers: { ...this.headers },
          timeout: 60000, // 60s
          validateStatus: function (status) {
            return status < 500; // Resolve only if the status code is less than 500
          }
        };
      
        const bearerToken = process.env['API_TOKEN'] || process.env['APITOKEN']; // APITOKEN for backwards compatibility
        if (bearerToken) {
          config.headers['Authorization'] = `Bearer ${bearerToken}`;
        } else {
          this.log('error', `Bearer Token environment variable not found: API_TOKEN`);
        }
    
        // Add parameters based on request method
        if (["GET", "DELETE"].includes(method)) {
          // For GET/DELETE, send params as query string
          config.params = { ...(config.params || {}), ...requestParams };
        } else {
          // For POST/PUT/PATCH, send params as JSON body
          config.data = requestParams;
          config.headers["Content-Type"] = "application/json";
        }
    
        this.log('debug', "Request config:", {
          url: config.url,
          method: config.method,
          params: config.params,
          headers: Object.keys(config.headers)
        });
    
        // Execute the request
        const response = await axios(config);
        this.log('debug', `Response status: ${response.status}`);
    
        return response.data;
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        this.log('error', `API request failed: ${errorMessage}`);
    
        if (axios.isAxiosError(error)) {
          const responseData = error.response?.data;
          const responseStatus = error.response?.status;
    
          this.log('error', 'API Error Details:', {
            status: responseStatus,
            data: typeof responseData === 'object' ? JSON.stringify(responseData) : responseData
          });
    
          // Rethrow with more context for better error handling
          const detailedError = new Error(`API request failed with status ${responseStatus}: ${errorMessage}`);
          detailedError.response = error.response;
          throw detailedError;
        }
    
        throw error;
      }
    }
Behavior4/5

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

The description discloses important behavioral traits: preserves data volumes and network configurations, and handles dependency order. This adds value beyond the schema, though it does not mention potential downtime or asynchronous behavior.

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 concise with three focused sentences, each contributing essential information. It is front-loaded with the core purpose and avoids redundancy.

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

Completeness4/5

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

For a simple restart tool with no output schema, the description covers purpose, behavior, and usage scenarios adequately. It lacks details on return values or error handling, but is sufficiently complete for basic usage.

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?

The input schema covers both parameters fully with descriptions (100% coverage). The description does not add new information about the parameters beyond what is already in the schema, so it adds marginal value.

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

Purpose5/5

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

The description clearly states it restarts all services in a Docker Compose project, providing a specific verb and resource. It distinguishes from sibling tools like VPS_startProjectV1 and VPS_stopProjectV1 by focusing on restarting rather than starting or stopping.

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

Usage Guidelines4/5

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

The description explicitly mentions use cases for applying configuration changes or recovering from service failures, guiding the agent on appropriate scenarios. It does not include when not to use or alternative tools, but the context is adequate.

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/hostinger/api-mcp-server'

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