Inspektor Gadget MCP Server vs Elasticsearch MCP Server

A side-by-side comparison of two Monitoring & Observability servers — tools, transport, auth, maintenance, and copy-paste config for each.

	Inspektor Gadget MCP Server Debug Kubernetes & container workloads with eBPF kernel telemetry through an AI interface. Unverified stdio (local) No auth Go	Elasticsearch MCP Server Official Elastic server: list indices, read mappings, and search with Query DSL. Verified stdio (local) API key TypeScript
Category	Monitoring & Observability	Monitoring & Observability
Language	Go	TypeScript
Transport	stdio (local)	stdio (local)
Auth	None	API key
GitHub stars	26	700
Last commit	5 days ago	4 months ago
Verified
Actively maintained
Install	`docker run -i --mount type=bind,src=${HOME}/.kube/config,dst=/kubeconfig ghcr.io/inspektor-gadget/ig-mcp-server:latest -gadget-discoverer=artifacthub`	`docker run -i --rm -e ES_URL -e ES_API_KEY docker.elastic.co/mcp/elasticsearch stdio`
Repo	Open	Open

Verdict

Pick Inspektor Gadget MCP Server if you want zero-setup with no API key, and you need the broadest set of tools.

Pick Elasticsearch MCP Server if you want the official, vendor-maintained server, and you prefer the more popular, battle-tested option.

Add Inspektor Gadget MCP Server

Install / run

docker run -i --mount type=bind,src=${HOME}/.kube/config,dst=/kubeconfig ghcr.io/inspektor-gadget/ig-mcp-server:latest -gadget-discoverer=artifacthub

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "inspektor-gadget-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--mount",
        "type=bind,src=${env:HOME}/.kube/config,dst=/kubeconfig",
        "ghcr.io/inspektor-gadget/ig-mcp-server:latest",
        "-gadget-discoverer=artifacthub"
      ]
    }
  }
}

Requires Docker to be installed and running.

Add Elasticsearch MCP Server

Install / run

docker run -i --rm -e ES_URL -e ES_API_KEY docker.elastic.co/mcp/elasticsearch stdio

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "elasticsearch-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ES_URL",
        "-e",
        "ES_API_KEY",
        "docker.elastic.co/mcp/elasticsearch",
        "stdio"
      ],
      "env": {
        "ES_URL": "<your-elasticsearch-cluster-url>",
        "ES_API_KEY": "<your-elasticsearch-api-key>"
      }
    }
  }
}

Requires Docker to be installed and running.

FAQ

Inspektor Gadget MCP Server or Elasticsearch MCP Server — which is better?

Pick Inspektor Gadget MCP Server if you want zero-setup with no API key, and you need the broadest set of tools. Pick Elasticsearch MCP Server if you want the official, vendor-maintained server, and you prefer the more popular, battle-tested option.

Can I use both Inspektor Gadget MCP Server and Elasticsearch MCP Server?

Yes — MCP clients let you enable multiple servers at once. Add both configs to your client's mcpServers and use whichever tool fits the task.

Do Inspektor Gadget MCP Server and Elasticsearch MCP Server work with Claude, Cursor and Windsurf?

Both do. Copy the per-client config below into Claude Desktop, Cursor, or Windsurf.

View Inspektor Gadget MCP Server →View Elasticsearch MCP Server →More comparisons →