Harness
by Harness
Run pipelines, toggle feature flags, trace failed deployments and read cloud costs from your AI assistant. 11 dispatcher tools reaching 228 Harness resource types, OAuth sign-in, and a risk-tiered confirmation gate.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Harness via MCP
https://mcp.harness.io/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Harness Tools & Capabilities (11)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Can the Harness MCP server read my secret values?
No. Harness states in its server repository that secret values are never included in any response, and the secret resource type supports only list and get, returning metadata such as name, type and scope. There is no create, update or delete for secrets through this connector, so an assistant can inventory your secrets but never read or change one.
Can an AI assistant deploy to production through Harness MCP?
Yes, if your own Harness permissions allow it. Running a pipeline is a harness_execute action, and a Harness pipeline can target any environment it is configured for, including production. Harness rates a pipeline run as high_write, so the connector asks you to confirm before it triggers, and your account's approval stages and RBAC still apply to the execution itself.
Why does the Harness connector only ask for organization, profile and email?
Because Harness does not express its permissions as OAuth scopes. Its authorization server at id.harness.io advertises exactly three scopes, all of them identity claims rather than capabilities. The real boundary is Harness RBAC, so the connector reaches whatever your roles and resource groups already permit, and the consent screen has no read-only option to pick.
How many things can the Harness MCP server actually change?
Eleven tools reach 228 resource types, by Harness's own count. The write verbs take a resource type as an argument rather than being scoped to one entity, so harness_create, harness_update, harness_delete and harness_execute apply across pipelines, connectors, environments, services, feature flags, chaos experiments and more. Read Harness's resource tables to see which verbs each type supports.
Does Claude ask me to confirm before Harness deletes something?
Not reliably, and this is the important caveat. Harness uses MCP elicitation for medium-risk operations and above, but its own client table lists Claude Desktop as not yet supporting elicitation. Where a client cannot show the prompt, Harness blocks the operation rather than running it, unless the caller passes confirm true explicitly.
Can I make the Harness MCP connector read-only?
Not on the hosted endpoint. Harness ships a HARNESS_READ_ONLY environment variable that blocks create, update, delete and execute, but environment variables only apply to the server you run yourself. On the managed endpoint at mcp.harness.io, restriction comes from Harness RBAC on the identity you sign in with, so grant a narrow role instead.
Do I need Harness Support to enable the hosted MCP endpoint?
Yes. Harness states the hosted MCP service must be enabled and configured per account by Harness Support before the endpoint can be used. The hosted service also authenticates with Harness Platform OAuth rather than an API key, and client configuration cannot change which Harness environment the managed endpoint routes to.
Sources
- Harness MCP server repository,
README.md— https://github.com/harness/mcp-server (fetched 2026-08-19, raw file). Verified as Harness's own repository: ownerharness, described as the official repo, MIT licensed, last pushed 2026-08-19 · retrieved 2026-08-19 - Harness MCP server prompt sources — https://github.com/harness/mcp-server (contents of
src/prompts, 35 files, listed 2026-08-19) · retrieved 2026-08-19 - Harness RBAC overview — https://developer.harness.io/docs/platform/role-based-access-control/rbac-in-harness (fetched 2026-08-19) · retrieved 2026-08-19
- Single Sign-On for Harness MCP — https://developer.harness.io/docs/platform/authentication/single-sign-on-for-harness-mcp (fetched 2026-08-19) · retrieved 2026-08-19
- Harness Developer Hub
robots.txt— https://developer.harness.io/robots.txt (fetched 2026-08-19).Allow: /with only/docs/first-gen/disallowed; noContent-Signalline · retrieved 2026-08-19 - Harness Developer Hub
llms.txt— https://developer.harness.io/llms.txt (fetched 2026-08-19) · retrieved 2026-08-19 - Harness hosted MCP documentation page — https://developer.harness.io/docs/platform/harness-ai/harness-mcp-server/ (attempted 2026-08-19). Client-rendered; the fetched HTML carries no article text, so nothing on this page is cited here · retrieved 2026-08-19
- Live RFC 9728 discovery —
https://mcp.harness.io/.well-known/oauth-protected-resourceand/.well-known/oauth-protected-resource/mcp, both HTTP 200 (2026-08-19). The two bodies differ only inresource, declaring the host and the/mcppath respectively; both namehttps://id.harness.ioas the authorization server · retrieved 2026-08-19 - Live RFC 8414 metadata —
https://id.harness.io/.well-known/oauth-authorization-server, HTTP 200 (2026-08-19).scopes_supportedpresent withorganization,profile,email;code_challenge_methods_supportedS256; aregistration_endpointis published · retrieved 2026-08-19 - Live unauthenticated request —
https://mcp.harness.io/mcpreturned HTTP 401 with nowww-authenticateheader (2026-08-19) · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/b98c06f8-3945-46ff-a81d-14233c0bc9a6 (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Developer Tools
- Developer
- Harness
- Tools
- 11
- Domain
- mcp.harness.io
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.