Connecting an MCP client to DevOps Deploy MCP server
To enable an MCP client to communicate with the HCL DevOps Deploy (Deploy) MCP server, you must define Deploy server connection details within an MCP client's configuration.
You must perform the following tasks for a successful connection of the Deploy MCP server
to an MCP client:
- Install an MCP client: You can use any MCP client, such as VS Code, Claude, and so on, to connect to the Deploy MCP server. Each MCP client has its own specific UI, command palette, or dedicated settings file for configuration. You must refer to the independent software vendor documentation for client-specific instructions.
- Add Deploy MCP server properties: Edit the client configuration file or settings to add the Deploy MCP server properties. See MCP server properties and Configuration file example.
- Start the server: Start the Deploy MCP server from the MCP client.
MCP server properties
| Property | Description | Required Value/Format |
|---|---|---|
"type" |
Indicates the server connection protocol. | http |
"url" |
Specifies the full Deploy MCP server URL. | https://deployServer_hostname:deployPort/mcp |
"Authorization" |
Provides a valid bearer access token ID. You must ensure that a realm is selected for the bearer authentication in the System Settings. See System settings. |
|
Configuration file example
The following JSON format illustrates how you can define the Deploy MCP
server properties in your VS Code MCP configuration file
(mcp.json):
{
"servers": {
"devops-deploy-local": {
"type": "http",
"url": "https://deployServer_hostname:deployPort/mcp",
"headers": {
"Authorization": "Bearer tokenID"
}
}
},
"inputs": []
}After a successful connection is established, you can use the integrated MCP tools to perform various deployment tasks. See Using the Deploy MCP tools.