Retrieve live Kubernetes deployment status for a cluster, including replica counts, pod health, and resource usage, to investigate deployment health or pod failures.
MIT
741,183 tools. Updated 2026-11-04 01:22
"Fetching Kubernetes logs for a given pod or deployment" matching MCP tools:
- Fetch recent Kubernetes events for a namespace to diagnose deployment failures, OOMKills, or pod scheduling issues.MIT
- Fetch Kubernetes pod logs with options for namespace, container, tail lines, or time duration.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
- Expose a deployment or pod as a new Kubernetes Service, selecting LoadBalancer for external access or NodePort for node-level access.Apache 2.0
- Retrieve pod logs from a Kubernetes cluster via Rancher proxy. Specify cluster, namespace, pod name, and optional tail lines.-
Matching MCP Servers
- AlicenseAqualityAmaintenanceLeast-privilege compiler and MCP gateway for AI agents: run your agent in record-only mode, compile the smallest policy it actually needs from its real tool calls, enforce it at the gateway (deny > approve > allow), and keep a SHA-256 hash-chained audit of every call that verifies offline.14110 npm1Apache 2.0
- AlicenseAqualityCmaintenanceSearch firsthand observations that agents recorded while doing real work — what actually happened with a product, API, service, or place, rather than what its documentation claims. Agents can also write back what they observed.515 npm1MIT
Matching MCP Connectors
pod-researcher — podcast prospecting for guest booking and sponsorship.
Offline log parsing, CI failures, HTTP capture analysis and bounded JSON configuration validation.
- Retrieve Kubernetes deployment runtime status by deployment ID, showing pod and Deployment health. Provides a clear error if K8s integration is disabled.Apache 2.0
- 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
- Stops a running pod by scaling it to zero, ending pod billing while attached storage remains billed; poll pods for stopped status.Apache 2.0
- Retrieve deployment details from an Octopus Deploy URL, including environment, release, and task ID for log investigation.Mozilla Public 2.0
- Fetch deployment metadata, step statuses, and the first failed step's log for a deployment ID to diagnose historical failures. Provide stepName to inspect successful steps.Apache 2.0
- Retrieve a chronological failure autopsy for a deployment, including build and pod events with remediation hints to diagnose and fix issues.MIT
- Wake an idle scaled-to-zero deployment by scaling it to 1 replica. The pod requires cold-start time before it can serve traffic.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 board activity logs with optional filters by item or user IDs. Specify a date range or use the default last 30 days.MIT
- List available managed Kubernetes versions from Gardener, ordered newest-first, to pick or validate a version for deployment.MIT
- List saved crash evidence from Kubernetes containers that were OOMKilled, evicted, or crashed to investigate pod restarts, CrashLoopBackOff, and memory pressure.Apache 2.0
- Retrieve stdout, stderr, and crash output for a deployment to diagnose errors or unexpected server exits using the crash exit code before redeploying.Apache 2.0
- 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