PlugWiki
Harness MCP Server logo

Harness MCP Server: run and debug Harness pipelines from your AI assistant

Official · by HarnessRemoteLocal
Gethttps://mcp.harness.io/mcpharness/mcp-serverDocs

Lets your AI assistant check, run and fix Harness pipelines, deployments, feature flags and cloud costs.

This is Harness' own server for its software delivery platform. It lets Claude, Cursor and other assistants list, inspect, create and run things across your Harness account, from pipelines to feature flags and cloud cost data. You can run it on your computer with a Harness API key, or use the hosted version and sign in with your Harness account. The hosted version only works after Harness Support turns on sign-in for your account.

Good for

  • Platform and DevOps engineers who want Claude or Cursor to find out why a pipeline failed
  • Developers who want to run or retry a deployment without leaving their editor
  • Release managers rolling out feature flags and checking DORA metrics
  • FinOps and security teams reviewing cloud costs or vulnerability scans

Works in

6 supported · 8 should work

Tap an app to see how to set it up and any known problems.

Install Harness MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Harness MCP server to Claude Code. Run this command:
    
    claude mcp add harness -e HARNESS_API_KEY=<HARNESS_API_KEY> -- npx -y harness-mcp-v2
    
    Ask me for HARNESS_API_KEY and only put the values in that config, nowhere else.
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

Read-only mode: For the local server, set HARNESS_READ_ONLY to true in its environment settings. It can then only list and read, not create, change, delete or run anything.

The local option needs a Harness API key: in Harness open My Profile, then API Keys, add a key and create a token under it. Your account ID is read from the token, so the key is usually the only setting you need.

The hosted option signs you in with your Harness account instead of a key, using the client ID mcp-client when your app asks for one. The local command is the default here because the hosted option works only on Harness SaaS and only after Harness Support turns on sign-in for your account; until then you get an invalid credentials error.

Built from the package data we hold. Not yet tested by us.

Tools

  • Lists pipelines, services, flags, projects and other Harness items

    Lists any kind of Harness item, such as pipelines, executions, services, environments, feature flags or projects, with filters, search and paging.

    Try: “List the pipelines in the payments project”

    Network · harness_list

  • Shows the details of one pipeline, run, service or other item

    Fetches one Harness item by its ID or a pasted Harness link, for example a pipeline's YAML or a single execution.

    Try: “Show me the YAML for the deploy-api pipeline”

    Network · harness_get

  • Searches across all kinds of Harness items with one query

    Searches many Harness resource types at once with one query and returns matching items, so you do not need to know where something lives.

    Try: “Find anything related to the checkout service”

    Network · harness_search

  • Explains why a pipeline run, connector or delegate is failing

    Looks into a pipeline run, connector, delegate or GitOps app and returns step timings, failure details and health signals so you can see what went wrong.

    Try: “Why did the last run of the payments pipeline fail?”

    Network · harness_diagnose

  • Gives a health summary of a project's recent runs and failure rates

    Returns a quick health view of a project: recent executions, failure rates and links into the Harness UI.

    Try: “How healthy is the checkout project this week?”

    Network · harness_status

  • Runs or retries pipelines, switches feature flags and syncs GitOps apps

    Carries out actions such as running or retrying a pipeline, importing a pipeline from Git, turning a feature flag on or off, or syncing a GitOps app. It asks you to confirm risky actions where your app supports it.

    Try: “Rerun the failed staging deployment”

    Runs code · harness_execute

  • Creates pipelines, services, environments and other Harness items

    Creates a new Harness item, such as a pipeline, trigger, service or environment, including pipelines stored in Git.

    Try: “Create a pipeline that builds and deploys the api service to staging”

    Write · harness_create

  • Changes an existing pipeline, service or other Harness item

    Updates an existing Harness item, for example editing a pipeline's stages or a service's settings.

    Try: “Add a manual approval step before production in the deploy-api pipeline”

    Write · harness_update

  • Deletes a Harness item after you confirm

    Deletes a Harness item such as a pipeline or trigger. It asks for confirmation first and is blocked in apps that cannot show the prompt.

    Try: “Delete the old fx-rates pipeline”

    Delete · harness_delete

  • Used by the assistant behind the scenes

    Lists what kinds of Harness items and actions are available

    Returns the resource types, operations and fields the server knows about, so the assistant can find the right one. It makes no call to Harness.

    Read · harness_describe

  • Looks up the exact format for creating or editing an item

    Fetches the YAML or JSON schema and examples for a resource type, such as a pipeline or connector, so the assistant writes valid definitions.

    Network · harness_schema

Read from the source code

Pros and cons

Good

  • Made and maintained by Harness, open source under MIT.
  • Covers CI/CD, GitOps, feature flags, cloud cost, security testing and more in one server.
  • Eleven general tools keep the assistant's tool list small.
  • Read-only mode with one setting.
  • Asks before deleting or running risky actions in clients that support prompts.
  • Hosted option signs you in with your Harness account, no key to manage.
  • Never returns secret values.

