Bring the full Harness DevOps platform into your IDE with this Kiro Power. Manage CI/CD pipelines, analyze cloud costs, track DORA metrics, review security posture, control feature flags, monitor GitOps deployments, run chaos experiments, and more — all through natural language.
Harness is a modern software delivery platform that unifies CI/CD, cloud cost management, feature flags, chaos engineering, security testing, and developer experience under a single platform. This power connects Kiro to the Harness MCP server, providing access to 150+ tools across the entire Harness ecosystem.
- CI/CD Pipelines — List, inspect, and debug pipeline executions; download logs; manage triggers and input sets
- Cloud Cost Management — View cost overviews, perspectives, recommendations, and anomalies
- Security & Compliance — Review supply chain security, vulnerability remediation, SBOMs, and security test results
- Chaos Engineering — Browse, run, and analyze chaos experiments and probes
- Feature Flags — List and inspect feature flag definitions across workspaces and environments
- DORA Metrics — Track deployment frequency, lead time, change failure rate, and MTTR
- GitOps — Monitor application sync status, clusters, and resource trees
- Internal Developer Portal — Query the service catalog, scorecards, and technical documentation
- Pull Requests — List, inspect, and create pull requests in Harness Code repositories
- Audit Trail — Review user audit events for compliance
- A Harness account with appropriate permissions
- A Harness API key (personal access token) — generate at Account Settings > API Keys
- Docker installed and running
- Open Kiro IDE
- Go to the Powers panel
- Click Add from GitHub
- Enter the repository URL:
https://github.com/rohangupta/harness-kiro-power - The power will be added and the MCP server configuration will be available
After installing the power, add your Harness credentials to ~/.kiro/settings/mcp.json:
{
"mcpServers": {
"harness": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "HARNESS_API_KEY",
"-e", "HARNESS_DEFAULT_ORG_ID",
"-e", "HARNESS_DEFAULT_PROJECT_ID",
"-e", "HARNESS_BASE_URL",
"-e", "HARNESS_TOOLSETS",
"harness/mcp-server", "stdio"
],
"env": {
"HARNESS_API_KEY": "<your-harness-api-key>",
"HARNESS_DEFAULT_ORG_ID": "<your-org-id>",
"HARNESS_DEFAULT_PROJECT_ID": "<your-project-id>",
"HARNESS_BASE_URL": "https://app.harness.io",
"HARNESS_TOOLSETS": "all"
}
}
}
}| Variable | Required | Description |
|---|---|---|
HARNESS_API_KEY |
Yes | Personal access token for authentication |
HARNESS_DEFAULT_ORG_ID |
No | Default organization to scope requests |
HARNESS_DEFAULT_PROJECT_ID |
No | Default project to scope requests |
HARNESS_BASE_URL |
No | API endpoint (default: https://app.harness.io) |
HARNESS_TOOLSETS |
No | Comma-separated toolsets to enable (default: all) |
Investigate a pipeline failure:
"Why did the deploy-production pipeline fail? Show me the logs."
Analyze cloud costs:
"What are our top cloud cost drivers this month? Any anomalies?"
Track DORA metrics:
"Show me the deployment frequency and change failure rate for the backend team."
Review security posture:
"What vulnerabilities exist in our latest Docker image? Show remediation steps."
Manage feature flags:
"List all feature flags in the production environment. What's the status of dark-mode-v2?"
Monitor GitOps deployments:
"Are all GitOps applications in sync? Show me any that are out of sync."
Run chaos experiments:
"List available chaos experiments. What were the results of the last pod-kill run?"
Developer portal:
"Show me the scorecard for the payments service. What's its maturity level?"
| Toolset | Tools | Description |
|---|---|---|
| Pipelines | 9 | Pipeline management, executions, triggers, input sets |
| Pull Requests | 5 | PR listing, inspection, and creation |
| Services | 2 | Service listing and details |
| Environments | 3 | Environment management and config migration |
| Infrastructure | 2 | Infrastructure definitions and config migration |
| Connectors | 3 | Connector catalog, details, and listing |
| Secrets | 2 | Secret listing and details |
| Delegates | 8 | Delegate management and token operations |
| Repositories | 2 | Code repository listing and details |
| Registries | 5 | Artifact registry and artifact management |
| Dashboards | 2 | Dashboard listing and data retrieval |
| Cloud Cost Management | 10 | Cost overviews, perspectives, recommendations, anomalies |
| Chaos Engineering | 9 | Experiment management, probes, and templates |
| Supply Chain Security | 9 | Artifact security, SBOM, chain of custody, OPA policies |
| Security Testing | 4 | Security issues, exemptions management |
| Logs | 1 | Pipeline execution log download |
| Templates | 1 | Pipeline and stage template listing |
| Internal Developer Portal | 8 | Catalog entities, scorecards, workflows, tech docs |
| Audit Trail | 1 | User audit event listing |
| Feature Management | 4 | Feature flag workspaces, environments, and definitions |
| Software Engineering Insights | 7 | DORA metrics, productivity metrics, team analytics |
| GitOps | 8 | Agents, applications, clusters, resource trees |
If you only need a subset of Harness capabilities, set HARNESS_TOOLSETS to load only what you need. This reduces the number of tools and improves performance:
"HARNESS_TOOLSETS": "pipelines,ccm,sei"
Available toolset names: default, pipelines, pull_requests, services, environments, infrastructure, connectors, secrets, delegate_tokens, delegate, repositories, registries, dashboards, ccm, chaos, scs, sto, logs, templates, idp, audit_trail, fme, sei, gitops