harness/mcp-server

线束MCP服务器2.0

一个MCP（模型上下文协议）服务器，通过11个整合工具和262种资源类型，为AI代理提供对 Harness.io 平台的完全访问权限。

为什么要用这个MCP服务器

大多数MCP服务器为每个API端点映射一个工具。对于像Harness这样广泛的平台，这意味着240+工具——而且随着工具数量增加，LLM在工具选择上会变得更差。上下文窗口充满了模式，每增加一个端点就意味着新的代码。

这台服务器的构建方式不同：

• 11 个工具，262 种资源类型。 基于注册表的调度系统将 harness_list、harness_get、harness_create 等路由到任何 Harness 资源——管道、服务、环境、组织、项目、功能标志、成本数据等。LLM 从11个工具中选择，而非数百个。
• 全方位平台覆盖。 42个默认工具集，涵盖CI/CD、GitOps、功能标志、云成本管理、安全测试、混沌工程、数据库DevOps、内部开发者门户、软件供应链、基础设施即代码管理、发布管理、治理、服务覆盖、知识图谱等。必要时提供可选加入的Ansible和可观测性评估覆盖。

Harness MCP Server 2.0

An MCP (Model Context Protocol) server that gives AI agents full access to the Harness.io platform through 11 consolidated tools and 263 resource types.

Why Use This MCP Server

Most MCP servers map one tool per API endpoint. For a platform as broad as Harness, that means 240+ tools — and LLMs get worse at tool selection as the count grows. Context windows fill up with schemas, and every new endpoint means new code.

This server is built differently:

• 11 tools, 263 resource types. A registry-based dispatch system routes harness_list, harness_get, harness_create, etc. to any Harness resource — pipelines, services, environments, orgs, projects, feature flags, cost data, and more. The LLM picks from 11 tools instead of hundreds.
• Full platform coverage. 42 default toolsets spanning CI/CD, GitOps, Feature Flags, Cloud Cost Management, Security Testing, Chaos Engineering, Database DevOps, Internal Developer Portal, Software Supply Chain, Infrastructure as Code Management, Release Management, Governance, Service Overrides, Knowledge Graph, and more. Opt-in Ansible and observability-evaluation coverage is available when needed.
• Multi-project workflows out of the box. Agents discover organizations and projects dynamically — no hardcoded env vars needed. Ask “show failed executions across all projects” and the agent can navigate the full account hierarchy.
• 35 prompt templates. Pre-built prompts for common workflows: build & deploy apps end-to-end, debug failed pipelines, review DORA metrics, triage vulnerabilities, optimize cloud costs, audit access control, plan feature flag rollouts, review pull requests, approve pending pipelines, and more.
• Works everywhere. Stdio transport for local clients (Claude Desktop, Cursor, Devin Desktop), HTTP transport for remote/shared deployments, Docker and Kubernetes ready.
• Zero-config start. Just provide a Harness API key. Account ID is auto-extracted from PAT and SAT tokens, org/project defaults are optional, and toolset filtering lets you expose only what you need.
• Extensible by design. Adding a new Harness resource means adding a declarative data file — no new tool registration, no schema changes, no prompt updates.

Prerequisites

Before installing or running the server, you need a Harness API key:

1. Log in to your Harness account
2. Go to My Profile → API Keys → + New API Key
3. Create a new Token under the API key — this generates a PAT or SAT in the format ...
4. Save the token somewhere secure — you’ll need it in the next step

For detailed instructions, see the Harness API Quickstart.

Quick Start

Option 0: Hosted Harness MCP