create-environment

Generate Harness environment YAML and deploy it via MCP.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill create-environment-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-environment
Source: https://github.com/harness/harness-skills/tree/main/skills/create-environment
Command: npx skills add https://github.com/harness/harness-skills --skill create-environment-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate Harness Environment YAML and deploy via MCP to create and manage environments across dev/staging/production with variable overrides and manifest configurations.

Core Features & Use Cases

  • Creates PreProduction or Production environments with per-environment variables and overrides
  • Supports multi-environment setups (dev, staging, prod) and manifest overrides
  • Pushes the environment to Harness using the MCP tool

Quick Start

Provide the environment details (name, identifier, type, variables, and overrides) and run the MCP create call to deploy the environment.

Frequently Asked Questions about create-environment

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

FAQPage Schema
How do I automate Harness environment creation using YAML and MCP?

You can automate Harness environment creation by providing structured YAML with environment details like name, identifier, type, variables, and overrides, which executes an MCP create call to deploy the configuration directly to Harness.

What is the best way to set up multiple Harness environments like dev, staging, and prod?

The best way to set up multiple environments is defining a multi-environment configuration in YAML with per-environment variables and manifest overrides, then applying it via the MCP tool to deploy PreProduction and Production environments.

Can I use manifest overrides and variables when deploying a Harness environment?

Yes, you can use manifest overrides and variables when deploying a Harness environment by defining them within your structured YAML input before executing the MCP create call to apply the specific configurations.

What do I need to provide to generate and deploy a Harness environment YAML?

To generate and deploy a Harness environment YAML, you need to provide the environment name, identifier, type, variables, and overrides as structured input so the MCP tool can execute the resource creation call.

Does this MCP environment setup support both PreProduction and Production environment types?

Yes, the MCP environment setup supports both PreProduction and Production environment types, allowing you to specify the desired type in your YAML input to manage deployments across different stages.

Why should I use YAML to manage Harness environment variables instead of manual configuration?

Using YAML to manage Harness environment variables enables automated, repeatable deployments with per-environment overrides, eliminating manual configuration errors and streamlining multi-environment setups via MCP.