Knowledge Base

How to install the Sectigo SCM MCP server on Windows with Claude Desktop

Updated on June 28, 2026

Overview

By the end of this guide, you will have installed Node.js and Claude Desktop, installed the Sectigo SCM MCP proxy package, added the MCP server configuration to Claude Desktop, and confirmed that Claude Desktop can reach the SCM server and list its tools. The guide covers the prerequisites, installing and validating Node.js, installing Claude Desktop and the MCP proxy, locating and editing the Claude Desktop configuration file, and validating the connection.

What is the Sectigo SCM MCP server?

The Sectigo Certificate Manager (SCM) Model Context Protocol (MCP) server exposes SCM capabilities — such as listing certificate profiles — as tools that an AI agent can call. Claude Desktop acts as the AI agent and connects to the server through a local proxy package.

Prerequisites

Windows 10/11, or Windows Server 2019/2022.

Claude Desktop installed.

Node.js installed.

The Sectigo MCP proxy package (a .tgz file).

SCM MCP client credentials.

Step 1 — Install and validate Node.js

Install Node.js: winget install -e --id OpenJS.NodeJS.LTS

Verify the installation by running node -v and npm -v.

Step 2 — Install Claude Desktop

Install and launch Claude Desktop.

Step 3 — Install the MCP proxy

Install the proxy package globally: npm install -g .\sectigo-mcp-proxy-26.5.0.tgz

Verify it is installed under %APPDATA%\npm.

Step 4 — Locate the configuration file

The Claude Desktop configuration file is named claude_desktop_config.json:

Standard installation: %APPDATA%\Claude\claude_desktop_config.json

MSIX (Microsoft Store) installation: AppData\Local\Packages\Claude_*\LocalCache\Roaming\Claude

Step 5 — Create the MCP configuration

In Claude Desktop, open Developer → Edit Config.

Add the SCM MCP server entry to the JavaScript Object Notation (JSON) configuration file, then save.

[Placeholder — add the exact configuration JSON here.] Include the server name (scm), the proxy command and arguments, and the SCM MCP client credential environment variables. This content was not present in the source document and must be supplied by the author or subject-matter expert before publishing.

Step 6 — Restart Claude Desktop

Restart Claude Desktop and confirm that the SCM server appears under the Developer section.

Step 7 — Validate the connection

Confirm that Claude Desktop can reach the server by entering these test prompts: