Best for
- Developers who need local access to Kubernetes services.
- Teams seeking to reduce environment-specific connection configuration.
- Users who need to forward multiple services or avoid local port conflicts.
K
kubefwd
Community
Bulk Kubernetes service forwarding for local development.
GitHub source repository ↗
34FMRS · D
Based on the repository, server manifest, and README, kubefwd is described as a Kubernetes bulk port-forwarding tool for local development. The manifest provides stdio MCP packages, while the README mentions Claude Code and Cursor integration and an Apache-2.0 license. No specific MCP tool identifiers or client configuration examples are provided.
kubefwd is a command-line utility that bulk-forwards Kubernetes services to a local workstation. It assigns each service a unique 127.x.x.x loopback IP and automatically adds service names to /etc/hosts. It includes an interactive TUI, automatic reconnection, traffic monitoring, pod log streaming, a REST API, and AI assistant integration.
Tools
The tool list has not been reviewed yet.
Setup
On macOS, run brew install kubefwd. On Linux, download a deb, rpm, or tar.gz package from releases. On Windows, use winget install txn2.kubefwd or Scoop. Docker is also supported. kubectl must be configured with access to a Kubernetes cluster before use.
Fit and risk
Not for
- Local development without a Kubernetes cluster.
- Environments without cluster access or the ability to grant root/sudo privileges.
- Simple single-service forwarding where service-name resolution, auto-reconnect, and monitoring are unnecessary.
Required permissions
- A kubectl configuration with access to the target Kubernetes cluster is required.
- Root/sudo access is required to modify /etc/hosts and network interfaces.
- Access through the Kubernetes API is required to establish service port forwards.
Risks and side effects
- The tool modifies the local /etc/hosts file and network interfaces, which can affect local service-name resolution.
- Cluster services are forwarded to the local machine, so local applications may access services in the development cluster.
- The tool requires privileged execution; its permissions should be appropriate for the target development environment.
Troubleshooting
- Verify that kubectl is configured and can access the target cluster.
- Verify that the runtime environment has root/sudo access.
- Check that /etc/hosts and network interfaces are writable.
- Confirm the target namespace, label selectors, and service ports.
- If connections drop, check pod status and cluster connectivity; kubefwd supports automatic reconnection.
Use cases
Run an application locally while accessing databases, authentication services, caches, or APIs in a development cluster.
Bulk-forward services in a namespace and access them by service name.
Use the TUI to inspect service status, traffic metrics, and container logs.
Control forwarding programmatically through the REST API.
Supported clients
Claude CodePartial support
CursorPartial support