Harness
Official Harness MCP for CI/CD, GitOps, feature management, cloud cost, security testing, chaos engineering, IDP, and software supply chain workflows.
Installation path
Choose Add Server, select Remote MCP, use HTTP, paste https://mcp.harness.io/mcp, set OAuth client ID to mcp-client when your client asks for one, then sign in with Harness ID. If OAuth is not enabled, use the local npx harness-mcp-v2 command with HARNESS_API_KEY.
Setup steps
- 01
Open Add Server
Configuration → MCP Registry → Add Server in Cosmos.
- 02
Pick the Remote MCP tab
- 03
Set the transport
Transport
HTTP - 04
Paste the server URL
URL
https://mcp.harness.io/mcp - 05
Choose authentication
OAuth with client ID mcp-client, then sign in with Harness ID.
- 06
Click Add, then enable
Toggle on the products that need it.
- 07
Fallback (no OAuth)
Add as a Local MCP with command npx, args harness-mcp-v2, env HARNESS_API_KEY=pat.xxx.
Local command
Suggested name: harness
HARNESS_API_KEY=pat.xxx npx harness-mcp-v2Local fallback defaults to stdio and requires a Harness PAT in HARNESS_API_KEY.
Remote URL
https://mcp.harness.io/mcpHosted MCP is for Harness SaaS with OAuth enabled. Dedicated clusters may need a region-specific MCP URL from Harness support.
Authentication
OAuth (client ID `mcp-client`): sign in with Harness ID. Local fallback uses HARNESS_API_KEY.
| Variable | Example | Required |
|---|---|---|
| HARNESS_API_KEY | pat.xxx | Yes |