The Agent ExaminerIndependent Review Authority
Development

mcp

by io.github.kubeshark · v53.3.0

Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.

GitHub stars
11,978
Transport
stdio (local process)
Auth
None required
Test status
untested

Install & run

Run the server locally with the package command below.

terminal
$https://github.com/kubeshark/kubeshark/releases/download/v53.3.0/kubeshark-mcp_darwin_arm64.mcpb
mcpbhttps://github.com/kubeshark/kubeshark/releases/download/v53.3.0/kubeshark-mcp_darwin_arm64.mcpb· stdio
mcpbhttps://github.com/kubeshark/kubeshark/releases/download/v53.3.0/kubeshark-mcp_darwin_amd64.mcpb· stdio
mcpbhttps://github.com/kubeshark/kubeshark/releases/download/v53.3.0/kubeshark-mcp_linux_arm64.mcpb· stdio
mcpbhttps://github.com/kubeshark/kubeshark/releases/download/v53.3.0/kubeshark-mcp_linux_amd64.mcpb· stdio
mcpbhttps://github.com/kubeshark/kubeshark/releases/download/v53.3.0/kubeshark-mcp_windows_amd64.mcpb· stdio

Connect this MCP server to your AI agent

MCP servers plug into any MCP-compatible client (Claude Desktop, Cursor, your own agent runtime, and more). The steps are the same everywhere:

  1. 1. Make sure the runtime is available. This server runs as a local process, so its package runner (e.g. npx / uvx / docker) must be installed on the machine running your agent.
  2. 2. Add it to your MCP client config. Point your client at the command above. Most clients accept an MCP servers map keyed by a name of your choosing.
  3. 3. No credentials needed. This server declares no required secrets — it should work out of the box.
  4. 4. Restart your client and verify.The server’s tools should appear in your agent’s tool list, ready to call.

Want this running without wiring configs yourself? Run this with Alfe →

Repository →
Developmentmcpb

Data from the official MCP registry · last updated 2026-05-19 · ★ 11,978 stars via GitHub.