Skip to main content
Glama
thisrohangupta

Harness MCP Server

by thisrohangupta
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HARNESS_API_KEYYesHarness personal access token or service account token.
HARNESS_BASE_URLNoBase URL for Harness API. Override for self-managed Harness.https://app.harness.io
HARNESS_ACCOUNT_IDNoHarness account identifier. Required when the API key is not a PAT token (i.e., not in format pat.<accountId>.<tokenId>.<secret>).
HARNESS_DEFAULT_ORG_IDNoDefault organization identifier.default
HARNESS_DEFAULT_PROJECT_IDNoDefault project identifier.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
harness_listA

List Harness resources with filtering and pagination. Accepts a Harness URL to auto-extract scope.

harness_getA

Get a Harness resource by ID. Accepts a Harness URL to auto-extract identifiers. For failure analysis, prefer harness_diagnose.

harness_createA

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.

harness_updateA

Update an existing Harness resource. You can pass a Harness URL to auto-extract identifiers. Response includes openInHarness link to the updated resource when applicable.

harness_deleteA

Delete a Harness resource. You can pass a Harness URL to auto-extract identifiers. This is destructive and cannot be undone.

harness_executeA

Execute an action on a Harness resource: run/retry/interrupt pipelines, kill/restore FME feature flags, test connectors, sync GitOps apps, run chaos experiments. You can pass a Harness URL to auto-extract identifiers.

harness_diagnoseA

Diagnose a Harness resource — analyze failures, test connectivity, check health, or troubleshoot GitOps sync issues. Defaults to pipeline execution diagnosis. Accepts a Harness URL to auto-detect the resource type.

harness_searchA

Search across multiple Harness resource types. Returns results ranked by relevance. Accepts a Harness URL for scope.

harness_describeA

Describe available Harness resource types, their supported operations, and fields. No API call — returns local metadata only. Use this to discover what resource_types you can use with other harness_ tools.

harness_statusA

Get a live project health overview: recent failed executions, currently running executions, and recent deployment activity. You can pass a Harness URL to auto-extract org and project. Ideal first question: 'what's happening in my project right now?'

harness_schemaA

Fetch Harness YAML schema for a resource type. Returns the JSON Schema definition so you know the exact body structure for harness_create/harness_update. Use without path for a summary of fields and available sections. Use with path to drill into a specific section (e.g. path='scheduled_trigger' for cron trigger spec). Available schemas: pipeline, template, trigger.

Prompts

Interactive templates invoked by user choice

NameDescription
debug-pipeline-failureAnalyze a failed pipeline execution and suggest fixes. Accepts an execution ID, pipeline ID, or Harness URL.
create-pipelineGenerate a new Harness pipeline YAML from requirements
optimize-costsAnalyze cloud cost data and recommend optimizations for a Harness project
security-reviewReview security issues across Harness resources and suggest remediations
onboard-serviceWalk through onboarding a new service into Harness with environments and a deployment pipeline
dora-metrics-reviewReview DORA metrics (deployment frequency, change failure rate, MTTR, lead time) and suggest improvements
setup-gitops-applicationGuide through onboarding a GitOps application — verify agent, cluster, repo, and create the application
chaos-resilience-testDesign and run a chaos experiment to test service resilience
feature-flag-rolloutPlan and execute a progressive FME feature flag rollout across environments
migrate-pipeline-to-templateAnalyze an existing pipeline and extract reusable stage/step templates from it
delegate-health-checkCheck delegate connectivity, health, and token status with troubleshooting guidance
developer-portal-scorecardReview IDP scorecards for services and identify gaps to improve developer experience
cloud-cost-breakdownDeep-dive into cloud costs by service, environment, or cluster with trend analysis
commitment-utilization-reviewAnalyze reserved instance and savings plan utilization to find waste and optimize commitments
cost-anomaly-investigationInvestigate cost anomalies — determine root cause, impacted resources, and remediation
rightsizing-recommendationsReview and prioritize rightsizing recommendations, optionally create Jira or ServiceNow tickets
vulnerability-triageTriage security vulnerabilities across pipelines and artifacts, prioritize by severity and exploitability
sbom-compliance-checkAudit SBOM and compliance posture for artifacts — license risks, policy violations, component vulnerabilities
supply-chain-auditEnd-to-end software supply chain security audit — provenance, chain of custody, policy compliance
security-exemption-reviewReview pending security exemptions and make batch approval or rejection decisions
access-control-auditAudit user permissions, over-privileged accounts, and role assignments to enforce least-privilege
code-reviewReview a Harness Code pull request — analyze diff, commits, checks, and comments to provide structured feedback
pr-summaryAuto-generate a pull request title and description from the commit history and diff of a branch
branch-cleanupAnalyze branches in a repository and recommend stale or merged branches to delete
pending-approvalsFind pipeline executions waiting for approval and present them for action
build-deploy-appEnd-to-end workflow: scan a repo, generate CI/CD pipelines in Harness, build a Docker image, generate K8s manifests, and deploy

Resources

Contextual data attached and managed by the client

NameDescription
execution-summaryRecent pipeline execution summaries (last 10).
pipeline schemaHarness JSON Schema definitions. Valid schema names: pipeline, template, trigger. Use these to understand the required body format for harness_create.
template schemaHarness JSON Schema definitions. Valid schema names: pipeline, template, trigger. Use these to understand the required body format for harness_create.
trigger schemaHarness JSON Schema definitions. Valid schema names: pipeline, template, trigger. Use these to understand the required body format for harness_create.

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/thisrohangupta/harness-mcp-v2'

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