
Harness
io.github.asklokeshPublished by GitHub account asklokeshv0.1.0Updated Oct 24, 2026
MCP server for Harness API integration
Overview
Local MCP server that connects an assistant to the Harness API for continuous delivery and cloud cost management.
- What you can do
- Access Harness platform APIs through a broad set of generated tools
- Work with continuous delivery and cloud cost management resources
- Authenticate against Harness using the configured API key
- Rely on built-in rate limiting, retry logic and async calls
- When to use it
- Useful when you want an assistant to query or act on Harness CI/CD and cloud cost data from your own machine, rather than through the Harness web UI.
- Requirements
- Runs locally as a Python package (pip install harness-mcp-server, or uvx). Requires a Harness API key in HARNESS_API_KEY and optionally a custom endpoint in HARNESS_API_URL. Network access to the Harness API is needed.
Installation
In SourceWeft
- Open Harness in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Harness MCP Server
Harness Mcp Server
[GitHub stars] [GitHub forks] [GitHub watchers]
A Model Context Protocol (MCP) server for integrating Harness with GenAI applications.
Overview
Continuous delivery and cloud cost management
Features
- Comprehensive Harness API coverage
- Multiple authentication methods
- Enterprise-ready with rate limiting
- Full error handling and retry logic
- Async support for better performance
Installation
Or install from source:
Configuration
Create a .env file or set environment variables according to Harness API requirements.
Quick Start
License
MIT License - see LICENSE file for details
Source: README.md at commit e302f12
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.