Skip to main content
Glama
harness

Harness MCP Server

Official
by harness
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

harness_create

Create Harness resources from YAML or JSON definitions, covering pipelines, input sets, connectors, and other supported types. Include account/org/project scope and remote git details to provision resources directly.

Instructions

Create a Harness resource. For pipelines/input sets: pass body as a YAML string directly (recommended for complex definitions), or use body.yamlPipeline (YAML string), or body.pipeline (JSON object). 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoA Harness UI URL — org, project, and supported resource_scope are extracted automatically
bodyYesThe resource definition body. For pipelines: pass a YAML string directly, or an object with yamlPipeline (YAML string) or pipeline (JSON object). For other resources: pass a JSON object
org_idNoOrganization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it.
paramsNoAdditional 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.
confirmNoSet to true to confirm the operation. Only required when the operation risk is medium_write or above (most write resources) AND the client cannot surface a confirmation prompt — e.g. managed MCP that does not advertise elicitation, or an elicitation that fails at runtime. Has no effect for low-risk creates. Does NOT override an explicit decline from a client that completed an elicitation prompt — a user's decline is authoritative.
project_idNoProject identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it.
resource_typeYesThe type of resource to create
resource_scopeNoScope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv3.2.22
    • changedInput schema / properties / org_id / description
      Previous value: -"Organization identifier (overrides default)"New value: +"Organization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it."
    • changedInput schema / properties / project_id / description
      Previous value: -"Project identifier (overrides default)"New value: +"Project identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it."
    • changedInput schema / properties / resource_scope / description
      Previous value: -"Scope for the operation. account: omit org/project (e.g. /v1/templates). org: org only. project: org+project. Auto-detected from url when present."New value: +"Scope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present."
  2. Changed1 schema field changedv3.2.21
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "agent",
-  "branch",
-  "chaos_action",
-  "chaos_dr_test",
-  "chaos_experiment",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_k8s_infrastructure",
-  "chaos_loadtest",
-  "chaos_probe",
-  "chaos_risk_scan",
-  "chaos_service",
-  "commit",
-  "connector",
-  "cost_budget",
-  "cost_budget_group",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "delegate_token",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_suite_evaluation",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_feature_flag_definition",
-  "fme_identity",
-  "fme_rule_based_segment",
-  "fme_segment",
-  "fme_segment_definition",
-  "freeze_window",
-  "gitops_application",
-  "gitops_applicationset",
-  "gitops_cluster_link",
-  "iacm_module",
-  "iacm_variable_set",
-  "iacm_workspace",
-  "idp_entity",
-  "incident",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "pr_reviewer",
-  "project",
-  "pull_request",
-  "repo_rule",
-  "repository",
-  "resource_group",
-  "role",
-  "role_assignment",
-  "scorecard",
-  "scorecard_check",
-  "scs_remediation_pr",
-  "security_exemption",
-  "security_exemption_bulk",
-  "service",
-  "service_account",
-  "service_override",
-  "space_rule",
-  "tag",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric",
-  "user_group"
-]New value: +[
+  "agent",
+  "branch",
+  "chaos_action",
+  "chaos_dr_test",
+  "chaos_experiment",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_k8s_infrastructure",
+  "chaos_loadtest",
+  "chaos_probe",
+  "chaos_risk_scan",
+  "chaos_service",
+  "commit",
+  "connector",
+  "cost_budget",
+  "cost_budget_group",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "delegate_token",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_suite_evaluation",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_environment",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_identity",
+  "fme_rule_based_segment",
+  "fme_segment",
+  "fme_segment_definition",
+  "freeze_window",
+  "gitops_application",
+  "gitops_applicationset",
+  "gitops_cluster_link",
+  "iacm_module",
+  "iacm_provider",
+  "iacm_variable_set",
+  "iacm_workspace",
+  "idp_entity",
+  "incident",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "pr_reviewer",
+  "project",
+  "pull_request",
+  "release_activity",
+  "release_process",
+  "repo_rule",
+  "repository",
+  "resource_group",
+  "role",
+  "role_assignment",
+  "scorecard",
+  "scorecard_check",
+  "scs_remediation_pr",
+  "security_exemption",
+  "security_exemption_bulk",
+  "service",
+  "service_account",
+  "service_override",
+  "space_rule",
+  "tag",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric",
+  "user_group"
+]
  3. Changed1 schema field changedv3.2.20
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "agent",
-  "branch",
-  "chaos_action",
-  "chaos_dr_test",
-  "chaos_experiment",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_probe",
-  "chaos_risk_scan",
-  "commit",
-  "connector",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "delegate_token",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_suite_evaluation",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_feature_flag_definition",
-  "fme_identity",
-  "fme_rule_based_segment",
-  "freeze_window",
-  "gitops_application",
-  "gitops_applicationset",
-  "gitops_cluster_link",
-  "idp_entity",
-  "incident",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "pr_reviewer",
-  "project",
-  "pull_request",
-  "repo_rule",
-  "repository",
-  "resource_group",
-  "role",
-  "role_assignment",
-  "scorecard",
-  "scorecard_check",
-  "scs_remediation_pr",
-  "security_exemption",
-  "security_exemption_bulk",
-  "service",
-  "service_account",
-  "service_override",
-  "space_rule",
-  "tag",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric",
-  "user_group"
-]New value: +[
+  "agent",
+  "branch",
+  "chaos_action",
+  "chaos_dr_test",
+  "chaos_experiment",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_k8s_infrastructure",
+  "chaos_loadtest",
+  "chaos_probe",
+  "chaos_risk_scan",
+  "chaos_service",
+  "commit",
+  "connector",
+  "cost_budget",
+  "cost_budget_group",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "delegate_token",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_suite_evaluation",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_identity",
+  "fme_rule_based_segment",
+  "fme_segment",
+  "fme_segment_definition",
+  "freeze_window",
+  "gitops_application",
+  "gitops_applicationset",
+  "gitops_cluster_link",
+  "iacm_module",
+  "iacm_variable_set",
+  "iacm_workspace",
+  "idp_entity",
+  "incident",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "pr_reviewer",
+  "project",
+  "pull_request",
+  "repo_rule",
+  "repository",
+  "resource_group",
+  "role",
+  "role_assignment",
+  "scorecard",
+  "scorecard_check",
+  "scs_remediation_pr",
+  "security_exemption",
+  "security_exemption_bulk",
+  "service",
+  "service_account",
+  "service_override",
+  "space_rule",
+  "tag",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric",
+  "user_group"
+]
  4. Changed1 schema field changedv3.2.17
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "agent",
-  "branch",
-  "chaos_action",
-  "chaos_dr_test",
-  "chaos_experiment",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_probe",
-  "commit",
-  "connector",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "delegate_token",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_suite_evaluation",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_feature_flag_definition",
-  "fme_identity",
-  "fme_rule_based_segment",
-  "freeze_window",
-  "gitops_application",
-  "gitops_applicationset",
-  "gitops_cluster_link",
-  "idp_entity",
-  "incident",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "pr_reviewer",
-  "project",
-  "pull_request",
-  "repo_rule",
-  "repository",
-  "resource_group",
-  "role",
-  "role_assignment",
-  "scorecard",
-  "scorecard_check",
-  "scs_remediation_pr",
-  "security_exemption",
-  "security_exemption_bulk",
-  "service",
-  "service_account",
-  "service_override",
-  "space_rule",
-  "tag",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric",
-  "user_group"
-]New value: +[
+  "agent",
+  "branch",
+  "chaos_action",
+  "chaos_dr_test",
+  "chaos_experiment",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_probe",
+  "chaos_risk_scan",
+  "commit",
+  "connector",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "delegate_token",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_suite_evaluation",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_identity",
+  "fme_rule_based_segment",
+  "freeze_window",
+  "gitops_application",
+  "gitops_applicationset",
+  "gitops_cluster_link",
+  "idp_entity",
+  "incident",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "pr_reviewer",
+  "project",
+  "pull_request",
+  "repo_rule",
+  "repository",
+  "resource_group",
+  "role",
+  "role_assignment",
+  "scorecard",
+  "scorecard_check",
+  "scs_remediation_pr",
+  "security_exemption",
+  "security_exemption_bulk",
+  "service",
+  "service_account",
+  "service_override",
+  "space_rule",
+  "tag",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric",
+  "user_group"
+]
  5. First observedv3.2.10

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the write nature is established without the description needing to restate it. The description adds useful behavioral context around input formats (YAML vs. JSON) and remote-pipeline parameter requirements, but does not disclose other behavioral traits like confirmation/risk or failure modes. This is adequate but not rich.

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 dense, information-rich, and front-loads the core action before branching into scenario-specific details. Every sentence covers a distinct case: basic create, YAML vs. JSON body formats, remote Git params, and a fallback for other resource types. There is no filler or repetition.

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

Completeness4/5

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

For a create tool with 8 parameters and a large resource_type enum, the description covers the most complex cases (pipelines, input sets, remote Git vs. Harness Code) and provides a sensible catch-all for other resource types via harness_describe. The output schema exists, so return values need not be described. It does not explain scope/org/project requirements, but those are fully covered in the schema, and the openWorldHint annotation further supports discoverability.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all parameters. The description does add a recommendation ('recommended for complex definitions') and scenario-to-parameter mappings for remote Git and Harness Code, but these largely echo what the params and body descriptions already state. It adds marginal value beyond the schema, not substantial new semantics.

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 opens with a specific verb and resource ('Create a Harness resource'), immediately establishing the operation. It goes on to distinguish key sub-flows (pipelines/input sets vs. remote pipelines vs. other resources), and the sibling list confirms the separation from harness_get/update/delete/list/describe. Nothing about the purpose is vague or tautological.

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

Usage Guidelines4/5

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

The description gives concrete usage guidance for the main branches: YAML strings for pipelines/input sets, git details for remote pipelines, and explicitly routes users to harness_describe for body formats of other resources. It lacks explicit 'when not to use this tool' guidance versus harness_update, but the create semantics and scenario-specific instructions provide clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/harness/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server