Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Harness Infrastructure Management (BYOK) — connector documentation

  • MCP endpoint: https://byok-harness-iacm.connectorbay.com/mcp
  • REST API: POST https://byok-harness-iacm.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-harness-iacm.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Harness Infrastructure Management Harness personal access token or service account token, sent in the X-Upstream-Key header and the Harness account ID (the string after /account/ in your Harness URL) in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-harness-iacm.connectorbay.com/health · Tool schemas: https://byok-harness-iacm.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-harness-iacm · agent@connectorbay.com

What Harness Infrastructure Management (BYOK) is for

Harness Infrastructure Management (BYOK) lets an AI assistant read your own Harness Infrastructure Management data through the Harness Infrastructure Management API with a key you supply (Harness personal access token or service account token). Read-only: 12 tools (list_workspaces, get_workspace, list_workspace_modules, list_workspace_pipelines, get_workspace_drift_config, list_executions, get_execution, list_activities, get_workspace_metrics, list_workspace_costs, get_workspace_ccm_cost_summary, list_workspace_insights). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to app.harness.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Harness Infrastructure Management. Harness Infrastructure Management and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Harness IaCM workspaces does my project have and are any failed?"
  • "Which repository and OpenTofu version does Harness workspace network_prod use?"
  • "Which modules does Harness workspace network_prod use?"
  • "Which pipelines run Harness workspace network_prod?"
  • "Is drift detection enabled for Harness workspace network_prod?"
  • "What were the latest IaCM executions in my Harness project?"

What it does

  • list_workspaces: List the IaCM workspaces of a project with name, status (active, failed, provisioning ...), description and timestamps. Filter by name, tag or status.
  • get_workspace: Get one IaCM workspace: provisioner and version, source repository branch and path, cost estimation and budget, lock state, template, tags and variable set names. Variable values and state are not returned.
  • list_workspace_modules: List the Terraform or OpenTofu modules a workspace uses with source, version and invocation count.
  • list_workspace_pipelines: List the pipelines linked to a workspace.
  • get_workspace_drift_config: Get a workspace's drift detection schedule: whether it is on, how often it runs and the pipeline used.
  • list_executions: List IaCM pipeline executions of a project with workspace, pipeline, status (none, success, failure) and time. Filter by workspace or time.
  • get_execution: Get one IaCM execution stage: workspace, pipeline, status and creation time.
  • list_activities: List IaCM activity records (plan, apply, destroy, drift ...) with status, pipeline, provisioner, branch and monthly cost. Commit messages are left out.
  • get_workspace_metrics: Get how many workspaces of a project are in each status (active, failed, provisioning ...), optionally for a time window.
  • list_workspace_costs: List estimated cost per workspace for a project with currency and date.
  • get_workspace_ccm_cost_summary: Get a workspace's cloud cost summary: monthly cost, previous month, savings found, open recommendations and resource count.
  • list_workspace_insights: List cost and drift insights for a workspace with type, state, resource type, monthly saving and remediation status.

BYOK key

You bring your own Harness Infrastructure Management Harness personal access token or service account token (https://developer.harness.io/docs/platform/automation/api/add-and-manage-api-keys/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to app.harness.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Only accounts served from app.harness.io are supported; clusters on other Harness hosts are not. Needs the IaCM module on the Harness account.

Data sources

Live from the Harness Infrastructure Management API (app.harness.io) with a BYOK key; documentation: https://apidocs.harness.io/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Harness Infrastructure Management. Harness Infrastructure Management and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Harness Infrastructure Management account.

Built for: Worldwide. Languages: English.