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.

DimensionTestkube MCP ServerMCP server for the open testing platform built for AI-driven engineering teamsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS63 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance15 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Engineering teams already running Testkube on Kubernetes for automated testing
  • Platform and DevOps teams that want to manage test workflows and executions with AI assistants
  • Organizations looking to fold test result inspection and troubleshooting into AI workflows
  • 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 have not deployed Testkube or lack organization/environment credentials
  • Teams unwilling to expose a test access token to an AI client
  • General-purpose testing scenarios unrelated to Testkube or non-Kubernetes testing
  • 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
  • Read and use the Testkube access token (TK_ACCESS_TOKEN) for authentication
  • Access test workflows, executions, and artifacts within the specified Testkube organization and environment
  • Remote mode requires network access to https://api.testkube.io and the organization/environment path
  • 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 access token is a sensitive credential; leaking it could let others read or act on test data in the target organization/environment
  • AI assistants may trigger or affect real test executions and the Kubernetes test resources they consume
  • The remote streamable-http mode sends requests and credentials to the Testkube cloud control plane
  • Overly broad token permissions or wrong organization/environment IDs could reach unintended environments
  • 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 DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015