MCP Server Kubernetes vs Vibie MCP

A side-by-side look at the MCP Server Kubernetes and Vibie 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.48FairAuth: not declaredVibie MCP logoVibie MCPCloud Platforms · Local subprocess (stdio)Deploy static HTML folders to permanent vibie.page URLs in seconds. One-line auto-install (npx vibie-mcp setup) wires up Claude Desktop and Cursor, OAuth device-flow auth, automatic folder marker for repeat deploys without re-typing slugs.59GoodAuth: oauth 2.0

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

Vibie MCP logoChoose Vibie MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You have the keys it needs: VIBIE_API_BASE.
  • You want tools like vibie_create_site, vibie_update_site, vibie_list_sites.
Explore Vibie MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Kubernetes logoMCP Server KubernetesVibie MCP logoVibie MCP
CategoryCloud PlatformsCloud Platforms
Quality signal48/100 · Fair59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsNone listedVIBIE_API_BASE
Verified ownerCommunity listingCommunity listing
GitHub stars1,6071
Directory activity 0 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listed4

Tools & capabilities

MCP Server Kubernetes tools

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

Vibie MCP tools 4

  • vibie_create_siteCreate a NEW Vibie site by uploading a local folder. Use this when the user wants to publish a brand new site, or when no .vibie/site.json marker exists in the folder. Vibie hosts static HTML/CSS/JS at a permanent URL like my-site-a3f9.vibie.page. Auto-creates a .vibie/site.json marker in the folder for future updates.
  • vibie_update_siteUpdate an existing Vibie site with new content from a local folder. Use this when the user wants to re-deploy or push changes to an already-published site. If .vibie/site.json marker exists in the folder, the slug is read automatically; otherwise pass slug explicitly. Same URL, new content.
  • vibie_list_sitesList all sites owned by the current Vibie user. Returns slug, display name, category, URL, visibility, and last update time. Use this to discover what sites the user already has, e.g. before update.
  • vibie_get_siteGet metadata for a single Vibie site by slug. Returns name, category, URL, visibility, like count, timestamps.

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"
      ]
    }
  }
}

Vibie MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shdomi8599-vibie-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vibie-mcp"
      ],
      "env": {
        "VIBIE_API_BASE": "YOUR_VIBIE_API_BASE_HERE"
      }
    }
  }
}

Frequently asked questions

MCP Server Kubernetes is categorized under Cloud Platforms and uses a local stdio subprocess. Vibie MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick MCP Server Kubernetes for cloud platforms work and Vibie 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. Vibie MCP is listed as free. Auth: oauth 2.0. 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 shdomi8599-vibie-mcp 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 48/100 (Fair) with 0 views, 0 installs and 1,607 GitHub stars. Vibie MCP has 59/100 (Good) with 3 views, 0 installs and 1 GitHub stars.