Windows-MCP-Server-Installation-Verification-Guide

Windows MCP server setup differs from Mac by requiring absolute file paths and explicit node.exe references instead of npx commands. The installation requires verifying npm and installing packages globally to the AppData\Roaming\npm\node_modules directory. Running servers needs complete paths for both node.exe and the server’s index.js file.

README.md file for now, script to come later…

=-=-=-=-=-

This guide assumes you have performed a basic MCP install on Windows 10. Guide created by Claude Desktop app running MCP servers.

Comprehensive Windows MCP Server Installation Verification Guide

I’ll use sequential thinking to analyze and create a comprehensive guide to the MCP sequential-thinking server.

Based on this analysis, here’s a comprehensive guide for verifying MCP server installation on Windows:

Prerequisites Check

1. Open Command Prompt as administrator
2. Verify npm installation:

   npm --version
   

3. Check npm’s global installation directory:

   npm config get prefix
   

   Note: Should point to C:\Users\\AppData\Roaming\npm

Installation Status Check

1. Check if package is already installed:

   npm list -g @modelcontextprotocol/server-sequential-thinking
   

2. Locate Node.js executable:

   where node
   

   Note: Usually at C:\Program Files\nodejs\node.exe

Package Installation

1. If not installed, run:

   npm install -g @modelcontextprotocol/server-sequential-thinking
   

2. Verify successful installation:

   npm list -g @modelcontextprotocol/server-sequential-thinking
   

Directory Structure Verification

1. Navigate to npm modules directory:

   cd %APPDATA%\npm\node_modules\@modelcontextprotocol
   

2. Verify folder structure:

   dir
   cd server-sequential-thinking
   dir
   cd dist
   dir
   

   Expected structure:
   • @modelcontextprotocol\
     • server-sequential-thinking\
       • dist\
         • index.js

Execution Test

1. Run server using absolute path:

   node "%APPDATA%\npm\node_modules\@modelcontextprotocol\server-sequential-thinking\dist\index.js"
   

2. Look for success message: “Sequential Thinking MCP Server running on stdio”

Troubleshooting Guide

1. If npm config get prefix shows unexpected location:

   • Reset npm prefix: npm config set prefix "%APPDATA%\npm"

2. If MODULE_NOT_FOUND error:

   • Verify installation: npm install -g @modelcontextprotocol/server-sequential-thinking
   • Check file paths match exactly

3. If node.exe not found:

   • Verify Node.js installation
   • Add to PATH if needed

4. If directory structure is incomplete:

   • Uninstall package: npm uninstall -g @modelcontextprotocol/server-sequential-thinking
   • Clear npm cache: npm cache clean --force
   • Reinstall package

Important Windows-Specific Notes