Harness MCP Server

The Harness MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Harness APIs, enabling advanced automation and interaction capabilities for developers and tools.

Components

Tools

The server implements several toolsets:

Default Toolset

The default toolset contains essential tools from various services:

Toolset Name: default

get_connector_details: Get details of a specific connector
list_connector_catalogue: List the Harness connector catalogue
list_connectors: List connectors with filtering options
list_pipelines: List pipelines in a repository
get_pipeline: Get details of a specific pipeline
get_execution: Get details of a specific pipeline execution
list_executions: List pipeline executions
fetch_execution_url: Fetch the execution URL for a pipeline execution
list_dashboards: Lists all available Harness dashboards
get_dashboard_data: Retrieves the data from a specific Harness dashboard

Pipelines Toolset

Toolset Name: pipelines

get_pipeline: Get details of a specific pipeline
list_pipelines: List pipelines in a repository
get_execution: Get details of a specific pipeline execution
list_executions: List pipeline executions
fetch_execution_url: Fetch the execution URL for a pipeline execution

Pull Requests Toolset

Toolset Name: pullrequests

get_pull_request: Get details of a specific pull request
list_pull_requests: List pull requests in a repository
get_pull_request_checks: Get status checks for a specific pull request
get_pull_request_activities: Get activities and comments for a specific pull request
create_pull_request: Create a new pull request

Services Toolset

Toolset Name: services

get_service: Get details of a specific service
list_services: List services

Environments Toolset

Toolset Name: environments

get_environment: Get details of a specific environment
list_environments: List environments
move_environment_configs: Move environment YAML from inline to remote

Infrastructure Toolset

Toolset Name: infrastructure

list_infrastructures: List infrastructure definitions
move_infrastructure_configs: Move infrastructure YAML between inline and remote

Connectors Toolset

Toolset Name: connectors

list_connector_catalogue: List the Harness connector catalogue
get_connector_details: Get details of a specific connector
list_connectors: List connectors with filtering options

Repositories Toolset

Toolset Name: repositories

get_repository: Get details of a specific repository
list_repositories: List repositories

Registries Toolset

Toolset Name: registries

get_registry: Get details of a specific registry in Harness artifact registry
list_artifact_files: List files for a specific artifact version in a Harness artifact registry
list_artifact_versions: List artifact versions in a Harness artifact registry
list_artifacts: List artifacts in a Harness artifact registry
list_registries: List registries in Harness artifact registry

Dashboards Toolset

Toolset Name: dashboards

list_dashboards: Lists all available Harness dashboards
get_dashboard_data: Retrieves the data from a specific Harness dashboard

Cloud Cost Management Toolset

Toolset Name: ccm

