Harness MCP Server
Connect AI agents to Harness for CI/CD, code repositories, pull requests, services, environments, and feature flags.
- Category
- Developer Tools
- Primary Subcategory
- CI/CD & Internal Developer Platforms
View in the Claude registryIntegration details
Description
The Harness MCP Server gives MCP-compatible clients access to Harness platform workflows through consolidated tools, resources, and prompts. It supports local stdio usage and can be bundled as a Node-based MCPB extension.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- CI/CD & Internal Developer Platforms
- Secondary Subcategories
- None listed
- Brand
- Harness
- Access
- Unknown
- First tracked
- 2026-05-07
- Tool count
- 0
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Get alerts for Harness MCP Server
Get updates when Harness MCP Server’s Discoverability Score or category rank changes.
Claude Discoverability Score
Harness MCP Server isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures
Remote Connectors Claude can surface from the Connector picker.
0 tools agents can invoke
No tools are exposed by this Claude Connector in the latest snapshot.
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.