mait.sh1.142.0

Private beta: features and content may change. No warranty; use at your own risk.

MCP Kubectl

Four inspection tools let your agent read Kubernetes observations; separate operator commands make changes.

Start here: what it does, why use it, and how it fits.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
What it does

Your agent reads the cluster. You keep the changes.

When something looks wrong in a cluster, the first questions are simple. Which pods are not ready? Is the deployment healthy? Are all the nodes up? MCP Kubectl lets your agent ask the live cluster those questions and answer from the real state, not from a pasted screenshot or a guess.

This server offers the agent four inspection tools. Cluster changes, such as applying a file or taking a node out of service, require a separate operator workflow. Other tools available to an agent are outside this server's read-only scope.

Your agentRead-onlyhelperYour clusterYou1asks2looks at3make changesYour agentRead-only helperYour clusterYou1asks2looks at3make changes
  1. Step 1: Your agent asks Read-only helper.
  2. Step 2: Read-only helper looks at Your cluster.
  3. Step 3: You make changes Your cluster.
Why use it

What you gain over pasting output or handing over full access.

Without access, an agent guesses. With full access, it could also delete or drain things. Pasting results into the chat by hand is slow and goes stale. Read-only access sits between the two.

Experience

The agent sees the live cluster

You ask which pods are not ready and get an answer from the cluster, not from a stale paste

Typical alternative
You copy results into the chat
Here
The agent asks the cluster directly and reads the current state
Reliability

Inspection tools have a smaller scope

Review observations before approving a separate change

Typical alternative
Giving an agent direct mutation commands
Here
This server exposes four inspection tools; changes remain separate
Tokens

Answers that are short and exact

The agent reads facts, not columns

Typical alternative
Long tables the agent has to read around
Here
Answers come as a few precise facts: names, how many are ready, restarts, counts
Security

Kubernetes permissions still decide

Authorize that identity for the intended scope; all clients admitted to one server share it

Typical alternative
Assuming a connected client has all cluster access
Here
Reads use the identity selected by the server owner
Usability

One executable for the main tasks

Confirm cluster credentials and optional workload utilities with the owner

Typical alternative
Separate tools for routine inspection and changes
Here
The executable supplies inspection and operator commands
Operability

Tool execution has a deadline

Preserve the error and check scope; connection and response delivery take separate time

Typical alternative
Waiting without an execution limit
Here
A slow inspection reports an error after its 60-second execution budget
Out of the box

Ready in the image, one entry to add.

The program comes with the MAIT image and updates with it (mait-image). The service owner must provide the intended cluster identity and the client connection. It uses a kubeconfig or, when configured inside a pod, its service-account credentials. There is no practice mode, so it needs a real cluster to answer.

You can also place it behind MCP Registry, so one entry in your agent's app reaches it.

Where it fits

Where it sits in the MAIT toolkit.

It is the cluster window for your agent, and it works alongside the registry.

Installed bymait-image ships the program
Used withMCP Registry, to reach it from one entry in your agent's app
Alternative toThe standard kubectl, for an agent that should only read
Learn more

Where to read on.