run-pipeline

Orchestrate Harness pipeline runs, status checks, and approvals via MCP server.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill run-pipeline-thisrohangupta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-pipeline
Source: https://github.com/thisrohangupta/cursor-harness-plugin/tree/main/skills/run-pipeline
Command: npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill run-pipeline-thisrohangupta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires harness_mcp, and includes scripts (resource) components.

What problem does it solve?

This Skill unit provides a way to manage Harness pipelines, enabling you to run, debug, and monitor them effectively, without navigating through the Harness UI.

Core Features & Use Cases

  • Execute Pipeline Runs: Trigger and oversee pipeline executions.
  • Monitor and Manage Executions: View status, handle approvals, and retry or abort runs.
  • Use Case: Suppose you have a deployment that just failed, you can use this Skill to quickly retry the failed pipeline execution or abort if necessary.

Quick Start

Run the ci-pipeline to trigger a pipeline execution for your CI process.

Frequently Asked Questions about run-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger and monitor Harness pipeline executions without using the UI?

You can trigger and monitor Harness pipeline executions by orchestrating them directly via the MCP server. This allows you to run pipelines, check their status, and handle approvals programmatically.

Can I retry a failed Harness pipeline deployment programmatically?

Yes, you can retry failed Harness pipeline deployments programmatically through MCP execution control. The Skill facilitates retrying or aborting pipeline runs as needed for fast error recovery.

What is the best way to handle pipeline approvals in automated workflows?

Handling pipeline approvals in automated workflows is managed by orchestrating execution control via the Harness MCP server. It facilitates programmatic approval handling within various workflow contexts.

Do I need the harness_mcp server to manage CI/CD pipeline runs?

Yes, you need the harness_mcp server configured to manage CI/CD pipeline runs. This Skill depends on it to orchestrate pipeline execution, monitor status, and handle approvals.

Why use MCP for pipeline management instead of standard CI/CD interfaces?

Using MCP for pipeline management allows direct execution control and monitoring of Harness pipelines without UI navigation. It provides strong error recovery mechanisms for overseeing runs and approvals.

What are the limitations of managing pipeline executions via MCP?

Managing pipeline executions via MCP is limited to operations supported by the harness_mcp server, such as triggering runs and handling approvals. Complex UI-specific configurations may still require the Harness interface.