MCP Server Kubernetes vs Vruum Gtm MCP

A side-by-side look at the MCP Server Kubernetes and Vruum Gtm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Server Kubernetes logoMCP Server KubernetesCloud Platforms · Local subprocess (stdio)/🏠 - Typescript implementation of Kubernetes cluster operations for pods, deployments, services.65GreatAuth: not declaredVruum Gtm MCP logoVruum Gtm MCPCloud Platforms · Local subprocess (stdio)Vruum AI revenue platform — outbound, deals, pipeline & CRM automation over one MCP.44FairAuth: not declared

Verdict: choose MCP Server Kubernetes for cloud platforms work as a local process; choose Vruum Gtm MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

MCP Server Kubernetes logoChoose MCP Server Kubernetes when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like cleanup, kubectl_get, kubectl_describe.
Explore MCP Server Kubernetes

Vruum Gtm MCP logoChoose Vruum Gtm MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: VRUUM_MCP_TOKEN, VRUUM_MCP_URL, VRUUM_MCP_TIMEOUT_MS, VRUUM_CONFIG_DIR.
Explore Vruum Gtm MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Kubernetes logoMCP Server KubernetesVruum Gtm MCP logoVruum Gtm MCP
CategoryCloud PlatformsCloud Platforms
Quality signal65/100 · Great44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedVRUUM_MCP_TOKENVRUUM_MCP_URLVRUUM_MCP_TIMEOUT_MSVRUUM_CONFIG_DIR
Verified ownerCommunity listingCommunity listing
GitHub stars1,6070
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools23Not listed

Tools & capabilities

MCP Server Kubernetes tools 23

  • cleanupCleanup all managed resources
  • kubectl_getGet or list Kubernetes resources by resource type, name, and optionally namespace
  • kubectl_describeDescribe Kubernetes resources by resource type, name, and optionally namespace
  • kubectl_applyApply a Kubernetes YAML manifest from a string or file
  • kubectl_deleteDelete Kubernetes resources by resource type, name, labels, or from a manifest file
  • kubectl_createCreate Kubernetes resources using various methods (from file or using subcommands)
  • kubectl_logsGet logs from Kubernetes resources like pods, deployments, or jobs
  • kubectl_scaleScale a Kubernetes deployment
  • kubectl_patchUpdate field(s) of a resource using strategic merge patch, JSON merge patch, or JSON patch
  • kubectl_rolloutManage the rollout of a resource (e.g., deployment, daemonset, statefulset)
  • kubectl_contextManage Kubernetes contexts - list, get, or set the current context
  • kubectl_reconnectReconnect to the Kubernetes API server by recreating all API clients. Use this after cluster upgrades (e.g., EKS control plane upgrades that rotate ENIs/IPs) to force fresh DNS resolution and new TCP connections.
  • +11 more on the listing page

Vruum Gtm MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

MCP Server Kubernetes

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "flux159-mcp-server-kubernetes": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-kubernetes"
      ]
    }
  }
}

Vruum Gtm MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-37": {
      "command": "npx",
      "args": [
        "-y",
        "@vruum/cli"
      ],
      "env": {
        "VRUUM_MCP_TOKEN": "YOUR_VRUUM_MCP_TOKEN_HERE",
        "VRUUM_MCP_URL": "YOUR_VRUUM_MCP_URL_HERE",
        "VRUUM_MCP_TIMEOUT_MS": "YOUR_VRUUM_MCP_TIMEOUT_MS_HERE",
        "VRUUM_CONFIG_DIR": "YOUR_VRUUM_CONFIG_DIR_HERE"
      }
    }
  }
}

Frequently asked questions

MCP Server Kubernetes is categorized under Cloud Platforms and uses a local stdio subprocess. Vruum Gtm MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick MCP Server Kubernetes for cloud platforms work and Vruum Gtm MCP for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

MCP Server Kubernetes has no declared pricing — check the project's own site. Vruum Gtm MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add flux159-mcp-server-kubernetes and mcp-37 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Server Kubernetes has a quality signal of 65/100 (Great) with 0 views, 0 installs and 1,607 GitHub stars. Vruum Gtm MCP has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.