Configuration

This page covers how to authenticate with the OpsHub Integration Manager MCP server and how to configure popular MCP-compatible clients.

---

Authentication

The OpsHub Integration Manager MCP server currently supports basic authentication. Credentials are passed as part of the MCP client configuration headers.

Note: LDAP and SAML users cannot authenticate with the MCP server. This is because MCP clients do not perform browser-based or redirect-based login flows that LDAP and SAML require. Use a local OpsHub Integration Manager user account for MCP access.

Credentials can be passed in one of the following two ways in your client configuration:

Option 1 — username and password as headers

{
  "servers": {
    "opshub-mcp": {
      "url": "<OpsHub Integration Manager URL>/OpsHubWS/mcp",
      "type": "http",
      "headers": {
        "username": "mcpuser",
        "password": "password"
      }
    }
  },
  "inputs": []
}

Option 2 — base64-encoded authorization header (recommended)

For improved security, encode your credentials as a Base64 string in the format username:password and pass them via the standard Authorization header. This avoids exposing plain-text credentials in your configuration file.

{
  "servers": {
    "opshub-mcp": {
      "url": "<OpsHub Integration Manager URL>/OpsHubWS/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Basic <Base64 encoded username:password>"
      }
    }
  },
  "inputs": []
}

Tip: To generate the Base64 value, encode username:password using any Base64 encoder. For example, admin:password encodes to YWRtaW46cGFzc3dvcmQ=.

---

Client configuration

Below are sample configurations for popular MCP-compatible clients. Replace the URL and credentials with values specific to your OpsHub Integration Manager instance.

Visual Studio Code

Authorization Header

{
  "servers": {
    "opshub-mcp": {
      "url": "<OpsHub Integration Manager URL>/OpsHubWS/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Basic <Base64 encoded username:password>"
      }
    }
  },
  "inputs": []
}

Username & Password Headers

Claude Desktop

Note: Claude Desktop does not natively support HTTP-type MCP servers. The mcp-remote npm package is required as a bridge. Install it by running npm install -g mcp-remote, then use the configuration below.

Authorization Header

{
  "mcpServers": {
    "opshub-mcp": {
      "command": "<path-to-npm-global-bin>\\mcp-remote.cmd",
      "args": [
        "<OpsHub Integration Manager URL>/OpsHubWS/mcp",
        "--header",
        "Authorization: Basic <Base64 encoded username:password>"
      ]
    }
  }
}

Username & Password Headers

Claude Code

Authorization Header

{
  "mcpServers": {
    "opshub-mcp": {
      "type": "http",
      "url": "<OpsHub Integration Manager URL>/OpsHubWS/mcp",
      "headers": {
        "Authorization": "Basic <Base64 encoded username:password>"
      }
    }
  }
}

Username & Password Headers

Cline

Authorization Header

{
  "mcpServers": {
    "opshub-mcp": {
      "disabled": false,
      "timeout": 60,
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "<OpsHub Integration Manager URL>/OpsHubWS/mcp",
        "--header",
        "Authorization: Basic <Base64 encoded username:password>"
      ]
    }
  }
}

Environment Variables

Continue

Authorization Header

mcpServers:
  - name: opshub-mcp
    command: npx
    args:
      - "-y"
      - "mcp-remote"
      - "<OpsHub Integration Manager URL>/OpsHubWS/mcp"
      - "--header"
      - "Authorization: Basic <Base64 encoded username:password>"
    env: {}

Username & Password Headers

---

HTTPS configuration

If your OpsHub Integration Manager instance is configured on HTTPS, your MCP client must trust the SSL certificate used by the server.

• For clients that use mcp-remote as a bridge (Claude Desktop, Cline, Continue), the certificate must be trusted by your OS certificate store or Node.js environment.

• If you are using a self-signed or internal CA certificate, you may need to explicitly add it to Node.js using the NODE_EXTRA_CA_CERTS environment variable:

  NODE_EXTRA_CA_CERTS=/path/to/your/certificate.pem

• For VS Code and Claude Code, which connect directly over HTTP/HTTPS, ensure the certificate is trusted at the OS level.

Note: If you encounter SSL errors, contact your system administrator to obtain the correct certificate file and follow the steps above.