mcpSource-backedReview first Safety ✓ Privacy ✓

Harness MCP Server for Claude

Access the entire Harness.io DevOps platform from Claude — CI/CD pipelines, GitOps, feature flags, cloud cost, security testing, chaos engineering, and more — through 11 consolidated tools covering 216 resource types across 36 toolsets, with 32 built-in prompt templates.

by Harness·added 2026-06-18·

Claude Code Codex Cursor Claude Desktop

HarnessClaude CodeCodexCursorClaude Desktop

Install

Source

claude mcp add harness -e HARNESS_API_KEY=pat.ACCOUNT_ID.TOKEN_ID.SECRET -- npx harness-mcp-v2@latest

Readiness

TrustReview first
Sourcesource-backed
Safety notesPresent
ReviewedYes

Documentation Source repository Registry JSON · LLM text

Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

Tools can create and execute CI/CD pipelines, deploy services, configure feature flags, and run chaos experiments — all affecting live environments.
The `harness_create` and `harness_execute` tools perform live platform operations; confirm before executing destructive or production actions.
Use `HARNESS_DEFAULT_ORG` and `HARNESS_DEFAULT_PROJECT` to scope operations and limit blast radius.

Privacy notes

Pipeline configurations, deployment histories, cost data, security findings, feature flag targeting rules, and IDP content from your Harness account are surfaced in Claude's context.
Your `HARNESS_API_KEY` grants broad platform access — treat it as a secret.

Prerequisites

A Harness account — log in at app.harness.io.
A Harness API key: My Profile → API Keys → + New API Key → + Token. PAT/SAT tokens embed the account ID automatically.
Node.js with `npx` available.
An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type: cli
Troubleshooting: No

Source repository stats

Scope: Source repo

Collection metadata

Estimated setup: 10 minutes
Difficulty: intermediate

Tool listing metadata

Website: https://harness.io
Disclosure: Harness is a commercial DevOps platform. The MCP server is officially maintained by Harness.

Full copyable content

{
  "mcpServers": {
    "harness": {
      "command": "npx",
      "args": ["harness-mcp-v2@latest"],
      "env": {
        "HARNESS_API_KEY": "pat.ACCOUNT_ID.TOKEN_ID.SECRET"
      }
    }
  }
}

About this resource

Overview

The Harness MCP Server is the official Model Context Protocol server from Harness. Rather than mapping one tool per API endpoint (which would produce 240+ tools), it uses a registry-based dispatch with 11 consolidated tools and 216 resource types — keeping LLM tool selection manageable while covering the entire Harness platform: CI/CD, GitOps, Feature Flags, Cloud Cost Management, Security Testing, Chaos Engineering, IDP, Governance, and more. Includes 32 built-in prompt templates. Licensed under MIT.

Key capabilities

CI/CD — list and debug pipeline executions, trigger builds, approve pending pipelines.
GitOps — manage services, environments, and deployment strategies.
Feature Flags — plan rollouts, create flags, review flag state.
Cloud Cost Management — review recommendations, audit waste.
Security Testing — triage vulnerabilities and review scan results.
Chaos Engineering — list and review chaos experiment results.
IDP & Knowledge Graph — search internal developer portal and knowledge resources.
Multi-project discovery — agents navigate org → project → resource hierarchies dynamically.
32 prompt templates — pre-built prompts for common workflows like "build & deploy app", "debug failed pipeline", "review DORA metrics", "triage vulnerabilities".

Tools (11 consolidated)

Tool	Purpose
`harness_list`	List resources of any of 216 types
`harness_get`	Get details of a specific resource
`harness_create`	Create a new resource
`harness_update`	Update an existing resource
`harness_delete`	Delete a resource
`harness_execute`	Trigger an execution (pipeline, chaos exp, etc.)
`harness_approve`	Approve a pending step or execution
`harness_search`	Search across resource types
`harness_analyze`	Analyze resource data and relationships
`harness_prompt`	Invoke a built-in prompt template
`harness_config`	Inspect server configuration and toolsets

How it compares

Server	CI/CD	GitOps	Feature Flags	Cost mgmt	Chaos	Tools
Harness MCP	Yes	Yes	Yes	Yes	Yes	11 (216 types)
GitHub Actions MCP	Yes	Limited	No	No	No	30+
ArgoCD MCP	No	Yes	No	No	No	15+
Jenkins MCP	Yes	No	No	No	No	10+

11 tools covering 216 resource types is uniquely scalable — adding new Harness platform coverage requires only a declarative data file, not new tool registrations.

Installation

Claude Code

claude mcp add harness \
  -e HARNESS_API_KEY=pat.ACCOUNT_ID.TOKEN_ID.SECRET \
  -- npx harness-mcp-v2@latest

