Ctrlk
Sign UpGet a DemoContact Us
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Harness MCP Server

Give AI agents full access to the Harness platform through 11 consolidated tools and 139 resource types using the Model Context Protocol (MCP).

The Harness MCP Server is an open-source Model Context Protocol server that gives AI agents full access to the Harness platform. It uses a registry-based dispatch system that routes 11 consolidated tools (harness_list, harness_get, harness_create, and others) to 139 resource types across 30 toolsets, covering CI/CD, GitOps, Feature Management & Experimentation, Cloud Cost Management, Security Testing, Chaos Engineering, Internal Developer Portal, Software Supply Chain, and more.

Unlike MCP servers that map one tool per API endpoint (which degrades LLM tool-selection accuracy as tool count grows), this server keeps the tool count small and the schema footprint minimal. Agents discover organizations and projects dynamically, so multi-project workflows work out of the box without hardcoded environment variables. Twenty-seven pre-built prompt templates cover common workflows such as debugging failed pipelines, reviewing DORA metrics, triaging vulnerabilities, and optimizing cloud costs.

What you will learn in this topic

By the end of this topic, you will be able to:

Before you begin

Before you configure MCP server, ensure you have the following:

  • Harness API key: A personal access token (PAT) in the format pat.<accountId>.<tokenId>.<secret>. The account ID is auto-extracted from PAT tokens. To create one, go to My Profile > API Keys > + New API Key, then create a Token. Go to Manage API Keys to review detailed instructions.

  • Node.js: Required when you use npx or npm install. This is not required for Docker.

If you use the Harness Hosted MCP endpoint, you need to authenticate with OAuth through Harness ID. This does not need an API key in your client configuration.

If your Harness account signs in through a SAML or OIDC Identity Provider, an administrator must add the MCP-specific ACS URL or redirect URI to that Identity Provider before you connect. For more information, see Single Sign-On (SSO) for Harness MCP.

Quick start

This set up does not require any installation. Run the server directly with npx command described below:

The server defaults to stdio transport (for Claude Desktop, Cursor, Windsurf, and similar clients). For remote or shared deployments, use http as described below:

Once the server runs, go to Configure your AI client to connect your editor or terminal.

Install with an alternative method

In this set up, use a global install or a source build when npx does not fit your environment.

Global install

Build from source

CLI usage

Option
Description

--port <number>

Port for HTTP transport (default: 3000, or PORT env var)

--help

Show help message and exit

--version

Print version and exit

How it works

The image below describes the flow of control from AI agent (such as Claude) to Harness REST API.

Flow of control from an AI agent through the MCP Server, registry, and HarnessClient to the Harness REST API
Click to view full size image

  1. Tools are generic verbs (harness_list, harness_get, and others) that accept a resource_type parameter to route to the correct API endpoint.

  2. The Registry maps each resource_type to a declarative ResourceDefinition specifying the HTTP method, URL path, parameter mappings, and response extraction.

  3. Dispatch resolves the resource definition, builds the HTTP request, calls the Harness API, and extracts the relevant response data.

  4. Toolset filtering controls which resource definitions load at startup.

  5. Deep links are automatically appended to responses, providing direct Harness UI URLs.

  6. Compact mode strips verbose metadata from list results to minimize token usage.

Next steps

PreviousAnthropic Connector
NextConfigure AI Clients

Last updated

Was this helpful?