manage-delegates
Monitor and manage Harness Delegates via MCP. List delegates and check health status, manage delegate registration tokens (create, revoke, delete), and find which delegates are associated with a token. Use when asked about delegate status, delegate health, delegate connectivity, delegate tokens, or troubleshooting delegate issues. Trigger phrases: delegate status, delegate health, list delegates, delegate token, delegate connectivity, delegate troubleshooting, delegate down.
- License 许可
- Apache-2.0
- 最近更新
- 2026-06-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- manage-delegates
- license
- Apache-2.0
- metadata
- { "author": "Harness", "version": "1.0.0", "mcp-server": "harness-mcp-v2" }
- description
- Monitor and manage Harness Delegates via MCP. List delegates and check health status, manage delegate registration tokens (create, revoke, delete), and find which delegates are associated with a token. Use when asked about delegate status, delegate health, delegate connectivity, delegate tokens, or troubleshooting delegate issues. Trigger phrases: delegate status, delegate health, list delegates, delegate token, delegate connectivity, delegate troubleshooting, delegate down.
- compatibility
- Requires Harness MCP v2 server (harness-mcp-v2)
03 SKILL.md 正文
Manage Delegates
Monitor delegate health and manage registration tokens via MCP.
Instructions
Step 1: List Delegates
List all delegates in the account to check health and connectivity:
Call MCP tool: harness_list
Parameters:
resource_type: "delegate"
This returns all delegates with their status, version, connectivity, and last heartbeat. Delegates are account-scoped -- no org/project needed.
Step 2: List Delegate Tokens
Call MCP tool: harness_list
Parameters:
resource_type: "delegate_token"
org_id: "<organization>"
project_id: "<project>"
Filter by name or status:
Call MCP tool: harness_list
Parameters:
resource_type: "delegate_token"
name: "prod-token"
status: "ACTIVE"
Step 3: Get Token Details
Call MCP tool: harness_get
Parameters:
resource_type: "delegate_token"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Step 4: Create a Token
Call MCP tool: harness_create
Parameters:
resource_type: "delegate_token"
org_id: "<organization>"
project_id: "<project>"
body:
name: "prod-delegate-token"
Step 5: Find Delegates for a Token
Call MCP tool: harness_execute
Parameters:
resource_type: "delegate_token"
action: "get_delegates"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Step 6: Revoke a Token
Call MCP tool: harness_execute
Parameters:
resource_type: "delegate_token"
action: "revoke"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Step 7: Delete a Token
Call MCP tool: harness_delete
Parameters:
resource_type: "delegate_token"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Resource Types
| Resource Type | Scope | Operations | Description |
|---|---|---|---|
delegate |
Account | list | List delegates with health status |
delegate_token |
Project | list, get, create, delete + revoke, get_delegates actions | Manage registration tokens |
Examples
- "Are all delegates healthy?" -- List delegates, check status and last heartbeat
- "Create a new delegate token for the staging project" -- Create token with project scope
- "Which delegates are using the prod-token?" -- Execute get_delegates action on the token
- "Revoke the old registration token" -- Execute revoke action
- "Show me all active delegate tokens" -- List tokens filtered by status ACTIVE
Performance Notes
- When diagnosing delegate issues, check both the delegate list (for health/heartbeat) and the token status (for auth). A delegate showing as disconnected may have a revoked token.
- Always verify delegate connectivity before troubleshooting pipeline failures -- many execution errors stem from unavailable delegates.
Troubleshooting
Delegate Shows Disconnected
- Check the delegate's last heartbeat timestamp -- if stale, the delegate process may be down
- Verify the delegate token is ACTIVE (not REVOKED)
- Check network connectivity between the delegate host and Harness SaaS
Pipeline Fails with "No Delegates Available"
- List delegates to confirm at least one is connected and healthy
- Check if the pipeline uses a delegate selector that doesn't match any active delegate
- Verify the delegate has the required tools installed (kubectl, helm, docker, etc.)
Token Issues
- Tokens are project-scoped -- a token created in project A cannot register delegates for project B
- Revoking a token disconnects all delegates registered with it
- Deleted tokens cannot be recovered -- create a new one and re-register delegates
04 同仓库更多 Skills
verify-sign
Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.
template-usage
Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).
sign-artifact
Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build/push; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.
sei-analytics
Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.
security-report
Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says "security report", "vulnerabilities", "SBOM", "security scan", "compliance check", or asks about application security.
scorecard-review
Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says "scorecard", "service maturity", "production readiness", "compliance score", or asks about service health scores.