PAT tokens embed the account ID — no separate HARNESS_ACCOUNT_ID needed for PAT/SAT tokens.

Claude Desktop

{
  "mcpServers": {
    "harness": {
      "command": "npx",
      "args": ["harness-mcp-v2@latest"],
      "env": {
        "HARNESS_API_KEY": "pat.ACCOUNT_ID.TOKEN_ID.SECRET",
        "HARNESS_DEFAULT_ORG": "default",
        "HARNESS_DEFAULT_PROJECT": "my_project"
      }
    }
  }
}

HTTP transport (shared deployments)

HARNESS_API_KEY=pat.ACCOUNT_ID.TOKEN_ID.SECRET npx harness-mcp-v2 http --port 8080

Requirements

A Harness account with a PAT/SAT API token.
Node.js with npx.
An MCP client (Claude Code or Claude Desktop).

Security

Scope HARNESS_DEFAULT_ORG and HARNESS_DEFAULT_PROJECT to limit blast radius.
Review pipeline executions and chaos experiments before confirming — they affect production.

Source Verification Notes

Verified on 2026-06-18:

Official GitHub repository harness/mcp-server (MIT) documents the harness-mcp-v2 npm package, HARNESS_API_KEY configuration with embedded account ID in PAT/SAT tokens, the 11 consolidated tools, 216 resource types across 36 toolsets, 32 prompt templates, stdio and HTTP transports, and the hosted Harness MCP option requiring Harness Support enablement.
Harness API documentation at developer.harness.io/docs/platform/automation/api/api-quickstart/ (HTTP 200) covers API key creation and authentication.
Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the stdio connector pattern used above.

#harness #cicd #devops #gitops #feature-flags #chaos-engineering #cloud-cost

Source citations

Add this badge to your README

