Connect an AI client

Connect to the MCP server from known AI clients: Claude Desktop, VS Code and IntelliJ with GitHub Copilot, and Cursor.

In this topic:

Overview

Before connecting a client, your admin needs to complete OpenText Software Delivery Management-side prerequisites in Enable MCP and register clients.

If your organization maintains a registry of approved MCP server connections, connect to the OpenText Software Delivery Management MCP server through that registry. Contact your administrator to determine whether a registry-based connection is available and how to enable it. If no organizational registry is available, follow the manual configuration instructions below for your AI client.

In your AI client, to add the MCP server to the client's tools, you need to add an entry to the tool's configuration or MCP JSON file.

The JSON entry includes the URL of the MCP endpoint. The URL pattern is: https://myoctane.company.com/mcp. The possible addresses for cloud tenants are:

• https://almoctane-ams.saas.microfocus.com/mcp

• https://almoctane-apj.saas.microfocus.com/mcp

• https://almoctane-eur.saas.microfocus.com/mcp

If you are using API key authentication, the entry should include also an authorization header with the API access token. If you are using OAuth authentication, the JSON entry does not need a headers section.

Follow the instructions below for your AI client.

Claude desktop

This section contains details for adding the MCP server to Claude desktop.

Config file location

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Config snippet

{
    "mcpServers": {
        "<server-name>": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-remote",
                "https://myoctane.company.com/mcp",
                "--static-oauth-client-info",
                "{\"client_id\": \"<client_id>\"}"
            ]
        }
    }
}

{
    "mcpServers": {
        "<server-name>": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-remote",
                "https://myoctane.company.com/mcp",
                "--header",
                "Authorization: Bearer <your-token>"
            ]
        }
    }
}

• Replace https://myoctane.company.com/mcp with your actual base URL and /mcp suffix.

• Replace <server-name> with a short, descriptive label for this server (for example, octane). This name appears in the client's MCP server list and must be unique among your configured servers.

• Replace <client_id> with your OAuth client ID.

• Replace <your-token> with your API access token.

VS Code and IntelliJ with GitHub Copilot

This section contains details for adding the MCP server to VS Code and IntelliJ with GitHub Copilot.

See each client documentation for the exact steps to access the MCP configuration file for editing.

In both clients, open the generated mcp.json file and add one of the following entries.

{
    "servers": {
        "<server-name>": {
            "type": "http",
            "url": "https://myoctane.company.com/mcp"
        }
    }
}

{
    "servers": {
        "<server-name>": {
            "type": "http",
            "url": "https://myoctane.company.com/mcp",
            "headers": {
                "Authorization": "Bearer <your-token-or-variable>"
            }
        }
    }
}

• Replace https://myoctane.company.com/mcp with your actual base URL and /mcp suffix.

• Replace <server-name> with a short, descriptive label for this server (for example, octane). This name appears in the client's MCP server list and must be unique among your configured servers.

• VS Code: Replace <your-token-or-variable> with ${input:octaneApiToken}. VS Code prompts you for the token value on first use and stores it in its secure secret storage � no plaintext token in the file.

Save the file, then verify in Copilot Chat that tools from the new server are listed in the tools picker.

Cursor

Cursor reads MCP configuration from .cursor/mcp.json at the project root.

Config snippet

{
  "mcpServers": {
    "<server-name>": {
      "url": "https://myoctane.company.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "<server-name>": {
      "url": "https://myoctane.company.com/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}

• Replace https://myoctane.company.com/mcp with your actual base URL and /mcp suffix.

• Replace <server-name> with a short, descriptive label for this server (for example, octane). This name appears in the client's MCP server list and must be unique among your configured servers.

• Replace <your-token> with the API access token.

Use the OpenText Software Delivery Management MCP in your client

Confirm that OpenText Software Delivery Management MCP is enabled

After configuration, verify that the server is active in your client:

• Claude Desktop: Open the tools picker in a chat and confirm that the MCP tools are listed.
• VS Code with GitHub Copilot: Open Copilot Chat, click Tools, and verify the MCP tools are listed and enabled.
• Cursor: Open Composer and confirm the MCP tools are available in the agent tools list.

If the tools are not visible, recheck the MCP configuration file path, the server URL (<octane-base-url>/mcp), and restart the client.

What to expect on first use

• API Access Key (Token) setup: If you configured a static Authorization: Bearer ... header, calls work immediately with no browser login. If you used an input variable in VS Code, the client prompts once for the token value at first use and stores it securely.
• OAuth 2.1 setup: On first tool use, the client opens a browser sign-in flow. After successful login, the client receives tokens and continues without manually entering an API token.

After first-time authentication succeeds, the MCP tools should run normally in subsequent chats.