MCP servers · cloudcorprecords

clusterport: MCP server and CLI for core Kubernetes operations

An MCP server and CLI that exposes core kubectl operations, such as get, apply, scale, patch and rollout, through the host's own kubectl.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

clusterport is a small MCP server and CLI for core Kubernetes work. It is a clean-room rebuild of a twelve-tool subset of the documented surface of the community Flux159 mcp-server-kubernetes project. The tools cover get, describe and logs; apply and create; delete, scale and patch; rollout actions and context switching; plus kubectl explain and API-resource listing. Each call runs through the host's kubectl as an argument array, never a shell string. Manifests are passed over stdin rather than written to temp files. Port-forwarding, exec into pods, Helm tools, addon install and uninstall, non-resource URL requests, watch and streaming, and node operations such as cordon, taint and drain are deliberately left out.

It suits MCP clients that need basic kubectl-style inspection and changes to cluster resources. The executor is injectable, and the test suite runs against a fake executor that checks exact argument arrays and stdin payloads, so no live cluster is touched.

Running it requires a working kubectl binary and cluster credentials on the host. Executor failures, such as a missing kubectl, an unreachable cluster or a nonexistent resource, are returned as tool errors with the underlying message. The CLI exits with 0 on success, 1 on a kubectl error and 2 on a usage error.

Limitations and requirements

The host needs a working kubectl binary and cluster credentials. When kubectl is absent, calls fail with the underlying spawn error (ENOENT). The published container image bundles no kubectl binary and expects a host executor.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/clusterport

    Core kubectl operations: get, describe, logs, apply, scale, patch, rollout and explain.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
clusterport: MCP server and CLI for core Kubernetes operations | AI Gate Discover