get_ccm_overview: Retrieves the cost overview for a specific account.
list_ccm_cost_categories: List all cost categories names for a specified account.
list_ccm_cost_categories_detail: List all cost categories details for a specified account.
get_ccm_cost_category: Retrieve a cost category detail by Id for a specified account.
list_ccm_perspectives_detail: List all perspectives for a specified account.
get_ccm_perspective: Retrieves a perspective by Id for a specified account.
get_last_period_cost_ccm_perspective: Retrieves the cost for a specified period and perspective within a given account.
get_last_twelve_months_cost_ccm_perspective: Retrieves a monthly cost breakdown for the past 12 months for a perspective within a specified account.
create_ccm_perspective: Creates a perspective for a specified account.
update_ccm_perspective: Updates a perspective for a specified account.
delete_ccm_perspective: Deletes a perspective for a specified account.
ccm_perspective_grid: Query detailed cost perspective data in Harness Cloud Cost Management.
ccm_perspective_time_series: Query detailed cost perspective data, grouped by time in Harness Cloud Cost Management.
ccm_perspective_summary_with_budget: Query a summary of cost perspectives with budget information in Harness Cloud Cost Management, including detailed cost and budget data grouped by time.
ccm_perspective_budget: Query the budget information for a perspective in Harness Cloud Cost Management.
get_ccm_metadata: Retrieves metadata about available cloud connectors, cost data sources, default perspectives, and currency preferences in Harness Cloud Cost Management.
ccm_perspective_recommendations: Returns monthly cost, savings, and a list of open recommendations for a perspective in Harness Cloud Cost Management.
ccm_perspective_filter_values: Returns available filter values for a cost perspective, enabling dynamic discovery of valid options for advanced queries in Harness Cloud Cost Management.
list_ccm_recommendations: Returns a filterable list of cost-optimization recommendations in Harness Cloud Cost Management.
list_ccm_recommendations_by_resource_type: Returns a aggregated statistics of cloud cost optimization recommendations grouped by resource type within a given account in Harness Cloud Cost Management.
get_ccm_recommendations_stats: Returns overall statistics for cloud cost optimization recommendations within a given account in Harness Cloud Cost Management.
update_ccm_recommendation_state: Marks a recommendation as Applied/Open/Ignored in Harness Cloud Cost Management.
override_ccm_recommendation_savings: Overrides savings for a recommendation in Harness Cloud Cost Management.
create_jira_ticket_for_ccm_recommendation: Creates a Jira ticket for a recommendation in Harness Cloud Cost Management.
create_service_now_ticket_for_ccm_recommendation: Creates a Service Now ticket for a recommendation in Harness Cloud Cost Management.
get_ec2_recommendation_detail: Returns ECS Recommendation details for the given Recommendation identifier.
get_azure_vm_recommendation_detail: Returns Azure Vm Recommendation details for the given Recommendation identifier.
get_ecs_service_recommendation_detail: Returns ECS Service Recommendation details for the given Recommendation identifier.
get_node_pool_recommendation_detail: Returns Node Pool Recommendation details for the given Recommendation identifier.
get_workload_recommendation_detail: Returns Workload Recommendation details for the given Recommendation identifier.
list_jira_projects: Returns a list of Jira projects available to create tickets for recommendations in Harness Cloud Cost Management.
list_jira_issue_types: Returns a list of Jira Issue types available to create tickets for recommendations in Harness Cloud Cost Management.
get_ccm_anomalies_summary: Returns a summary of cost anomalies for a specified account in Harness Cloud Cost Management.
list_ccm_anomalies: Returns a list of cost anomalies for a specified account in Harness Cloud Cost Management.
list_ccm_ignored_anomalies: Returns a list of ignored cost anomalies for a specified account in Harness Cloud Cost Management.
get_ccm_anomalies_for_perspective: Returns a anomalies for a perspective and account in Harness Cloud Cost Management.
list_all_ccm_anomalies: Returns a list of all cost anomalies for a specified account in Harness Cloud Cost Management.
list_filter_values_ccm_anomalies: Returns the list of distinct values for all the specified anomalies for a specified account in Harness Cloud Cost Management.
report_ccm_anomaly_feedback: Reports feedback for an anomaly and account in Harness Cloud Cost Management.
get_ccm_commitment_coverage: Get commitment coverage information for an account in Harness Cloud Cost Management.
get_ccm_commitment_savings: Get commitment savings information for an account in Harness Cloud Cost Management.
get_ccm_commitment_utilisation: Get commitment utilisation information for an account in Harness Cloud Cost Management broken down by Reserved Instances and Savings Plans in day wise granularity.
get_ccm_estimated_savings: Get estimated savings information for a cloud account in Harness Cloud Cost Management
get_ccm_commitment_ec2_analysis: Get AWS EC2 commitment analysis for an account in Harness Cloud Cost Management, including RI/SP commitment spend, utilization breakdown, current savings, estimated annualized savings, and ESR.

Database Operations Toolset

Toolset Name: dbops

get_database_schema_info: Retrieves metadata about a database schema including its identifier, instance identifier, and database type.

Chaos Engineering Toolset

Toolset Name: chaos

chaos_experiments_list: List all the chaos experiments for a specific account.
chaos_experiment_describe: Get details of a specific chaos experiment.
chaos_experiment_run: Run a specific chaos experiment.
chaos_experiment_run_result: Get the result of a specific chaos experiment run.

Supply Chain Security (SCS) Toolset

Toolset Name: scs

list_artifact_sources: List all artifact sources available in Harness SCS for a specific organization and project.
list_artifacts_per_source: List all artifacts within a specific artifact source.
get_artifact_overview: Get metadata, security findings, SBOM, and compliance status for a specific artifact.
get_artifact_chain_of_custody: Retrieve the full chain of custody (event history) for a specific artifact.
fetch_compliance_results_by_artifact: Fetch compliance results for a specific artifact.
get_code_repository_overview: Get an overview of vulnerabilities, SBOM, compliance issues, and policy violations for a code repository.
list_scs_code_repos: List all code repositories scanned by Harness SCS.

