Skip to main content
Glama
127,235 tools. Last updated 2026-05-05 11:43

"Fetching Kubernetes logs for a given pod or deployment" matching MCP tools:

  • Retrieve logs from deployment infrastructure to debug issues or monitor behavior. Specify deployment name, optional project scope, and number of recent lines.
    MIT
  • Retrieve build or deployment logs from Railway projects to monitor application performance, troubleshoot errors, and analyze system behavior. Supports filtering by deployment ID, service, environment, and search terms.
    MIT
  • Retrieve etcd pod logs from Kubernetes/OpenShift clusters with time-based filtering, line limits, and real-time streaming capabilities for troubleshooting.
    Apache 2.0
  • Fetch and analyze logs from Tekton PipelineRun pods in Kubernetes, prioritizing failed pods and managing output size automatically for troubleshooting.
    Apache 2.0

Matching MCP Servers

Matching MCP Connectors

  • Manage your Canvas coursework with quick access to courses, assignments, and grades. Track upcomin…

  • Deploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs.

  • Execute a command in a Kubernetes pod or container and receive the output. Uses an array format for secure, shell-free execution.
    MIT
  • Retrieve logs for a specific deployment to debug issues, monitor progress, and check build output on Railway.app infrastructure.
    MIT
  • Check the current status of a deployment to monitor progress, verify successful deployment, or detect failures.
    MIT
  • Retrieve logs for a specific deployment to debug issues, monitor progress, and check build output in Railway.app infrastructure.
    MIT
  • Retrieve logs for a specific deployment to debug issues, monitor progress, and check build output in Railway.app infrastructure.
    MIT
  • Retrieve logs for a specific deployment to debug issues, monitor progress, or check build output. Requires deployment ID.
    MIT
  • Analyzes Kubernetes pod logs with intelligent strategy selection based on context and urgency, providing insights for troubleshooting, investigation, or monitoring.
    Apache 2.0
  • Delete a specific Kubernetes pod for troubleshooting or cleanup. The pod will be recreated if managed by a controller.
    MIT
  • Analyze Kubernetes pod logs to identify errors, warnings, and performance patterns with adaptive time window selection and multi-pass processing.
    Apache 2.0
  • Analyzes Kubernetes namespace issues by examining pod logs and events, prioritizing failed pods and correlating data within token budget constraints.
    Apache 2.0