Skip to main content
Glama
raffelprama

MCP cldkctl Server

by raffelprama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to MCP cldkctl Server

No user-submitted related servers found.

    Related Servers

    • Claude Code MCP

      auchenberg
      A
      license
      B
      quality
      D
      maintenance
      An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) through the standardized MCP interface.
      8
      4 npm
      188
      MIT

    • my-mcp-server

      15972289829
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      96 npm
      -

    • MCP Tools

      ZbigniewTomanek
      A
      license
      Not graded
      quality
      D
      maintenance
      A custom Model Context Protocol server that gives Claude Desktop and other LLMs access to file system operations and command execution capabilities through standardized tool interfaces.
      23
      Apache 2.0
    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.3/5.0

    Scored across 161 tools

    Disambiguation4/5

    Tools are generally distinct by resource and action, with clear naming like create_vm, get_vm, delete_vm. However, there is some overlap, such as cldkctl_vm_reboot and cldkctl_reboot_vm, which could cause confusion, and similar patterns for other resources like pods and services. Descriptions help, but the redundancy reduces clarity.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with a verb_noun structure, such as create_deployment, get_pod, delete_vm. There are no deviations in style or convention across all 161 tools, making them predictable and easy to parse.

    Tool Count1/5

    With 161 tools, the count is extremely high and feels overwhelming for a single server. This many tools suggests poor scoping, likely mapping directly to API endpoints without consolidation, making it difficult for agents to navigate and increasing the risk of misselection.

    Completeness5/5

    The tool set provides comprehensive coverage across multiple domains, including authentication, billing, Kubernetes resources, VMs, notebooks, registries, and organization management. Each domain has full CRUD operations and lifecycle management, with no obvious gaps, ensuring agents can handle complete workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources