Skip to main content
Glama
onlitec

VPS MCP Server

by onlitec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to VPS MCP Server

No user-submitted related servers found.

    Related Servers

    • Portainer MCP Server

      caffeineflo
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers, stacks, images, volumes, and networks through Portainer's API. Supports listing resources, viewing logs, and performing container operations with configurable write permissions.
      1
      -

    • portainer-mcp

      ginkida
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to manage Portainer container environments through natural language, including deploying stacks, managing containers, images, volumes, networks, and executing commands.
      53
      63 PyPI
      2
      MIT

    • Docker Manager MCP

      jmagar
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers, deploy stacks, and monitor services across multiple Docker hosts from one centralized location. Supports container lifecycle management, Docker Compose operations, and infrastructure orchestration through natural language commands.
      6
      MIT

    • portainer-mcp

      Lauredmarin
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables managing Docker containers and Portainer resources through natural language, supporting stack deployment, container operations, and environment monitoring.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific Docker/Portainer resources (containers, images, networks, volumes, Portainer config) and actions (create, get, list, remove, start/stop/restart), making it easy for an agent to select the correct one. For example, 'create_container' vs 'start_container' serve different lifecycle stages.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case throughout. Verbs like create, get, list, remove, start, stop, restart, pull, test, and set are applied predictably to nouns like container, image, network, volume, and portainer_config. There are no deviations in naming conventions.

    Tool Count4/5

    With 21 tools, the count is slightly high but reasonable for the server's purpose of managing Docker and Portainer operations. It covers a comprehensive set of actions across multiple resource types, though it might feel heavy compared to a more minimal set. Each tool earns its place by addressing a specific need in container management.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for Docker resources (containers, images, networks, volumes) and Portainer configuration. It includes creation, retrieval, listing, removal, and operational controls (start/stop/restart), with no obvious gaps. The Portainer tools handle connection testing and configuration, ensuring agents can manage the full workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources