create-infrastructure

Automate Harness infrastructure definition YAML and deployment targets via MCP v2.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manages and automates the definition of deployment targets for Harness infrastructure, streamlining the setup and configuration of where workloads will run.

Core Features & Use Cases

  • Infrastructure Definition: Automates the generation of Harness Infrastructure Definition YAML for various infrastructure types.
  • Deployment Target Setup: Facilitates the creation of KubernetesDirect, GKE, AKS, ECS, AWS Lambda, Azure Web Apps, and PDC deployments.
  • MCP Integration: Leverages Harness MCP v2 to create and manage infrastructure through code, reducing manual configuration overhead.

Quick Start

Generate and create a KubernetesDirect infrastructure definition for 'prod' by running 'create-infrastructure prod'.

Frequently Asked Questions about create-infrastructure

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

FAQPage Schema
How do I automate Harness infrastructure definition for Kubernetes deployment targets?

You can automate infrastructure definition for Kubernetes deployment targets by generating YAML and executing it via Harness MCP v2. This Skill creates KubernetesDirect definitions, requiring a pre-existing cluster connector and environment to function properly.

What infrastructure types does Harness MCP v2 support for deployment target setup?

Harness MCP v2 supports deployment target setup for KubernetesDirect, GKE, AKS, ECS, AWS Lambda, Azure Web Apps, and PDC. It automates the generation and creation of infrastructure definitions across these varied environments.

Do I need pre-existing connectors and environments to create infrastructure definitions in Harness?

Yes, you need pre-existing cloud or cluster connectors and environments to create infrastructure definitions in Harness. This Skill automates the YAML generation and deployment target mapping but relies on these foundational resources already being configured.

How do I define deployment targets as code for AWS Lambda and ECS?

You can define deployment targets as code for AWS Lambda and ECS by automating the generation of Harness Infrastructure Definition YAML. This Skill leverages MCP v2 to apply these configurations, streamlining the setup of where your serverless workloads run.

What's the best way to streamline Harness deployment target configuration across multiple environments?

The best way to streamline Harness deployment target configuration is automating Infrastructure Definition YAML generation through MCP v2. This reduces manual configuration overhead and allows you to efficiently map workloads to multiple infrastructure types like AKS or GKE.