Skip to main content
Glama
zhouweico

mcp-kubevela

by zhouweico
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-kubevela

No user-submitted related servers found.

    Related Servers

    • Argo CD MCP Server

      mane-tv2
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.
      Apache 2.0

    • argocd-mcp

      adityaraj178
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Argo CD applications through natural language, providing tools for cluster, project, application, and resource management via stdio and HTTP transports.
      Apache 2.0
    • @vertracloud/mcp by vertracloud

      @vertracloud/mcpofficial

      vertracloud
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to operate Vertra Cloud resources through the public API: deploy and manage applications, view logs and metrics, create and restore snapshots, and administer databases and environment variables.
      99
      301 npm
      2
      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

    A3.7/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools are mostly distinct by resource type (applications, components, revisions, workflows, envs, targets, etc.). Some tools are overloaded (e.g., vela_list_workflow_records returns workflows, records, or details; vela_list_components lists or gets details), which could cause initial confusion, but descriptions clarify the behavior.

    Naming Consistency4/5

    Almost all tools follow the vela_<verb>_<resource> pattern with list/get verbs. A few exceptions like vela_velaql_query, vela_system_info, and vela_compare_application break the pattern slightly, but the overall naming remains predictable and consistent.

    Tool Count4/5

    21 tools cover KubeVela's many resource types and API endpoints thoroughly. Though above the typical 3-15 range, each tool serves a distinct purpose and the count feels justified rather than bloated.

    Completeness4/5

    As a read-only diagnostic server, the surface is comprehensive: projects, applications, components, revisions, records, workflows, envs, targets, clusters, addons, definitions, system info, compare, manifest, triggers, and VelaQL queries. Write operations are absent but consistent with the apparent focus on troubleshooting and audit, leaving no critical gaps for that purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources