MCP.so
ログイン

Harness MCP Server

@harness

Harness MCP Server について

This is the official repo for the Harness MCP server

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

harness

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "harness": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HARNESS_API_KEY",
        "-e",
        "HARNESS_DEFAULT_ORG_ID",
        "-e",
        "HARNESS_DEFAULT_PROJECT_ID",
        "-e",
        "HARNESS_BASE_URL",
        "harness/mcp-server:1.0.0-beta",
        "stdio"
      ],
      "env": {
        "HARNESS_API_KEY": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
        "HARNESS_BASE_URL": "https://app.harness.io"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Harness MCP Server?

Harness MCP Server is an MCP (Model Context Protocol) server that gives AI agents full access to the Harness.io platform through 11 consolidated tools and 212 resource types. It is built for developers and platform engineers who want to interact with Harness CI/CD, GitOps, Feature Flags, Cloud Cost Management, and more via natural language.

How to use Harness MCP Server?

Provide a Harness API key (PAT or SAT) and run the server with npx harness-mcp-v2@latest (no install required) or install globally via npm install -g harness-mcp-v2. Use stdio transport for local clients (Claude Desktop, Cursor, Devin Desktop) or HTTP transport for remote/shared deployments. Optionally set HARNESS_ORG and HARNESS_PROJECT for default scope; the agent can also discover orgs and projects dynamically.

Key features of Harness MCP Server

  • 11 tools, 212 resource types via registry-based dispatch
  • 32 pre-built prompt templates for common workflows
  • Covers CI/CD, GitOps, Feature Flags, Cloud Cost, Security Testing, and more
  • Multi-project workflows with dynamic org/project discovery
  • Zero-config start – just provide a Harness API key
  • Extensible by adding declarative data files – no new tool registration needed

Use cases of Harness MCP Server

  • Build and deploy applications end-to-end across multiple projects
  • Debug failed pipelines and triage security vulnerabilities
  • Review DORA metrics and optimize cloud costs
  • Plan and execute feature flag rollouts
  • Audit access control and approve pending pipelines

FAQ from Harness MCP Server

What do I need to get started with Harness MCP Server?

You need a Harness API key (PAT or SAT) created from your Harness account profile. No other credentials are required—the account ID is auto‑extracted from the token.

What authentication methods does Harness MCP Server support?

For local/self‑hosted use, it uses HARNESS_API_KEY. The hosted MCP service uses Harness Platform OAuth (not HARNESS_API_KEY) and must be enabled by Harness Support.

Can I run Harness MCP Server remotely or in a shared deployment?

Yes, use the HTTP transport. Set HARNESS_MCP_AUTH_TOKEN for shared or remotely reachable deployments. The server exposes endpoints like /mcp (JSON‑RPC and SSE) and /health. Multi‑user mode allows each session to authenticate with its own Harness API key.

What Harness resources does the server cover?

It provides 37 default toolsets covering CI/CD, GitOps, Feature Flags, Cloud Cost Management, Security Testing, Chaos Engineering, Database DevOps, Internal Developer Portal, Software Supply Chain, Infrastructure as Code Management, Governance, Service Overrides, and Knowledge Graph. Opt‑in Ansible coverage is also available.

Where does my data live when using Harness MCP Server?

All data is fetched from the Harness.io platform API. The server does not store data; it only proxies requests to Harness endpoints using the credentials provided.

コメント

「その他」の他のコンテンツ