Security Test Orchestration (STO) Toolset

Toolset Name: sto

frontend_all_issues_list: List and filter security issues in Harness STO by target, pipeline, tool, severity, exemption status, and type.
global_exemptions: List all global exemptions in Harness STO.
promote_exemption: Promote a specific exemption to a global exemption.
approve_exemption: Approve a specific exemption.

Logs Toolset

Toolset Name: logs

download_execution_logs: Download logs for a pipeline execution

Templates Toolset

Toolset Name: templates

list_templates: List templates at a given scope
intelligent_template_search: Find the most relevant templates based on a natural language description.

Internal Developer Portal Toolset

Toolset Name: idp

get_entity: Get details of a specific entity in the Harness IDP Catalog
list_entities: List entities in the Harness Internal Developer Portal Catalog
get_scorecard: Get details of a specific entity in the Harness IDP Catalog
list_scorecards: List scorecards in the Harness Internal Developer Portal Catalog
get_score_summary: Get Score Summary for Scorecards in the Harness Internal Developer Portal Catalog.
get_scores: Get Scores for Scorecards in the Harness Internal Developer Portal Catalog.

Audit Trail Toolset

Toolset Name: audit

list_user_audits: Retrieve the complete audit trail for a specified user.

Feature Management and Experimentation (FME) Toolset

Toolset Name: fme

list_fme_workspaces: List all FME workspaces
list_fme_environments: List environments for a specific workspace
list_fme_feature_flags: List feature flags for a specific workspace
get_fme_feature_flag_definition: Get the definition of a specific feature flag in an environment

Prerequisites

You will need to have Go 1.23 or later installed on your system.
A Harness API key for authentication.

Quickstart

Makefile Usage

This project provides a Makefile to simplify common development tasks. The main targets are:

make build – Build the mcp-server binary with version information embedded.
make init – Set up git hooks and submodules for pre-commit checks.
make dep – Download Go module dependencies.
make tools – Install tools required for the build (if any are specified).
make format – Format Go code using goimports and gci.

You can run any of these commands from the project root. For example:

make build
make format

Build from Source

Clone the repository:

git clone https://github.com/harness/mcp-server.git
cd mcp-server

Build the binary:

go build -o cmd/harness-mcp-server/harness-mcp-server ./cmd/harness-mcp-server

Run the server:

HARNESS_API_KEY=your_api_key HARNESS_DEFAULT_ORG_ID=your_org_id HARNESS_DEFAULT_PROJECT_ID=your_project_id ./cmd/harness-mcp-server/harness-mcp-server stdio

Use Docker Image

Alternatively, you can use the pre-built Docker image:

docker run -i --rm \
  -e HARNESS_API_KEY=your_api_key \
  -e HARNESS_DEFAULT_ORG_ID=your_org_id \
  -e HARNESS_DEFAULT_PROJECT_ID=your_project_id \
  -e HARNESS_BASE_URL=your_base_url \
  harness/mcp-server stdio

Integration with AI Assistants

Usage with Gemini CLI

Add the server configuration to your Gemini config file at: ~/.gemini/settings.json

{
  "theme": "Default",
  "selectedAuthType": "oauth-personal",
  "mcpServers": {
    "Harness": {
      "command": "/path/to/harness-mcp-server",
      "args": ["stdio"],
      "env": {
        "HARNESS_API_KEY": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
      }
    }
  }
}

Usage with Gemini CLI Extensions

You will need to run the following command to install the Harness MCP as an extension:

gemini extensions install https://github.com/harness/mcp-server

Then you will need to set the environment variables for the extension:

export HARNESS_API_KEY="your_api_key_here"

Launch Gemini and start asking questions about Harness!

gemini

Claude Desktop Configuration

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json

Server Configuration

{
  "mcpServers": {
    "harness": {
      "command": "/path/to/harness-mcp-server",
      "args": ["stdio"],
      "env": {
        "HARNESS_API_KEY": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>"
      }
    }
  }
}

Usage with Claude Code

Add the server configuration to your Claude config file at: ~/.claude.json

