agentskillexchange Operate Harness pipelines, projects, and delivery resources from MCP-enabled agents
Use the Harness MCP Server when an agent needs governed access to Harness pipelines, services, environments, feature flags, cost data, and related platform resources from an MCP workflow instead of sending a human through the Harness UI.
Installation
Use the upstream install or setup path that matches your environment:
- npm install -g harness-mcp-v2
- git clone https://github.com/harness/mcp-server.git
- pnpm install
- pnpm build
Requirements and caveats from upstream:
- Works everywhere. Stdio transport for local clients (Claude Desktop, Cursor, Windsurf), HTTP transport for remote/shared deployments, Docker and Kubernetes ready.
- Important: The hosted MCP service uses Harness Platform OAuth, not HARNESS_API_KEY. It must also be enabled/configured per account by Harness Support before the endpoint can be used.
Basic usage or getting-started notes:
Before installing or running the server, you need a Harness API key:
Log in to your Harness account
Go to My Profile → API Keys → + New API Key
Extracted from upstream docs: https://raw.githubusercontent.com/harness/mcp-server/HEAD/README.md