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.

DimensionHarness MCP ServerOfficial MCP server giving AI agents full access to the Harness.io platform via 11 consolidated toolsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS63 / 100 · C76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions15 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Teams already using the Harness platform for CI/CD, GitOps, or Feature Flags management
  • Automated workflows that need to dynamically discover organizations/projects rather than hardcode configuration
  • Enterprises wanting centralized governance and audit logging via MCP gateways (Docker MCP Gateway, Portkey, LiteLLM, etc.)
  • 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
  • Teams not using the Harness platform
  • Use cases that require one tool per API endpoint with fine-grained per-tool permission control
  • Accounts without a Harness API key or without Harness Support enabling the hosted MCP service
  • 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
  • Requires a Harness personal access token (PAT) or service account token (SAT); the account ID is typically auto-extracted from the token
  • Has read-write access (create/update/delete/execute) by default; can be restricted to read-only with HARNESS_READ_ONLY=true
  • In multi-user HTTP mode, each session supplies its own x-harness-api-key — the server itself holds no credentials
  • 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
  • Mutating operations (create, update, delete, execute) can directly modify production pipelines, feature flags, or infrastructure configuration, so misuse can cause outages
  • Running HTTP transport on a non-loopback bind without HARNESS_MCP_AUTH_TOKEN can expose the server to unauthorized access; HARNESS_MCP_ALLOW_UNAUTHENTICATED_HTTP=true explicitly disables that protection
  • Audit logging omits raw request/response bodies by default, but HARNESS_LOG_UNSAFE_BODIES can enable them, which may then contain secrets
  • 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, Cursor, Devin DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1115