{
  "mcpServers": {
    "Harness": {
      "command": "/path/to/harness-mcp-server",
      "args": ["stdio"],
      "env": {
        "HARNESS_API_KEY": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
        "HARNESS_BASE_URL": "<YOUR_BASE_URL>"
      }
    }
  }
}

Usage with Windsurf

To use the Harness MCP Server with Windsurf:

Add the server configuration to your Windsurf config file:

Using Local Binary

{
  "mcpServers": {
    "harness": {
      "command": "/path/to/harness-mcp-server",
      "args": ["stdio"],
      "env": {
        "HARNESS_API_KEY": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
        "HARNESS_BASE_URL": "<YOUR_BASE_URL>"
      }
    }
  }
}

Using Docker Image

{
  "mcpServers": {
    "harness": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HARNESS_API_KEY",
        "-e",
        "HARNESS_DEFAULT_ORG_ID",
        "-e",
        "HARNESS_DEFAULT_PROJECT_ID",
        "-e",
        "HARNESS_BASE_URL",
        "harness/mcp-server",
        "stdio"
      ],
      "env": {
        "HARNESS_API_KEY": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
        "HARNESS_BASE_URL": "<YOUR_BASE_URL>"
      }
    }
  }
}

Usage with Amazon Q Developer CLI

To use the Harness MCP Server with Amazon Q Developer CLI:

Add the server configuration to your Amazon Q config file at: ~/.aws/amazonq/mcp.json

Using Local Binary

{
  "mcpServers": {
    "harness": {
      "command": "/path/to/harness-mcp-server",
      "args": ["stdio"],
      "env": {
        "HARNESS_API_KEY": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
        "HARNESS_BASE_URL": "<YOUR_BASE_URL>"
      }
    }
  }
}

Cursor Configuration

{
  "mcpServers": {
    "harness": {
      "command": "/path/to/harness-mcp-server",
      "args": ["stdio"],
      "env": {
        "HARNESS_API_KEY": "your_api_key",
        "HARNESS_DEFAULT_ORG_ID": "your_org_id",
        "HARNESS_DEFAULT_PROJECT_ID": "your_project_id",
        "HARNESS_BASE_URL": "<if-needed>"
      }
    }
  }
}

Cursor MCP Guide

VS Code Configuration

{
  "mcp": {
    "servers": {
      "harness": {
        "command": "docker",
        "args": [
          "run",
          "-i",
          "--rm",
          "-e",
          "HARNESS_API_KEY",
          "-e",
          "HARNESS_DEFAULT_ORG_ID",
          "-e",
          "HARNESS_DEFAULT_PROJECT_ID",
          "-e",
          "HARNESS_BASE_URL",
          "harness/mcp-server",
          "stdio"
        ],
        "env": {
          "HARNESS_API_KEY": "<YOUR_API_KEY>",
          "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
          "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
          "HARNESS_BASE_URL": "<YOUR_BASE_URL>"
        }
      }
    }
  }
}

VS Code MCP Guide

Tool Usage Guide

Download Execution Logs

Using Docker:

We need to mount the logs directory to the container to download the logs.

docker run -d --name mcp-server -p 8080:8080 -v /path/to/logs/in/host:/path/in/container harness/mcp-server --output-dir=/path/in/container

This ensures that the logs downloaded to container are accessible in the host.

Example:

docker run -d --name mcp-server -p 8080:8080 -v /Users/testuser/logs:/logs harness/mcp-server --output-dir=/logs

Sample MCP Configuration:

{
  "mcpServers": {
    "harness": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-v",
        "/Users/testuser/logs:/logs",
        "-e",
        "HARNESS_MCP_USER_PAT",
        "-e",
        "HARNESS_DEFAULT_ORG_ID",
        "-e",
        "HARNESS_DEFAULT_PROJECT_ID",
        "-e",
        "HARNESS_MCP_BASE_URL",
        "harness/mcp-server",
        "stdio",
        "--output-dir=/logs", #/path/in/container
        "--toolsets=logs",
        "--api-key="
      ],
      "env": {
        "HARNESS_MCP_USER_PAT": "<YOUR_API_KEY>",
        "HARNESS_DEFAULT_ORG_ID": "<YOUR_ORG_ID>",
        "HARNESS_DEFAULT_PROJECT_ID": "<YOUR_PROJECT_ID>",
        "HARNESS_MCP_BASE_URL": "<YOUR_BASE_URL>"
      }
    }
  }
}