Watch out

  • The hosted server must be switched on for your account by Harness Support.
  • Hosted sign-in is for Harness SaaS only.
  • Low-risk changes run without asking, and Claude Desktop cannot show prompts.
  • Single sign-on accounts need an admin to add an extra address to the identity provider.
  • Desktop apps often fail to find npx until you set full paths.

Permissions

high risk · 5 things to watch

High risk

With a broad key it can change pipelines, run deployments and delete resources across your Harness account. Turn on read-only mode first and use a key that only reaches the projects you need.

What it can do

Watch out for

  • It can run pipelines and deploy

    It can run and retry pipelines, switch feature flags and sync GitOps apps. Use read-only mode or a key limited to the projects you need. github.com

  • Some changes go through without asking

    Low-risk creates and updates run without a prompt, and Claude Desktop cannot show prompts yet. Leave HARNESS_AUTO_APPROVE_RISK at its default of none. github.com

  • A path handling fix is still in progress

    A path traversal report from September led to a hardening change opened in late October. Keep the server on the newest version. github.com

  • Secret values are never returned

    Secrets come back as names and metadata only, so the assistant cannot read their values. developer.harness.io

  • The hosted server acts as you

    After you sign in it uses your Harness user and role permissions. developer.harness.io

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlySet HARNESS_READ_ONLY=true on the local server. Only list and get work; create, update, delete and execute are blocked. Not documented for the hosted endpoint.
Talks toapp.harness.io (or your HARNESS_BASE_URL)
Sign-in and keysLocal: a Harness API key in the client config or environment. Hosted: Harness ID sign-in, no key in the config.

Alternatives

Use this server if your pipelines and deployments run in Harness. If they run in GitHub Actions, GitLab, CircleCI, Buildkite or Argo CD, pick that platform's server instead.

ServerOfficialRunsSign-inGitHub stars
For Harness
HarnessThis pageOfficialHostedLocalAPI key or account111
Other tools for the same job
GitHubFor GitHubOfficialHostedLocalAccount34.1K
GitLabFor GitLabOfficialHostedAccount–
Argo CDCommunity––601
BuildkiteOfficialLocal–56

What people say

Public discussion is thin; GitHub users mostly report specific bugs, and most of those are now closed.

What people like

  • Harness staff reply on GitHub and pointed people asking for a hosted option to the managed endpoint.

Common complaints

  • A security reporter waited about a month for a reply before hardening work started.
  • Some feature flag actions failed and links were malformed on one release.
  • Early users had to reconnect the local server often in Claude Code.

In their words

Questions

Is the Harness MCP server free?

Yes, the server is free and open source under MIT. You still need a Harness account, and on the hosted version the tools you see depend on your Harness licenses.

What is the Harness MCP server URL?

The hosted address is https://mcp.harness.io/mcp for the main Harness SaaS cluster. If you are on a dedicated cluster or another region, confirm the address with Harness Support.

Should I use the hosted server or run it myself?

Use the hosted server if you are on Harness SaaS and want to sign in with your own account instead of handling a key. Run it yourself if Support has not enabled hosted access, you use self-managed Harness, or you want read-only mode.

Why does the hosted server say my credentials are invalid?

Sign-in has not been turned on for your Harness account yet, even if your normal login works. Ask Harness Support to enable it, then connect again.

Is it safe to use?

It can run pipelines and delete resources, so start in read-only mode. It asks before risky actions in Cursor and VS Code, and it never returns secret values.

Can it delete my pipelines?

Yes, if your key allows it. It asks for confirmation first, and in apps that cannot show the prompt, deletes are blocked.

How do I add it to Claude Code?

Use the Claude Code tab in the install box above. Pick the hosted option if your account has it, or the local command with your API key.

Why does Claude Desktop or Cursor say it cannot find npx?

Desktop apps often do not see your terminal's settings. Put the full path to npx in the config and add the folder that holds node to PATH, as the install notes show.

Does it work with self-managed Harness?

Yes, if you run it yourself and point it at your own Harness address. Hosted sign-in is for Harness SaaS only.

Examples

  • Find failed runs across every project

    show failed executions across all projects

    Source
  • Work out why a pipeline failed from its steps and logs

    Why did the last run of the payments pipeline fail?

  • Review DORA metrics for a project

    Show me the DORA metrics for the checkout project this month.

  • Plan a feature flag rollout

    Plan a gradual rollout for the new-checkout flag.

Information

updated Nov 2, 2026

Publisher
Harness (official)
Package
harness-mcp-v2
Registry
npm
Endpoint
https://mcp.harness.io/mcp
Transport
stdio, Streamable HTTP
Version
3.2.38
License
MIT
Last commit
Oct 30, 2026
Open issues
4

DocsGitHubnpmChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 10
  1. GitHub · github.com
  2. Harness Developer Hub · developer.harness.io
  3. Harness Developer Hub · developer.harness.io
  4. Harness Developer Hub · developer.harness.io
  5. GitHub · github.com
  6. GitHub · github.com
  7. GitHub · github.com
  8. GitHub · github.com
  9. GitHub · github.com
  10. GitHub · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.