Skip to content
Agentmart
Submit a tool

How to connect Kubernetes to Cursor

This page wires Kubernetes MCP Server into Cursor. The listing comes from containers, it runs locally through npx, and no API key is listed for it. You edit one config file, check the MCP logs, and look for the server's entry under Available Tools. Install details come from the listing and from Cursor's documentation.

Updated Oct 26, 2026 · Built from catalog data; how we rank and grade

Checked against Cursor's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

Before you start

  • Cursor installed and able to start.
  • Node.js with npx (the server starts with npx).
  • No API key is listed for Kubernetes MCP Server.

  1. 1. Check what you need

    Cursor spawns this server with npx, so Node.js has to be present first. Run the node --version check before editing any config.

    Check that it is installed
    node --version
    • The listing names no required key.

  2. 2. Add Kubernetes MCP Server to Cursor

    Cursor reads server definitions from an mcp.json file. The entry below tells it to launch the package through npx, and the file can sit in a project or in your home directory.

    Add this to .cursor/mcp.json in the project, or to ~/.cursor/mcp.json for every project.cursor/mcp.json
    {
  "mcpServers": {
    "kubernetes-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "kubernetes-mcp-server@0.0.67"
      ]
    }
  }
}

  3. 3. Restart or reload if it does not appear

    If Kubernetes MCP Server does not show up in Cursor, this step holds the docs' restart wording and the approval prompt that gates tool use.

    • The docs do not say whether editing mcp.json needs a restart. They tell you to restart Cursor after updating files of a custom local server.
    • Cursor asks for approval before an agent uses an MCP tool unless you allowlist it.

Check that it works

The Output panel is where Cursor reports whether the server connected, so the check starts there.

  • Open the Output panel (Cmd+Shift+U on macOS), choose MCP Logs, and look for connection errors. A working server lists its tools under Available Tools; agent mcp list shows connection state from the terminal.

Troubleshooting

A server fails or an npm-based server misbehaves after an update
Check the MCP Logs channel in the Output panel. For npm-based servers the docs suggest removing the server, running npm cache clean --force, and adding it again. Source

Security notes

  • Publisher: containers, not listed as the vendor's own server; license Apache-2.0.
  • It runs on your machine with your user account's permissions, so it can reach any file or network resource you can. Read its source before you give it access: https://github.com/containers/kubernetes-mcp-server.
  • The listing declares no required keys; use a token with the narrowest scope if the service asks for one.
  • This listing has no security grade: Agent Market has not published security grades yet, so the choice is yours to make from the source and the permissions.

How we grade security · Trust policy

Servers and skills in this guide

From here you can browse other Kubernetes servers, compare them, or read the general Cursor guide.

  1. 1
    Kubernetes MCP Server

    containers

    A Model Context Protocol (MCP) server for Kubernetes and OpenShift

    ★ 2.2K↓ 4.4K/wkLast active Oct 23, 2026Local (stdio), Remote (HTTP)Claude Code, Codex, VS Code, Cursor +2

Related

Sources

Cite this page

How to connect Kubernetes to Cursor. Agent Mart. https://agentmart.dev/guides/connect-kubernetes-to-cursor (last updated 2026-10-26)