OfficialVerified

Harness MCP Server

Harness.io platform resources and CI/CD pipelines managed via 11 unified tools.

Data last scanned today · Reviewed today

43 9 dangerous tools29 tools★ 97TypeScriptMIT

Overview

The Harness MCP Server provides AI agents with comprehensive access to the Harness.io platform by consolidating thousands of potential API endpoints into 11 streamlined tools. By utilizing a registry-based dispatch system, the server enables interaction with over 245 resource types, including pipelines, feature flags, cloud cost metrics, and software supply chain data without overwhelming the LLM's context window. The server supports complex, multi-project workflows through dynamic discovery of organizations and projects, eliminating the need for hardcoded environment variables. It features 35 pre-built prompt templates for tasks such as debugging pipeline failures, analyzing DORA metrics, and auditing access controls. It is designed to be transport-agnostic, supporting stdio for local clients, HTTP for remote deployments, and compatibility with Docker or Kubernetes.

Our verdict

With a security score of 40/100, this server is classified as high-risk. This rating stems from the fact that the project is community-maintained rather than official, and both its authentication methods and read-only capabilities have not yet undergone editorial or security review. It is recommended for use only in non-sensitive or isolated development environments where the potential impact of unauthorized platform access is strictly contained.

Consolidates thousands of API endpoints into just 11 tools
Supports dynamic navigation of complex organizational project hierarchies
Includes 35 pre-built workflow prompt templates for common tasks
Maintained by 60 contributors with recent daily commit activity

Not an official, vendor-maintained Harness product
Authentication and read-only mode security status remains unreviewed
No verified security audit or official editorial oversight

Setup

Claude Desktop

{
  "mcpServers": {
    "harness-mcp-server": {
      "args": [
        "-y",
        "harness-mcp-v2"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
harness_describe	Discover available resource types, operations, and fields. No API call — returns local registry metadata.	low
harness_schema	Fetch exact YAML/JSON Schema definitions and examples for creating/updating resources.	low
harness_list	List resources of a given type with filtering, search, and pagination.	low
harness_get	Get a single resource by its identifier.	low
harness_create	Create a new resource. Supports inline and remote (Git-backed) pipelines. Prompts for user confirmation via elicitation.	medium
harness_update	Update an existing resource. Supports inline and remote (Git-backed) pipelines. Prompts for user confirmation via elicitation.	medium
harness_delete	Delete a resource. Prompts for user confirmation via elicitation. Destructive.	high
harness_execute	Execute an action on a resource (run/retry pipeline, import pipeline from Git, toggle flag, sync app). Prompts for user confirmation via elicitation.	high
harness_search	Search across Harness resource types with a single query.	low
harness_diagnose	Diagnose pipeline, connector, delegate, and gitops_application resources.	low

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›What authentication is required to use this MCP server?

You need a Harness API key in the form of a PAT or SAT. The server automatically extracts the account ID from these tokens, so you generally do not need to provide it separately.

›Can I use the hosted Harness MCP service instead of running the server locally?

Yes, if your account has the service enabled. Note that the hosted version uses Harness Platform OAuth instead of an API key and requires configuration by Harness Support.

›How does this server handle multiple Harness projects?

The server features dynamic discovery of organizations and projects. This allows agents to navigate your entire account hierarchy without requiring hardcoded environment variables.

›Can I limit the tools exposed by the server?

Yes, the server supports toolset filtering, which allows you to expose only the specific Harness toolsets you need for your use case.

›Does this server support both local and remote deployments?

Yes, it supports stdio transport for local clients like Claude Desktop or Cursor, and HTTP transport for remote or shared deployments.

›Is Ansible support included by default?

Ansible coverage is available as an opt-in feature. You can enable it when you need to access inventory and playbook data.