| FMRS | 63 / 100 · C | 80 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 8 / 20 | 14 / 20 | 13 / 20 |
|---|
| Security and permissions | 15 / 20 | 16 / 20 | 14 / 20 |
|---|
| Maintenance | 10 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 15 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 18 / 20 | 14 / 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.)
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - 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
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - 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
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - 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
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - 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 clients | Claude Desktop, Claude Code, Cursor, Devin Desktop | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Amp |
|---|
| Tools | 11 | 2 | 15 |
|---|