Back to Home
sysdiglabs icon

sysdig-mcp-server

Verified Safe

by sysdiglabs

Overview

Serves as a Model Context Protocol (MCP) server, enabling Large Language Models (LLMs) to query and interact with the Sysdig Secure platform for security events and Kubernetes metrics.

Installation

Run Command
docker run -e SYSDIG_MCP_API_HOST=<your_sysdig_host> -e SYSDIG_MCP_API_TOKEN=<your_sysdig_secure_api_token> -e SYSDIG_MCP_TRANSPORT=stdio -p 8080:8080 ghcr.io/sysdiglabs/sysdig-mcp-server:latest

Environment Variables

  • SYSDIG_MCP_API_HOST
  • SYSDIG_MCP_API_TOKEN
  • SYSDIG_MCP_TRANSPORT
  • SYSDIG_MCP_API_SKIP_TLS_VERIFICATION
  • SYSDIG_MCP_LISTENING_HOST
  • SYSDIG_MCP_LISTENING_PORT
  • SYSDIG_MCP_MOUNT_PATH
  • SYSDIG_MCP_LOGLEVEL

Security Notes

The server offers an option (`SYSDIG_MCP_API_SKIP_TLS_VERIFICATION=true`) to skip TLS verification, which, while useful for self-signed certificates in specific deployments (e.g., on-prem), introduces a significant security risk for Man-in-the-Middle (MITM) attacks if used improperly in production environments. The `generate_sysql` tool has a known limitation where it does not work with Service Account tokens and returns a 500 error, requiring a regular user API token instead. Tools dynamically filter based on user permissions, which is a strong positive security control. Direct SysQL execution is possible via `run_sysql`, and while SysQL is designed for secure querying, a robust prompt engineering or validation layer is crucial on the LLM side to prevent unintended data exposure or resource strain. No obvious hardcoded secrets or malicious patterns were found in the provided code snippet; API tokens are loaded from environment variables or HTTP headers, which is good practice.

Similar Servers

Stats

Interest Score36
Security Score7
Cost ClassLow
Avg Tokens750
Stars6
Forks1
Last Update2025-12-09

Tags

MCP ServerSysdig SecureLLM IntegrationKubernetes MonitoringGo