TerraVision vs MCP Server Kubernetes

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

TerraVision logoTerraVisionCloud Platforms · Local subprocess (stdio)Cloud architecture diagrams generated from terraform plan, with official AWS, Azure, GCP icons48FairAuth: not declaredMCP Server Kubernetes logoMCP Server KubernetesCloud Platforms · Local subprocess (stdio)/🏠 - Typescript implementation of Kubernetes cluster operations for pods, deployments, services.48FairAuth: not declared

Verdict: choose TerraVision for cloud platforms work as a local process; choose MCP Server Kubernetes 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?

TerraVision logoChoose TerraVision when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
Explore TerraVision

MCP Server Kubernetes logoChoose MCP Server Kubernetes when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
Explore MCP Server Kubernetes

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTerraVision logoTerraVisionMCP Server Kubernetes logoMCP Server Kubernetes
CategoryCloud PlatformsCloud Platforms
Quality signal48/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,6601,607
Directory activity 3 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

TerraVision tools

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

MCP Server Kubernetes 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.

TerraVision

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "terravision": {
      "command": "uvx",
      "args": [
        "--from",
        "terravision[mcp]",
        "terravision"
      ]
    }
  }
}

MCP Server Kubernetes

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

Frequently asked questions

TerraVision is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Server Kubernetes belongs to Cloud Platforms and uses a local stdio subprocess. Pick TerraVision for cloud platforms work and MCP Server Kubernetes 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.

TerraVision has no declared pricing — check the project's own site. MCP Server Kubernetes 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 terravision and flux159-mcp-server-kubernetes as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, TerraVision has a quality signal of 48/100 (Fair) with 3 views, 0 installs and 1,660 GitHub stars. MCP Server Kubernetes has 48/100 (Fair) with 0 views, 0 installs and 1,607 GitHub stars.