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 supports the following authentication methods. 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 ways in your client configuration:

Option 1 — API Key header (recommended)

Use an API Key generated from the OpsHub Integration Manager UI. Refer to API Key Management for details. This is the most secure option as the key is dedicated, revocable, and keeps your user credentials out of configuration files entirely. Pass it via the x-api-key header:

{
  "servers": {
    "opshub-mcp": {
      "url": "<OpsHub Integration Manager URL>/OpsHubWS/mcp",
      "type": "http",
      "headers": {
        "x-api-key": "<your-api-key>"
      }
    }
  },
  "inputs": []
}

Alternatively, you can pass the API Key via the Authorization header:

Tip: To generate an API Key, go to Administration → API key in OpsHub Integration Manager. See API Key Management for step-by-step instructions.

Option 2 — base64-encoded authorization header

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.

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

Option 3 — username and password as headers

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

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.

Claude Code

Cline

Continue

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:

• 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.