# Harness MCP Server: Governed AI Access

Harness's MCP server includes 33 different actions available to any connected model or AI agent. When registered with Barndoor, you can ensure centralized governance, visibility, and control across every AI agent your team uses.

**Tools** **33**  
**Capabilities** **[Create](/content/integration-capability/create/index.html), [Read](/content/integration-capability/read/index.html), [Update](/content/integration-capability/update/index.html)**  
**Category** **[DevOps & Infrastructure](/content/integration-category/devops-infrastructure/index.html)**  
**Type** **Barndoor Hosted**

## What can AI agents do with the Harness MCP server?

### Tools Available
- **List Pipelines**  
  read  
  Lists pipelines in a Harness project.
- **Get Pipeline**  
  read  
  Retrieves details of a specific pipeline.
- **List Executions**  
  read  
  Lists pipeline executions with filtering.
- **Create Pull Request**  
  create  
  Creates a new pull request in Harness Code.
- **Get CCM Overview**  
  read  
  Retrieves Cloud Cost Management overview.
- **Move Environment Configs**  
  update  
  Moves environment configurations between scopes.

[See full list →](https://docs.barndoor.ai/mcp-servers/harness)

## Use cases for Harness

- **Pipeline Management**  
  "View pipeline configurations and stages", "Track execution history and status", "Inspect pipeline logs and results"
- **Pull Request Management**  
  "Manage code repositories and branches", "Create and review pull requests", "Track PR status and checks"
- **Infrastructure Management**  
  "List and configure services and environments", "Manage infrastructure definitions", "Move configurations across scopes"
- **Cloud Cost Analysis**  
  "Monitor cloud cost overview and trends", "Analyze cost categories and allocations", "Track spending across cost perspectives"

## What are the risks of using the Harness MCP without an AI gateway?
- **Uncontrolled reads** — AI agents can pull data out of Harness with no visibility into what was accessed.
- **Ungoverned writes** — agents can create or modify records in Harness with no approval step.
- **Destructive actions** — agents can delete or overwrite Harness data with no approval gate or audit trail.

## Why connect Harness with the Barndoor AI gateway?
Barndoor MCP Governance is the gateway between your AI agents and the tools they use.

| At a glance | Available? |
| --- | --- |
| Fine-grained access controls policies per agent, team, role, user, MCP server and tool call | Yes |
| Approval required before write/destructive actions | Yes (configurable per role) |
| Full audit log (reads and writes) | Yes |
| Sensitive data detection before it reaches a model or agent | Yes |
| Instant access revocation | Yes |
| SOC 2 Type II compliant | Yes |

- **Centralized MCP management** — One place to manage and control every MCP server across the organization so your team has an approved catalog of MCP servers that employees and AI agents connect through.
- **Universal connection** — One universal URL works across every AI provider your team uses.
- **Fine-grained access controls** — Set access policies for how AI is connecting with Harness based on human identities, agent profiles, tool-access, context, and data fields.
- **Protect sensitive data** — Keeps sensitive data from reaching a model or AI agent with PII detection, masking, tokenization, redaction, and more.
- **Observability** — Real-time reporting and dashboards that give you visibility into what AI is doing with Harness, how policies are being enforced, and who (human or agent) is doing what.
- **Enterprise-grade security** — Stay compliant with audit trails and logging.

## Works with every AI client

\
\
ChatGPT](/content/integrations/chatgpt/index.html) \
\
Claude Code](/content/integrations/claude-code/index.html) \
\
Claude Desktop](/content/integrations/claude-desktop/index.html) \
\
Codex](/content/integrations/codex/index.html) \
\
CrewAI](/content/integrations/crewai/index.html) \
\
Cursor](/content/integrations/cursor/index.html) \
\
Gemini CLI](/content/integrations/gemini-cli/index.html) \
\
GitHub Copilot](/content/integrations/github-copilot/index.html) \
\
Google ADK](/content/integrations/google-adk/index.html) \
\
LangChain](/content/integrations/langchain/index.html) \
\
Microsoft Copilot](/content/integrations/microsoft-copilot/index.html) \
\
OpenClaw](/content/integrations/openclaw/index.html)

## Getting started with Harness in Barndoor
1. Connect the Harness MCP server once  
2. Define your policies  
3. Go live across every AI client

[See the full setup guide →](https://docs.barndoor.ai/mcp-servers/harness#setup-instructions)

## Frequently asked questions

**What is MCP?**  
MCP (Model Context Protocol) is the open standard that lets AI models and agents connect to external tools and data sources through a common interface, instead of a custom integration for every tool. Harness is an MCP server that exposes a defined set of tools an AI agent can call. Barndoor sits at that connection point, applying access policies and audit logging to every tool call regardless of which AI client is making it.

**Is Barndoor secure?**  
Yes. Barndoor is SOC 2 Type II compliant. Barndoor enforces fine-grained access control, requires approval before destructive actions, protects sensitive data with data loss prevention, and logs every action for audit.

**How are Harness schema changes handled?**  
Barndoor tracks tool and schema changes on Harness. New or changed tools inherit deny-by-default access until an admin reviews and approves them, keeping runtime enforcement current without manual reconfiguration. Every schema change is captured in the audit trail alongside who approved it.

**Do you integrate with my identity provider?**  
Barndoor authenticates admins and policy managers through your OIDC or SAML 2.0 identity provider. Signing into Claude, Cursor, or ChatGPT still happens directly with those providers. Barndoor's integration point is the Harness connection where access policies apply to what an agent can do once it's connected.

**Do users have to enter tokens manually?**  
No. Barndoor brokers the OAuth connection to Harness centrally, so users and agents never handle or store a standing token themselves. Access is granted and revoked through policy instead of shared credentials.

**How does Barndoor integrate with AI agent identities?**  
Barndoor gives each AI agent its own governed identity called an AgentProfile, separate from the human who configured or uses it. AgentProfile lets policies and audit logs attribute a given action to the specific agent, not a shared service token, so you can set different access rules per agent and revoke one agent's access without affecting others.

**Can I deploy custom-built MCP servers?**  
Yes. Barndoor supports customer-built MCPs, so internal tools and systems your team builds get the same policy enforcement and audit trail as Barndoor MCPs and official MCPs.

**Can I set and audit tool-level access across teams?**  
Yes. Barndoor's access control is fine-grained, down to the agent, team, group, user, MCP server, the specific tool call, and the data type involved. Every call is logged with a timestamp, the user or agent calling it, the client it came from, and the result of the policy applied, so you can see exactly who or what did what, when, and whether it was allowed, across any team or role.

**How can I get started with Harness and Barndoor?**  
Connect Harness once, define your access policies, and go live across every AI client your team uses. Setup takes three steps: connect the server, define policies by role or agent, and roll out to Claude, Cursor, ChatGPT, and any other MCP-compatible client.