Skip to main content
Glama
510,465 tools. Updated 2026-09-04 01: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 logs from a Kubernetes pod by specifying its name, namespace, and number of recent lines. Get container output for debugging or monitoring.
    MIT
  • Retrieve pod logs from a Kubernetes cluster via Rancher proxy. Specify cluster, namespace, pod name, and optional tail lines.
  • Retrieve logs from a Kubernetes pod or a specific container, with options to tail lines or fetch logs from a previous container instance.
    Apache 2.0
  • 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides Kubernetes cluster management capabilities through natural language via MCP protocol over HTTP/SSE. Supports Pod, Service, Deployment operations, log retrieval, and resource management with JWT authentication and RBAC permissions.
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables MCP clients to inspect and operate Kubernetes clusters across multiple contexts, with read-only/read-write/admin access modes and security flags controlling namespaces, contexts, deletes, applies, and exec.
    10
    399
    2
    MIT

Matching MCP Connectors

  • Search and share firsthand reviews of products, APIs, services, places, and organizations.

  • Register a deployment region

  • Retrieve logs from deployment infrastructure to debug issues or monitor behavior. Specify deployment name, optional project scope, and number of recent lines.
    MIT
  • Retrieve a chronological failure autopsy for a deployment, including build and pod events with remediation hints to diagnose and fix issues.
    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
  • 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 a specific environment's current deployment. Review the Terraform plan output; for historical deployments use deployment context instead.
    Apache 2.0
  • Fetch Terraform deployment logs with pagination. Retrieve logs from completed jobs immediately or stream from running jobs using last_event_id cursor.
    Apache 2.0
  • Get build and runtime logs for any deployment, or the latest, to monitor progress and diagnose failures like missing dependencies or build errors.
    MIT
  • Lists every Kubernetes context in the active kubeconfig and reports AKO deployment status, pod phase, and version per cluster. Use it to identify the correct context before running AKO diagnostics.
    MIT
  • Rank Kubernetes pods, workloads, or nodes by live CPU or memory usage to pinpoint performance bottlenecks, OOM risks, and uneven node load before investigating logs.
    Apache 2.0