harness-mcp-v2 3.2.21 → 3.2.23

package/README.md

@@ -2,7 +2,7 @@
 
 [![MCP Toplist](https://mcptoplist.com/badge/glama%2Fharness%2Fmcp-server.svg)](https://mcptoplist.com/server/glama%2Fharness%2Fmcp-server)
 
-An MCP (Model Context Protocol) server that gives AI agents full access to the Harness.io platform through 11 consolidated tools and 240 resource types.
+An MCP (Model Context Protocol) server that gives AI agents full access to the Harness.io platform through 11 consolidated tools and 243 resource types.
 
 ## Why Use This MCP Server
 
@@ -10,8 +10,8 @@ Most MCP servers map one tool per API endpoint. For a platform as broad as Harne
 
 This server is built differently:
 
-- **11 tools, 240 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.** 39 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 coverage is available when you need inventory and playbook data.
+- **11 tools, 243 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.** 40 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 coverage is available when you need inventory and playbook data.
 - **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.
@@ -870,7 +870,7 @@ Maintainers can refresh the vendored entity snapshots with `pnpm sync-entity-sch
 
 ### Pipeline Run Workflow (Recommended)
 
-Use this sequence to reduce execution-time input errors:
+For v0 pipelines, use this sequence to reduce execution-time input errors:
 
 1. **Discover required runtime inputs**
   - `harness_get(resource_type="runtime_input_template", resource_id="<pipeline_id>")`
@@ -905,6 +905,14 @@ Use this sequence to reduce execution-time input errors:
 4. **Optional: combine both**
   - Use `input_set_ids` for the base shape and `inputs` for simple overrides.
 
+For v1 pipelines:
+
+1. Fetch `harness_get(resource_type="runtime_input_template_v1", resource_id="<pipeline_id>")`.
+   For Git-backed pipelines, pass `branch_name`, `connector_ref`, and `repo_name` through `params`.
+2. Use each returned `inputs[].details.name` as a top-level key in `harness_execute.inputs`.
+3. Run `harness_execute(resource_type="pipeline_v1", action="run", resource_id="<pipeline_id>", inputs={...})`.
+   The server wraps these values under an `inputs:` YAML root and sends the API's `inputs_yaml` body.
+
 If required fields are unresolved, the tool returns a pre-flight error with expected keys and suggested input sets. You can inspect available shorthand mappings with `harness_describe(resource_type="pipeline")` (`executeActions.run.inputShorthands`).
 
 ### Dynamic Pipeline Execution
@@ -1205,7 +1213,7 @@ Harness pipelines can be stored in three ways:
 
 ## Resource Types
 
-240 resource types organized across 39 toolsets. Each resource type supports a subset of CRUD operations and optional execute actions.
+243 resource types organized across 40 toolsets. Each resource type supports a subset of CRUD operations and optional execute actions.
 
 ### Platform
 
@@ -1230,10 +1238,12 @@ Harness pipelines can be stored in three ways:
 | `pipeline_summary`             |      | x   |        |        |        |                     |
 | `input_set`                    | x    | x   | x      | x      | x      |                     |
 | `runtime_input_template`       |      | x   |        |        |        |                     |
+| `runtime_input_template_v1`    |      | x   |        |        |        |                     |
+| `pipeline_resolved_yaml`       |      | x   |        |        |        |                     |
 | `approval_instance`            | x    |     |        |        |        | `approve`, `reject` |
 
 
-Only one pipeline YAML resource type is loaded at startup. By default `HARNESS_PIPELINE_VERSION=0` exposes `pipeline` and hides `pipeline_v1`; set `HARNESS_PIPELINE_VERSION=1` to expose `pipeline_v1` and hide `pipeline`. In HTTP mode, include `x-harness-pipeline-version: 0` or `1` on the `initialize` request to choose the version for that session.
+Both pipeline YAML resource types are available when the pipelines toolset is enabled. `HARNESS_PIPELINE_VERSION` and the HTTP `x-harness-pipeline-version` initialization header select the default version preference; they do not hide the other version.
 
 ### AI Agents
 
@@ -1829,7 +1839,7 @@ Security exemption execute workflow:
 
 ## Toolset Filtering
 
-By default, 39 of 40 toolsets are enabled. One toolset is opt-in and excluded from the defaults:
+By default, 40 of 41 toolsets are enabled. One toolset is opt-in and excluded from the defaults:
 
 - **`ansible`** — Harness Ansible (inventories, playbooks, hosts, activity). Opt-in because it is project-scoped and adds concepts many users do not need.
 
@@ -1927,8 +1937,8 @@ Available toolset names:
                           |
                  +--------v---------+
                 |    Registry       |  <-- Declarative resource definitions
-                |  39 Toolsets      |      (data files, not code)
-                |  240 Resource Types|
+                |  40 Toolsets      |      (data files, not code)
+                |  243 Resource Types|
                  +--------+---------+
                           |
                  +--------v---------+

package/build/data/schemas/v0/pipeline.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"pipeline.d.ts","sourceRoot":"","sources":["../../../../src/data/schemas/v0/pipeline.ts"],"names":[],"mappings":"AAGA,QAAA,MAAM,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAswxH/B,CAAC;AACF,eAAe,MAAM,CAAC"}
+{"version":3,"file":"pipeline.d.ts","sourceRoot":"","sources":["../../../../src/data/schemas/v0/pipeline.ts"],"names":[],"mappings":"AAGA,QAAA,MAAM,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAkgzH/B,CAAC;AACF,eAAe,MAAM,CAAC"}