Evidra vs MCP Server Kubernetes

A side-by-side look at the Evidra 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.

Evidra logoEvidraCloud PlatformsFail-closed policy guardrails for AI agents running kubectl, terraform, helm, and argocd.35FairAuth: not declaredMCP Server Kubernetes logoMCP Server KubernetesCloud Platforms · Local subprocess (stdio)/🏠 - Typescript implementation of Kubernetes cluster operations for pods, deployments, services.65GreatAuth: not declared

Verdict: choose Evidra for cloud platforms work; 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?

Evidra logoChoose Evidra when

  • You need dedicated capabilities in the Cloud Platforms domain.
Explore Evidra

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEvidra logoEvidraMCP Server Kubernetes logoMCP Server Kubernetes
CategoryCloud PlatformsCloud Platforms
Quality signal35/100 · Fair65/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars151,607
Directory activity 3 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listed23

Tools & capabilities

Evidra tools

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

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

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.

Evidra

No confirmed install command for Evidra yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Server Kubernetes

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

Frequently asked questions

Evidra is categorized under Cloud Platforms and uses an install path we have not confirmed yet. MCP Server Kubernetes belongs to Cloud Platforms and uses a local stdio subprocess. Pick Evidra 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. Evidra has no confirmed install command yet — follow its own setup instructions.

Evidra 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 evidra-2 and flux159-mcp-server-kubernetes as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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