Home

kubefwd enables developers to work locally while accessing services running in Kubernetes. Connect to db:5432, auth:443, redis:6379—all by service name, exactly as in-cluster. No environment config, no Docker Compose. Just run kubefwd.

Get Started GitHub

Four Ways to Use kubefwd¶

Idle ModeClassic ModeREST APIMCP

Start without pre-specified services. Browse and forward interactively.

sudo -E kubefwd --tui

Browse namespaces and services visually
Forward exactly what you need
API and auto-reconnect enabled by default
Getting Started →

Forward all services in a namespace immediately.

sudo -E kubefwd svc -n my-namespace --tui

Backwards-compatible with all previous versions
Perfect for known workflows
Getting Started →

Programmatic control via 40+ HTTP endpoints.

sudo -E kubefwd  # Idle mode, API enabled
curl http://kubefwd.internal/api/v1/services

Add/remove namespaces and services dynamically
Query metrics and diagnostics
SSE event streaming
REST API →

Talk to your AI about your work, not about tools.

# Add to Claude Code
claude mcp add --transport stdio kubefwd -- kubefwd mcp

"Connect me to the staging database"
"Test my new API deployment"
"Why can't my app reach redis?"
MCP Integration →

🔌

Unique IP per Service Each service gets its own 127.x.x.x. Multiple databases on port 3306? No conflicts.

🔄

Auto-Reconnect Pods restart? kubefwd reconnects automatically with exponential backoff.

📊

Interactive TUI Browse namespaces, select services, monitor traffic, and stream logs.

🌐

Service Names Work Updates /etc/hosts so any app can access services by name.

# macOS
brew install txn2/tap/kubefwd

# Windows
scoop install kubefwd

# Then start exploring
sudo -E kubefwd --tui