M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionkubefwdBulk Kubernetes service forwarding for local development.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS34 / 100 · D76 / 100 · B
Reliability2 / 2013 / 20
Security and permissions6 / 2014 / 20
Maintenance9 / 2018 / 20
Documentation10 / 2017 / 20
Setup experience7 / 2014 / 20
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.
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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.
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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.
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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.
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015