Configuring Claude Desktop

Configure Claude Desktop to connect to the MCP Server for Vulnerability Remediation through an HTTP-to-stdio bridge.

About this task

Claude Desktop commonly launches local MCP servers through stdio. Because the MCP Server for Vulnerability Remediation exposes a streamable HTTP endpoint, configure an HTTP-to-stdio bridge such as mcp-remote.

Procedure

  1. Edit the Claude Desktop configuration file.

    macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    {
  "mcpServers": {
    "bes-mcp-fixlet-gen": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://127.0.0.1:9495/",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <bigfix-token>"
      }
    }
  }
}
  2. Restart Claude Desktop completely.

    For a shared server, replace the URL with its DNS name or IP address. Keep the space after Bearer in the environment value. Node-based clients may also require NODE_EXTRA_CA_CERTS to point to the copied selfsigned_cert.pem certificate. Completely restart Claude Desktop after changing the configuration.

What to do next

Important:
Claude Desktop does not support the VS Code-style interactive token input. This example stores the token as plain text in claude_desktop_config.json; restrict access to the file and use a dedicated, revocable token. Where secrets in configuration files are prohibited, use a wrapper that retrieves the token from the operating-system credential store and starts mcp-remote with AUTH_HEADER set.