Skip to main content
Glama
260,522 tools. Last updated 2026-07-05 07:02

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

  • Retrieve live Kubernetes deployment status for a cluster, including replica counts, pod health, and resource usage, to investigate deployment health or pod failures.
    MIT
  • Retrieve build logs or a deployment summary for a specific deployment. Get the live URL, status, build size, and build time, or see full log lines when available.
    MIT
  • Find recent deployments for an environment, filtered by status. Choose a deployment to debug its logs.
    Apache 2.0
  • Debug a failed deployment by fetching its metadata, step statuses, and the log of the first failed step. Optionally target a specific step for inspection.
    Apache 2.0
  • 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

Matching MCP Servers

Matching MCP Connectors

  • Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.

  • kube-linter audit for Kubernetes manifests — 63 checks: security, availability, RBAC, network.

  • Adjust the number of running pods in a Kubernetes deployment to control workload capacity. Set replicas to 0 to suspend the workload or increase to run more instances.
    MIT
  • Retrieve plan logs for the latest deployment of an environment on env0 to review infrastructure changes.
    Apache 2.0
  • Diagnose Kubernetes workloads and GitOps reconcilers to find root cause of failures. Bundles resource details, logs, events, and startup blockers in one round-trip.
    Apache 2.0
  • Retrieve diagnostic logs from a specific pod, filtering for errors, panics, stack traces, and warnings. Supports optional grep, since, and previous container options for targeted debugging.
    Apache 2.0
  • Collects and aggregates error, warning, panic, and stack trace logs from all pods of a Kubernetes workload concurrently, with optional grep filtering and deduplication.
    Apache 2.0
  • 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
  • Checks AKO pod status (running, restarts, age, ready) in Kubernetes. Essential first step for troubleshooting Ingress or LoadBalancer issues in Tanzu/K8s.
    MIT