Example Tool Input:

{
  "logs_directory": "pipeline-logs",
  "org_id": "<YOUR_ORG_ID>",
  "plan_execution_id": "<YOUR_PLAN_EXECUTION_ID>",
  "project_id": "<YOUR_PROJECT_ID>"
}

Sample Response:

Files downloaded to : /Users/testuser/logs/pipeline-logs/logs-<YOUR_PLAN_EXECUTION_ID>/logs.zip

Using Local Binary:

Example configuration:

"args": ["stdio", "--toolsets=logs", "--api-key=", "--output-dir=/Users/testuser/log-files"]

Example Tool Input:

{
  "logs_directory": "logs1",
  "project_id": "<YOUR_PROJECT_ID>",
  "plan_execution_id": "<YOUR_PLAN_EXECUTION_ID>",
  "org_id": "<YOUR_ORG_ID>"
}

Sample Response:

Files downloaded to : /Users/testuser/log-files/logs1/logs-<YOUR_PLAN_EXECUTION_ID>/logs.zip

Development

Command Line Arguments

The Harness MCP Server supports the following command line arguments:

--toolsets: Comma-separated list of tool groups to enable, if the list is empty or flag is not set, only default toolset is enabled. Use --toolsets=all to enable all available toolsets. Note: This flag is only effective when --enable-license is false (the default).
--enable-license: Enable license validation and module-based toolset management (default is false, i.e OSS version). When set to true, toolsets are managed through modules.
--enable-modules: Comma-separated list of modules to enable (only used when --enable-license is true). Use --enable-modules=all to enable all available modules, or specify individual modules like --enable-modules=CORE,CI,CD.
--read-only: Run the server in read-only mode
--log-file: Path to log file for debugging
--log-level: Set the logging level (debug, info, warn, error)
--version: Show version information
--help: Show help message
--base-url: Base URL for Harness (default: "https://app.harness.io")
--output-dir: Directory where the tool writes output files (e.g., pipeline logs)

Environment Variables

Environment variables are prefixed with HARNESS_:

HARNESS_API_KEY: Harness API key (required) - Account ID is automatically extracted from the API key
HARNESS_DEFAULT_ORG_ID: Default Harness organization ID (optional, if not specified it would need to be passed in the request if it's required for that operation)
HARNESS_DEFAULT_PROJECT_ID: Default Harness project ID (optional, if not specified it would need to be passed in the request if it's required for that operation)
HARNESS_TOOLSETS: Comma-separated list of toolsets to enable (default: "all")
HARNESS_READ_ONLY: Set to "true" to run in read-only mode
HARNESS_LOG_FILE: Path to log file
HARNESS_LOG_LEVEL: Set the logging level (debug, info, warn, error)
HARNESS_BASE_URL: Base URL for Harness (default: "https://app.harness.io")

Authentication

The server uses a Harness API key for authentication. This can be set via the HARNESS_API_KEY environment variable.

Using the create_follow_up_prompt Tool to generate actionable prompt events

The create_follow_up_prompt tool allows you to generate actionable prompt events that appear as buttons in the UI. These buttons can navigate users to specific pages within the Harness platform.

Here's how to use it:

{
  "actions": [
    {
      "text": "Button Text",
      "action": "OPEN_ENTITY_NEW_TAB",
      "data": {
        "pageName": "PAGE_NAME",
        "metadata": {
          "<KEY>": "<VALUE>"
        }
      }
    }
  ]
}

Parameters:

text: The text to display on the button
action: The action to perform (currently supports OPEN_ENTITY_NEW_TAB)
data: Contains navigation information
- pageName: The page to navigate to (e.g., ExecutionPipelineView, PipelineStudio, etc.)
- metadata: Key-value pairs needed for the target page (e.g., {"executionId": "abc123", "pipelineId": "xyz789"})

Example:

actionData := `{"actions": [{"text": "View Pipeline", "action": "OPEN_ENTITY_NEW_TAB", "data": {"pageName": "PipelineStudio", "metadata": {"id": "pipeline-id"}}}]}`

Alternative: Quick Prompts

If you provide an array of strings instead of the actions object, these strings will be added to the message box as quick prompts that users can click on:

// Add quick prompts to the message box
quickPrompts := `["Show me pipeline details", "List recent executions", "Analyze performance"]`

Notes for Local Testing

There might be certain tools that are not added in external mode or vice-versa, for local testing, following changes in pkg/harness/tools.go need to be done in mcp-server code to enable that certain tool in both internal and external modes.

baseURL := "https://localhost:8000"
secret := <SERVICE_SECRET>

Example

// registerGenai registers the genai toolset
func registerGenai(config *config.Config, tsg *toolsets.ToolsetGroup) error {

	// Determine the base URL and secret for genai service
	baseURL := "http://localhost:8000"
	secret := <GENAI_SECRET>

	// Create base client for genai with the default timeout
	c, err := CreateClient(baseURL, config, secret, defaultGenaiTimeout)
	if err != nil {
		return err
	}
  .
  .
  .

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector with this command:

npx @modelcontextprotocol/inspector /path/to/harness-mcp-server stdio

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

Testing

Running E2E Tests

The project includes end-to-end (E2E) tests that validate the integration with Harness services. To run these tests:

Set up the required environment variables:

export HARNESS_MCP_SERVER_E2E_TOKEN=<your_harness_api_token>
export HARNESS_MCP_SERVER_E2E_ACCOUNT_ID=<your_account_id>  
export HARNESS_MCP_SERVER_E2E_ORG_ID=<your_org_id>          
export HARNESS_MCP_SERVER_E2E_PROJECT_ID=<your_project_id>  
export HARNESS_MCP_SERVER_E2E_BASE_URL=<base_url>

Run the E2E tests using the Go test command with the e2e build tag:

go test -tags=e2e ./test/e2e/... -v

To run specific E2E tests, use the -run flag:

go test -tags=e2e ./test/e2e/... -v -run TestPipelineWorkflow

In VS Code, you can run the E2E tests directly using the launch.json configuration. Simply open the Run and Debug view, select the E2E test configuration from the dropdown menu, and click the Run button.

The E2E tests create an in-process MCP client that communicates with the Harness API using your provided credentials.

Name		Name	Last commit message	Last commit date
Latest commit History 209 Commits
.harness		.harness
.vscode		.vscode
chart		chart
client		client
cmd/harness-mcp-server		cmd/harness-mcp-server
config		config
docs		docs
pkg		pkg
test		test
.gitignore		.gitignore
CONTRIBUTOR_LICENSE_AGREEMENT.md		CONTRIBUTOR_LICENSE_AGREEMENT.md
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
SECURITY.md		SECURITY.md
gemini-extension.json		gemini-extension.json
go.mod		go.mod
go.sum		go.sum
go_tools.go		go_tools.go

License

harness/mcp-server

Folders and files

Latest commit

History

Repository files navigation

Harness MCP Server

Table of Contents

Components

Tools

Default Toolset

Pipelines Toolset

Pull Requests Toolset

Services Toolset

Environments Toolset

Infrastructure Toolset

Connectors Toolset

Repositories Toolset

Registries Toolset

Dashboards Toolset

Cloud Cost Management Toolset

Database Operations Toolset

Chaos Engineering Toolset

Supply Chain Security (SCS) Toolset

Security Test Orchestration (STO) Toolset

Logs Toolset

Templates Toolset

Internal Developer Portal Toolset

Audit Trail Toolset

Feature Management and Experimentation (FME) Toolset

Prerequisites

Quickstart

Makefile Usage

Build from Source

Use Docker Image

Integration with AI Assistants

Usage with Gemini CLI

Usage with Gemini CLI Extensions

Claude Desktop Configuration

Usage with Claude Code

Usage with Windsurf

Using Local Binary

Using Docker Image

Usage with Amazon Q Developer CLI

Using Local Binary

Cursor Configuration

VS Code Configuration

Tool Usage Guide

Download Execution Logs

Using Docker:

Using Local Binary:

Development

Command Line Arguments

Environment Variables

Authentication

Using the create_follow_up_prompt Tool to generate actionable prompt events

Parameters:

Example:

Alternative: Quick Prompts

Notes for Local Testing

Example

Debugging

Testing

Running E2E Tests

About

Resources

License

Security policy

Uh oh!

Stars

Watchers

Forks

Releases 17

Packages 0

Uh oh!

Contributors 28

Languages

Packages