Show that Harness MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/harness-mcp-server.svg)](https://heyclau.de/entry/mcp/harness-mcp-server)

How it compares

Harness MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	Harness MCP Server for Claude Access the entire Harness.io DevOps platform from Claude — CI/CD pipelines, GitOps, feature flags, cloud cost, security testing, chaos engineering, and more — through 11 consolidated tools covering 216 resource types across 36 toolsets, with 32 built-in prompt templates. Open dossier	ConfigCat MCP Server for Claude Manage ConfigCat feature flags from Claude — create, update, and delete flags and targeting rules, manage environments, find and clean up stale flags, and audit change history — with the official ConfigCat MCP server and its 52 tools for the full ConfigCat Management API. Open dossier	LaunchDarkly MCP Server for Claude Manage LaunchDarkly feature flags, AI configs, environments, and audit logs from Claude — with the official LaunchDarkly Model Context Protocol server backed by the LaunchDarkly REST API. Open dossier	Portainer MCP Server for Claude Manage Docker and Kubernetes infrastructure from Claude — list environments, inspect containers, manage GitOps workflows, troubleshoot resources, and proxy Docker/K8s API calls — with the official Portainer MCP server generated from the Portainer OpenAPI spec. Open dossier
Trust
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Category	mcp	mcp	mcp	mcp
Source	source-backed	source-backed	source-backed	source-backed
Author	Harness	ConfigCat	LaunchDarkly	Portainer
Added	2026-06-18	2026-06-18	2026-06-18	2026-06-18
Platforms	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓Tools can create and execute CI/CD pipelines, deploy services, configure feature flags, and run chaos experiments — all affecting live environments. The `harness_create` and `harness_execute` tools perform live platform operations; confirm before executing destructive or production actions. Use `HARNESS_DEFAULT_ORG` and `HARNESS_DEFAULT_PROJECT` to scope operations and limit blast radius.	✓Tools can create, update, and delete feature flags, targeting rules, environments, and segments — changes affect live feature flag configuration. Use `list-staleflags` before deleting flags to identify zombie flags and avoid breaking active SDKs.	✓Feature flag operations include create, update (patch), and delete — changes affect live targeting rules for all users in the environment. Audit log and code reference reads are non-destructive, but flag patch and delete operations are irreversible and will affect production traffic immediately. Scope the API key to the minimum required permissions (read-only for analysis workflows, write only for flag management workflows).	✓The server exposes the full Portainer REST API — including container start/stop/delete, stack deployment, and Kubernetes resource management. The API proxy tools forward requests directly to your Docker/Kubernetes API — review before executing any destructive operations. For team deployments over HTTP, the container requires TLS (either BYO certificates or a TLS-terminated reverse proxy) — do not expose plaintext on the public internet.
Privacy notes	✓Pipeline configurations, deployment histories, cost data, security findings, feature flag targeting rules, and IDP content from your Harness account are surfaced in Claude's context. Your `HARNESS_API_KEY` grants broad platform access — treat it as a secret.	✓Feature flag configurations, targeting rules, audience segments, SDK keys, and audit log entries from your ConfigCat account are surfaced in Claude's context. `CONFIGCAT_API_USER` and `CONFIGCAT_API_PASS` are Management API credentials — keep them in the MCP config env and never commit them to version control.	✓Feature flag definitions, targeting rules, user segments, AI config prompts, environment configurations, and audit log entries from your LaunchDarkly project are surfaced in Claude's context. Your API key is passed as a CLI argument — store it in Claude Code's MCP config rather than in shell history; rotate keys from the LaunchDarkly Authorization page.	✓Container names, environment configurations, Docker/Kubernetes resource details, and GitOps credentials from your Portainer instance are surfaced in Claude's context. Your Portainer API key grants the same access as your Portainer user account — treat it as a secret.
Prerequisites	A Harness account — log in at app.harness.io. A Harness API key: My Profile → API Keys → + New API Key → + Token. PAT/SAT tokens embed the account ID automatically. Node.js with `npx` available. An MCP client such as Claude Code or Claude Desktop.	A ConfigCat account — log in at app.configcat.com. Management API credentials: My Account → Public API Credentials → + Create new credentials (these are separate from SDK keys). Node.js with `npx` available. An MCP client such as Claude Code or Claude Desktop.	A LaunchDarkly account and an API key from the LaunchDarkly Authorization page (Settings → Authorization → API Keys). Node.js (v18+) with `npx` available, and an MCP client such as Claude Code or Claude Desktop.	A running Portainer instance (CE or Business Edition). A Portainer API key: My Account → Access tokens → Add access token. Python with `uv` installed: `pip install uv` or `brew install uv`. Match the MCP server minor version to your Portainer instance minor version (e.g., `mcp-portainer~=2.42.0` for Portainer 2.42.x).
Install	`claude mcp add harness -e HARNESS_API_KEY=pat.ACCOUNT_ID.TOKEN_ID.SECRET -- npx harness-mcp-v2@latest`	`claude mcp add configcat -e CONFIGCAT_API_USER=<your-api-user> -e CONFIGCAT_API_PASS=<your-api-pass> -- npx -y @configcat/mcp-server`	`claude mcp add launchdarkly -- npx -y --package @launchdarkly/mcp-server -- mcp start --api-key YOUR_API_KEY`	`claude mcp add portainer -e PORTAINER_URL=https://portainer.example.com -e PORTAINER_API_KEY=ptr_xxxxx -- uvx --from "mcp-portainer~=2.42.0" mcp-portainer`
Config	`{ "mcpServers": { "harness": { "command": "npx", "args": ["harness-mcp-v2@latest"], "env": { "HARNESS_API_KEY": "pat.ACCOUNT_ID.TOKEN_ID.SECRET", "HARNESS_DEFAULT_ORG": "default", "HARNESS_DEFAULT_PROJECT": "your_project" } } } }`	`{ "mcpServers": { "configcat": { "command": "npx", "args": ["-y", "@configcat/mcp-server"], "env": { "CONFIGCAT_API_USER": "<your-api-user>", "CONFIGCAT_API_PASS": "<your-api-pass>", "CONFIGCAT_BASE_URL": "https://api.configcat.com" } } } }`	`{ "mcpServers": { "LaunchDarkly": { "command": "npx", "args": ["-y", "--package", "@launchdarkly/mcp-server", "--", "mcp", "start", "--api-key", "YOUR_API_KEY"] } } }`	`{ "mcpServers": { "portainer": { "command": "uvx", "args": ["--from", "mcp-portainer~=2.42.0", "mcp-portainer"], "env": { "PORTAINER_URL": "https://portainer.example.com", "PORTAINER_API_KEY": "ptr_xxxxx", "PORTAINER_TLS_VERIFY": "0" } } } }`
Citations	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationdeveloper.harness.io Websiteharness.io	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationraw.githubusercontent.com	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationgithub.com	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationgithub.com
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed

Signals

Loading live community signals…

Safety notes

Privacy notes

Prerequisites

Schema details

About this resource

Overview

Key capabilities

Tools (11 consolidated)

How it compares

Installation

Claude Code

Claude Desktop

HTTP transport (shared deployments)

Requirements

Security

Source Verification Notes

Source citations

Add this badge to your README

How it compares

Related resources

ConfigCat MCP Server for Claude

LaunchDarkly MCP Server for Claude

Portainer MCP Server for Claude

Argo CD MCP Server

Signals