Skip to main content
Glama
Kirad20

contabo-mcp

by Kirad20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to contabo-mcp

No user-submitted related servers found.

    Related Servers

    • contabo-mcp

      sanchayan721
      A
      license
      A
      quality
      C
      maintenance
      Exposes the full Contabo API (all 157 operations) to OpenAI-compatible agents, enabling management of instances, snapshots, images, object storage, private networks, firewalls, DNS, domains, VIPs, secrets, tags, users, and audits. Operates read-only by default, with POST/PATCH/PUT/DELETE operations unlocked via an environment flag, while handling OAuth2 authentication and token caching automatically.
      15
      MIT

    • Cloudways MCP Server

      ayaz
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Cloudways infrastructure, including servers, applications, monitoring, and security via the Cloudways API.
      -

    • coolify-mcp-server

      AbdulWadudh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to manage a self-hosted Coolify instance, including applications, databases, services, servers, projects, deployments, environment variables, tags, teams, private keys, and S3 backup storages via the Coolify REST API.
      215 npm
      MIT

    • Coolify MCP Server

      HowieDuhzit
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Coolify for complete infrastructure management including applications, databases, servers, deployments, and team operations. Provides 100% API coverage with 64 tools for managing the entire Coolify ecosystem through natural language.
      18
      10 npm
      6
      MIT
    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

    C2.9/5.0

    Scored across 158 tools

    Disambiguation3/5

    The tools are grouped around distinct resources (compute, DNS, domains, users, firewalls, object storage, tags, etc.), so many are clearly separable by resource. However, several boundaries are fuzzy: patch_firewall vs put_firewall both update firewalls, retrieve/list/get synonyms overlap, and audit tools such as retrieve_tag_audits_list and retrieve_assignments_audits_list are hard to distinguish without close reading.

    Naming Consistency3/5

    Most names use snake_case and include a resource, which provides a readable pattern. But verb conventions are mixed: retrieve_*, list_*, get_*, patch_*, put_*, update_*, and action-style names like instance_start coexist, and some names omit the resource while others include it.

    Tool Count1/5

    The server exposes 158 tools, far beyond a manageable tool set even for a broad cloud API. While the underlying API is large, this count creates severe selection and context-loading problems for an agent.

    Completeness5/5

    The surface covers a very broad cloud-provider domain with CRUD, lifecycle actions, assignments, audits, troubleshooting, credentials, and ancillary resources like images, snapshots, DNS, domains, tags, users, roles, firewalls, and object storage. Obvious core workflows and lifecycle operations appear to be present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources