MCP Server Kubernetes vs Fortress

A side-by-side look at the MCP Server Kubernetes and Fortress 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 declaredFortress logoFortressCloud Platforms · Local subprocess (stdio)Stealth browser for AI agents: fetch pages behind Cloudflare/DataDome/CAPTCHA, extract clean data.49FairAuth: not declared

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

Fortress logoChoose Fortress when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: TILION_LICENSE_KEY.
Explore Fortress

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Kubernetes logoMCP Server KubernetesFortress logoFortress
CategoryCloud PlatformsCloud Platforms
Quality signal48/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedTILION_LICENSE_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars1,607771
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

MCP Server Kubernetes tools

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

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

Fortress

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fortress": {
      "command": "npx",
      "args": [
        "-y",
        "tilion-mcp"
      ],
      "env": {
        "TILION_LICENSE_KEY": "YOUR_TILION_LICENSE_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

MCP Server Kubernetes is categorized under Cloud Platforms and uses a local stdio subprocess. Fortress belongs to Cloud Platforms and uses a local stdio subprocess. Pick MCP Server Kubernetes for cloud platforms work and Fortress 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. Fortress 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 fortress 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. Fortress has 49/100 (Fair) with 1 views, 0 installs and 771 GitHub stars.