// Generate DORA metrics and engineering performance reports using Harness SEI via MCP. Track deployment frequency, lead time, change failure rate, and MTTR. Use when user says "DORA metrics", "deployment frequency", "lead time", "engineering metrics", or asks about team performance.
| name | dora-metrics |
| description | Generate DORA metrics and engineering performance reports using Harness SEI via MCP. Track deployment frequency, lead time, change failure rate, and MTTR. Use when user says "DORA metrics", "deployment frequency", "lead time", "engineering metrics", or asks about team performance. |
| metadata | {"author":"Harness","version":"2.0.0","mcp-server":"harness-mcp-v2"} |
| license | Apache-2.0 |
| compatibility | Requires Harness MCP v2 server (harness-mcp-v2) |
Generate DORA metrics reports using Harness Software Engineering Insights (SEI) via MCP.
Deployment Frequency:
Call MCP tool: harness_get
Parameters:
resource_type: "sei_deployment_frequency"
Lead Time for Changes:
Call MCP tool: harness_get
Parameters:
resource_type: "sei_lead_time"
Change Failure Rate:
Call MCP tool: harness_get
Parameters:
resource_type: "sei_change_failure_rate"
Mean Time to Recovery:
Call MCP tool: harness_get
Parameters:
resource_type: "sei_mttr"
For detailed deployment frequency:
Call MCP tool: harness_get
Parameters:
resource_type: "sei_deployment_frequency_drilldown"
For detailed change failure rate:
Call MCP tool: harness_get
Parameters:
resource_type: "sei_change_failure_rate_drilldown"
Call MCP tool: harness_list
Parameters:
resource_type: "sei_team"
Call MCP tool: harness_list
Parameters:
resource_type: "sei_team_developer"
Call MCP tool: harness_get
Parameters:
resource_type: "sei_ai_adoption"
Also: sei_ai_adoption_breakdown, sei_ai_impact, sei_ai_usage, sei_ai_usage_breakdown
| Metric | Elite | High | Medium | Low |
|---|---|---|---|---|
| Deployment Frequency | Multiple/day | Weekly-Monthly | Monthly-6mo | 6mo+ |
| Lead Time | < 1 hour | 1 day-1 week | 1-6 months | 6mo+ |
| Change Failure Rate | < 5% | 5-10% | 10-15% | > 15% |
| MTTR | < 1 hour | < 1 day | 1 day-1 week | 1 week+ |
## DORA Metrics Report
**Period:** <date range>
**Team:** <team or org>
### Performance Summary
| Metric | Value | Rating | Trend |
|--------|-------|--------|-------|
| Deployment Frequency | X/week | High | Improving |
| Lead Time | X hours | Elite | Stable |
| Change Failure Rate | X% | Medium | Needs attention |
| MTTR | X hours | High | Improving |
### Overall Rating: <Elite/High/Medium/Low>
### Recommendations
1. CFR at X% - invest in test automation and code review
2. Lead time trending up - look at PR review bottlenecks
3. Consider feature flags to decouple deploy from release
| Resource Type | Operations | Description |
|---|---|---|
sei_deployment_frequency | get | Deploy frequency metric |
sei_deployment_frequency_drilldown | get | Detailed frequency data |
sei_lead_time | get | Lead time for changes |
sei_change_failure_rate | get | Change failure rate |
sei_change_failure_rate_drilldown | get | Detailed CFR data |
sei_mttr | get | Mean time to recovery |
sei_team | list, get | Team definitions |
sei_team_developer | list | Team members |
sei_metric | list, get | Generic metrics |
sei_org_tree | get | Organization structure |
sei_business_alignment | get | Business alignment |
sei_ai_adoption | get | AI adoption metrics |
Create and update Harness AI agent instances for automated code and infrastructure tasks. Supports multi-stage execution, MCP server integration, LLM connector configuration, runtime inputs, repository cloning, and task/rules-based instruction. Use when asked to create an agent, update agent spec, modify agent configuration, automate tasks, perform agentic workflows, build autonomous systems, or work with AI agents. Trigger phrases: create agent, update agent, modify agent spec, AI agent, autonomous agent, agentic pipeline, automation task, automate workflow, Harness agent, code coverage agent, review agent, agentic task.
Execute and monitor Harness pipeline runs via MCP tools. Find pipelines, provide runtime inputs, trigger executions, monitor progress, handle approvals, retry failures, and abort running or stuck executions. Use when asked to run a pipeline, execute a deployment, trigger a build, start a pipeline, deploy a service, check execution status, approve a pipeline, or abort/stop/interrupt executions. Trigger phrases: run pipeline, execute pipeline, deploy, start build, trigger pipeline, check execution, approve deployment, retry failed pipeline, abort execution, stop pipeline, interrupt execution, kill stuck pipeline.
Create OPA governance policies for Harness via MCP. Define policies that enforce compliance rules on pipelines, services, environments, feature flags, artifacts, code repositories, templates, SBOM, security tests, Terraform, GitOps, connectors, secrets, and more. Use when asked to create, write, fix, or explain an OPA policy, Rego rule, deny rule, governance policy, compliance rule, or policy-as-code for any Harness entity. Trigger phrases: create policy, OPA policy, governance policy, compliance rule, rego policy, deny rule, enforce policy, security policy, supply chain governance.
Analyze cloud costs, find optimization opportunities, and track anomalies using Harness CCM via MCP. Use when user says "cloud costs", "analyze costs", "cost optimization", "reduce spending", "cost report", or asks about cloud bills.
Manage Harness Feature Flags via MCP. Create boolean or multivariate flags, list flags by project or workspace, get flag details with environment state, toggle flags on/off per environment, and delete flags. Use when asked to create a feature flag, toggle a flag, list flags, check flag status, enable or disable a feature, or manage feature rollouts. Trigger phrases: feature flag, toggle flag, create flag, enable feature, disable feature, flag status, feature rollout, kill switch.