Harvester MCP Server

Model Context Protocol (MCP) server for Harvester HCI

Local serverstdioGo

What is the Harvester MCP server?

Most developer tooling work still happens through a UI a human drives. Harvester MCP server moves it into the conversation instead. Model Context Protocol (MCP) server for Harvester HCI.

The short version

Model Context Protocol (MCP) server for Harvester HCI that enables Claude Desktop, Cursor, and other AI assistants to interact with Harvester clusters through the MCP protocol.

  • Kubernetes Core Resources —
  • Pods: List, Get, Delete
  • Deployments: List, Get
  • Services: List, Get
  • Namespaces: List, Get
  • Nodes: List, Get

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Examples — With debug logging: bash harvester-mcp-server --log-level=debug

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: KUBECONFIG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Go 1.23+ - Access to a Harvester cluster with a valid kubeconfig

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Harvester's toolset — Examples — is a fair guide to whether it matches your workflow. It is maintained by starbops; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ExamplesWith debug logging: bash harvester-mcp-server --log-level=debug

How to install the Harvester MCP server

{
  "mcpServers": {
    "harvester": {
      "command": "/path/to/harvester-mcp-server",
      "args": ["--kubeconfig", "/path/to/kubeconfig.yaml", "--log-level", "info"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Go 1.23+ - Access to a Harvester cluster with a valid kubeconfig
VariableDescriptionRequired
KUBECONFIGConfiguration value read at startup.Optional

Example prompts to try

  • Use Harvester to Examples.

Frequently asked questions

Supported operations include List, Get, and Delete for Pods; List and Get for Deployments, Services, Namespaces, Nodes, and Virtual Machines; List for CRDs, Images, Volumes, and Networks. Writing and creating resources are described in the resource handler architecture but are not yet exposed as tools.