Harness Code (BYOK) — connector documentation
- MCP endpoint:
https://byok-harness-code.connectorbay.com/mcp - REST API:
POST https://byok-harness-code.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-harness-code.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Harness Code Harness personal access token or service account token, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-harness-code.connectorbay.com/health· Tool schemas:https://byok-harness-code.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-harness-code · agent@connectorbay.com
What Harness Code (BYOK) is for
Harness Code (BYOK) lets an AI assistant read your own Harness Code data through the Harness Code API with a key you supply (Harness personal access token or service account token). Read-only: 10 tools (list_repositories, get_repository, list_branches, list_tags, get_repository_summary, list_repository_rules, list_space_rules, get_repository_general_settings, get_repository_security_settings, get_usage_metrics). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to app.harness.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Harness Code. Harness Code and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which repositories do I have in Harness Code?"
- "How many open pull requests does Harness Code repository web-app have?"
- "Which branches does Harness Code repository web-app have?"
- "Which release tags does Harness Code repository web-app have?"
- "How many branches and open pull requests does Harness Code repository web-app have?"
- "What protection rules apply to Harness Code repository web-app?"
What it does
list_repositories: List Harness Code repositories of an account, organization or project with language, size, pull request counts and last push time.get_repository: Get one Harness Code repository: description, default branch, language, size, visibility, pull request counts and timestamps.list_branches: List a repository's branches with the commit SHA, default flag, and optionally how far each is ahead of or behind the default branch.list_tags: List a repository's tags with the target SHA, whether the tag is annotated, its title and signature verification result.get_repository_summary: Get a repository's branch count, tag count, commit count on the default branch and pull request totals (open, merged, closed).list_repository_rules: List a repository's protection rules (branch, tag and push rules) with state, branch pattern and the rule definition such as required approvals. Creator names are left out.list_space_rules: List protection rules defined at account, organization or project level (they apply to many repositories) with state, type and pattern.get_repository_general_settings: Get a repository's general settings: auto-merge, Git LFS and file size limit.get_repository_security_settings: Get a repository's security settings: secret scanning, vulnerability scanning mode (disabled, detect, block, strict) and committer identity matching.get_usage_metrics: Get Harness Code usage for an account, organization or project: pushes, bandwidth, storage and storage limit status.
BYOK key
You bring your own Harness Code Harness personal access token or service account token (https://developer.harness.io/docs/platform/automation/api/add-and-manage-api-keys/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to app.harness.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Notices
Only accounts served from app.harness.io are supported; clusters on other Harness hosts are not.
Data sources
- https://apidocs.harness.io/ (the API this connector calls, with a BYOK key)
Live from the Harness Code API (app.harness.io) with a BYOK key; documentation: https://apidocs.harness.io/. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Harness Code. Harness Code and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Harness Code account.
Built for: Worldwide. Languages: English.