FerentinFerentin
Harness logo

Harness

Beta

Ferentin connects to the Harness-managed MCP endpoint using Harness Platform OAuth through Harness ID. Each user authorizes individually, so every tool call runs under that user's Harness RBAC and licensed modules. The hosted endpoint has no API-key path, so there is no tenant-level agent mode.

  • Harness
  • CI/CD
  • DevOps
Configure Harness
Authentication
OAuth 2.0
Hosting
Vendor-hosted endpoint
Required scopes
4

How it works

Every agent request passes through Ferentin policy before it reaches Harness.

  1. AI agentAsks for something
  2. Ferentin policies
    • Per user OAuth
    • PKCE
    • Harness rbac
    • Module license gating
  3. Harness MCP serverAuthorized connection
  4. Governed resultMasked, logged, returned

What you can do with Harness

  • Pipeline management
  • Gitops
  • Cloud cost management
  • Security testing
  • Chaos engineering
  • Internal developer portal

Permissions requested

The OAuth 2.0 scopes Harness asks you to approve when you connect.

ScopeAccess
openidNot rated
profileNot rated
emailNot rated
offline_accessNot rated

Before you connect

  • The hosted endpoint does NOT accept a Harness API key (PAT). Harness Platform OAuth is the only supported method — HARNESS_API_KEY applies to the self-hosted server only.
  • Auth is per-user: tools run as the signed-in Harness user and honour that user's RBAC.
  • Available tools depend on which Harness modules your account licenses; unlicensed modules simply do not appear.
  • Harness ID exposes a DCR registration endpoint, but it requires an initial access token, so Ferentin uses the documented pre-arranged client id instead.
1 more technical note
  • Dedicated SaaS clusters and non-default regions may use a different MCP base URL — confirm with Harness Support before installing.

About Harness

Harness is an AI-native software delivery platform spanning CI/CD, GitOps, feature management, cloud cost management, security testing orchestration, chaos engineering, an internal developer portal, and software supply chain assurance.

WebsiteDeveloper docs

Frequently asked about Harness

What can AI agents do with Harness through Ferentin?
Through Ferentin, agents can use Harness for pipeline management, gitops, cloud cost management, security testing, chaos engineering and internal developer portal. Every call is checked against your Ferentin policies first.
How is Harness access secured?
Requests through the Harness integration are covered by per user OAuth, PKCE, harness rbac and module license gating. These controls are applied by Ferentin, not by Harness, so they hold across every connected agent.
What permissions does the Harness integration require?
The Harness integration requests 4 OAuth 2.0 scopes: openid; profile; email; offline_access
How do I connect Harness to Ferentin?
Open the Ferentin admin console, add Harness as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
Is the Harness integration generally available?
The Harness integration is currently beta on Ferentin.

Related integrations

3
GitHub logo
GA

GitHub

Development platform for version control, collaboration, and CI/CD workflows.

MCP Servers
View
GitLab logo
GA

GitLab

Manage repositories, merge requests, CI/CD pipelines, and issues across your GitLab DevOps platform from an AI agent.

MCP Servers
View
PagerDuty logo
GA

PagerDuty

Triage incidents, review on-call schedules, and coordinate response so an agent can accelerate outage handling.

MCP Servers
View