Harness MCP Server

harness_create

Create Harness resources like pipelines, connectors, and environments by specifying a resource type and a YAML or JSON body. Supports remote pipelines with Git integration.

Instructions

Create a Harness resource. For pipelines: use body.yamlPipeline (YAML string, recommended) or body.pipeline (JSON). For remote pipelines, pass git details in params: external Git (store_type='REMOTE', connector_ref, repo_name, branch, file_path) or Harness Code (store_type='REMOTE', is_harness_code_repo=true, repo_name, branch, file_path). For others: call harness_describe for the body format.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource_type": "<resource_type>",
      "body": "<body>"
    },
    "name": "harness_create"
  }
}

Input Schema

Name	Required	Description
`resource_type`	Yes	The type of resource to create
`body`	Yes	The resource definition body (varies by resource type — typically the YAML or JSON spec)
`url`	No	A Harness UI URL — org and project are extracted automatically
`org_id`	No	Organization identifier (overrides default)
`project_id`	No	Project identifier (overrides default)
`params`	No	Additional parameters. For external Git pipelines: store_type='REMOTE', connector_ref, repo_name, branch, file_path, commit_msg. For Harness Code pipelines: store_type='REMOTE', is_harness_code_repo=true, repo_name, branch, file_path.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.3Jun 22, 2026

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate non-read-only, non-destructive, non-idempotent, open world. The description reinforces that this is a creation operation and adds context about body formats and git requirements, which is helpful beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with four sentences, front-loaded with the primary purpose, and every sentence adds essential guidance. No fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool's complexity (6 params, nested objects, no output schema), the description covers key usage patterns: pipeline creation, remote git, and directing to harness_describe for other resources. It is complete and actionable for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by specifying that for pipelines, body should be a YAML string or JSON, and for remote pipelines, params must include git details. This clarifies the intended use beyond the schema's generic descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a Harness resource' with a specific verb and resource. It distinguishes from sibling tools like harness_delete, harness_describe, etc., by providing explicit guidance for pipelines and deferring to harness_describe for other resource types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use and when-not-to-use: for pipelines, recommends YAML vs JSON; for remote pipelines, explains git details needed; for other resources, instructs to call harness_describe for the body format. This clearly differentiates usage scenarios and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server