Welcome
Administration
This section provides information on administration, installation, configuration, and integrations and teamspace management.
DevOps Loop MCP server
The DevOps Loop Model Context Protocol (MCP) server provides a standardized interface so that external MCP clients can interact with DevOps Loop and perform supported operations.
Configuring an external MCP server in a teamspace
You can configure an external MCP server in DevOps Loop to connect to external MCP services and make them available to all loops in a teamspace.

Release Notes
This document includes information about the features introduced, a product overview, and installation instructions, as well as contact information of HCL Customer Support for this version of HCL DevOps Loop.
System Requirements
This document includes information about hardware and software requirements for HCL DevOps Loop.
Getting Started
HCL DevOps Loop is a platform designed to support the full DevOps lifecycle. The Getting Started section introduces key concepts and walks through the initial steps to help new users begin working with the platform.
Administration
This section provides information on administration, installation, configuration, and integrations and teamspace management.
- Configuration of external databases for the capabilities in DevOps Loop
  DevOps Loop capabilities use databases to store configuration data, execution results, and operational information. In the default configuration, some capabilities deploy internal databases as part of the Helm installation. However, you can configure the capabilities to use external databases that are managed outside the Kubernetes cluster.
- Installation of DevOps Loop
  To get started working with HCL DevOps Loop, you must first install the platform in your environment.
- License management and user administration
  After you install DevOps Loop, you must manage licenses, users, and authentication to control access to platform resources.
- Backup and restoration of DevOps Loop
  You must back up HCL DevOps Loop data before you uninstall the current version of DevOps Loop. You must back up the data to avoid data loss or inaccessibility.
- Private CA and self-signed certificate support
  A private Certificate Authority (CA) is an organization-specific service that issues and manages digital certificates for use within an enterprise’s private network. These certificates secure communication between internal applications and services.
- Upgrading DevOps Loop
  After you complete the required backup and pre-upgrade tasks, you can upgrade DevOps Loop to a newer version.
- Integrations in DevOps Loop
  DevOps Loop provides a set of integrations to extend the platform’s capabilities and connect your loops to external systems and intelligent tools. These integrations enable you to automate tasks, enhance productivity, and interact with loop resources from outside the DevOps Loop interface.
- DevOps Loop MCP server
  The DevOps Loop Model Context Protocol (MCP) server provides a standardized interface so that external MCP clients can interact with DevOps Loop and perform supported operations.
  - Getting started with the DevOps Loop MCP server
    Use the Loop MCP endpoint to fetch and manage loop platform entities, including loops, teamspaces, users, and loop analytics.
  - DevOps Loop MCP server configuration in VS Code
    You can connect Visual Studio Code (VS Code) with GitHub Copilot to the DevOps Loop MCP server to run MCP-based queries that retrieve and update loop resources directly from VS Code. After the connection is established, the MCP server configuration is saved and remains available across VS Code sessions.
  - Connecting Claude to the DevOps Loop MCP server
    You can connect Claude to the DevOps Loop MCP Server and use it as a connector to retrieve and update loop resources.
  - Configuring an external MCP server in a teamspace
    You can configure an external MCP server in DevOps Loop to connect to external MCP services and make them available to all loops in a teamspace.
- Teamspace management
  A teamspace in HCL DevOps Loop is a secure, dedicated environment designed for multiple teams to work independently within a single shared DevOps Loop installation.
- Uninstalling DevOps Loop
  You can safely uninstall DevOps Loop from your environment, ensuring that all resources and data are properly removed.
Working with Loops
A loop is a workflow that connects DevOps activities of your team from planning and development through build, deployment, testing, and release phases.
Capabilities of DevOps Loop
HCL DevOps Loop provides an integrated suite of capabilities such as Plan, Code, Control, Build, Test, Release, Deploy, Measure and Harbor (if enabled) to manage every stage of the software development lifecycle within a connected, continuous loop.
Loop Genie overview - Tech Preview
Loop Genie is an AI-powered assistant integrated into DevOps Loop. It provides a unified conversational interface for retrieving information and performing actions across multiple DevOps Loop capabilities.
Troubleshooting
Offline Documentation (PDF)
You can access the following link to view or download the release notes, system requirements, and user documentation for DevOps Loop in a Portable Document Format (PDF) file.
Security Considerations
This document describes the actions that you can take to ensure that your installation is secure, customize your security settings, and set up user access controls in HCL DevOps Loop.
Notices
This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Configuring an external MCP server in a teamspace

You can configure an external MCP server in DevOps Loop to connect to external MCP services and make them available to all loops in a teamspace.

Before you begin

You must have completed the following tasks:

Ensured that you have administrative privileges in DevOps Loop.
Ensured that you must have a valid MCP server endpoint URL.

Procedure

Navigate to Settings > Installed Integrations.
The Installed Integrations page is displayed.
Click the MCP tab.
Click Add Server.
The Add Server pane is displayed.
Enter a name to identify the MCP server in the Name field.
For example, GitHub MCP Server.
Select the appropriate domain from the Domain list.

Note:
Each MCP server belongs to a Domain. Only one MCP server can be enabled for a Domain at a time. If you are adding a new MCP server to an existing domain, ensure that other MCP servers of the same domain are disabled.

Note:
If you select Others in the Domain list, the MCP server name is used as the domain value for that MCP server.
Enter the MCP server endpoint URL in the Server URL field.
Keep OAuth selected as the Credential Type.
Optional: Enter the client ID in the Client ID field.
Optional: Enter the client secret in the Client Secret field.
Click Save.

The OAuth authentication window is displayed.
Complete the OAuth authentication process.
The MCP server is added to DevOps Loop within a teamspace.
Use the toggle switch in the Manage External MCP list to enable the MCP server.

Note:
Newly added MCP servers are disabled, which is the default setting. If AI integration is inactive, the MCP server cannot be enabled.

Results

The MCP server is added to the Manage External MCP list. When the MCP server is enabled, it is available to all loops within the teamspace.

What to do next

The teamspace members can authenticate and use the MCP server through Loop Genie.