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.

DimensionK8M MCP 服务器管理Visually manage MCP servers and their tools inside K8MGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS44 / 100 · D76 / 100 · B
Reliability6 / 2013 / 20
Security and permissions8 / 2014 / 20
Maintenance14 / 2018 / 20
Documentation8 / 2017 / 20
Setup experience8 / 2014 / 20
Best for
  • Teams already using K8M to manage Kubernetes clusters who want unified MCP server management
  • Users who need to connect MCP servers over SSE and want a visual on/off control
  • 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
  • Users who need non-SSE MCP server types (the page states these are not supported)
  • Users without a K8M deployment who just want to use a single MCP server standalone
  • 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
  • Access to the K8M admin console (login required)
  • Server read/write and delete API permissions needed to manage MCP servers
  • Once an MCP server is enabled, LLM-driven calls execute with the caller's own cluster permissions
  • 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
  • Enabled MCP servers are registered automatically in conversations and may be invoked by the model
  • The server URL is user-supplied; pointing it at an untrusted remote service risks data exposure
  • Deleting or bulk-deleting server configurations is not easily reversible
  • The default credentials k8m/k8m create a clear unauthorized-access risk if not changed promptly
  • 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 Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015