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:

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:

2. If `MODULE_NOT_FOUND` error:

3. If node.exe not found:

4. If directory structure is incomplete:

Important Windows-Specific Notes

1. Always use double backslashes (\\) in config files

2. Use absolute paths rather than relative paths

3. Remember Windows path length limitations

4. Use `node.exe` path from `where node` command

5. Check permissions if access is denied

This guide ensures a methodical, thorough verification of your MCP server installation on Windows. Follow each step in order, and verify success before moving to the next step.

=-=-=-=-

Key differences between MacOS and Windows 10 for MCP server setup and installation.

Based on this analysis, here's a comprehensive comparison guide between MacOS and Windows 10 for MCP server setup:

MacOS vs Windows 10: MCP Server Setup Differences

File System Structure

MacOS

• Global packages: `/usr/local/lib/node_modules`
• Node executable: `/usr/local/bin/node`
• Config location: `~/Library/Application Support/Claude/`
• Uses forward slashes (/)
• Case-sensitive by default

Windows 10

• Global packages: `C:\Users\\AppData\Roaming\npm`
• Node executable: `C:\Program Files\nodejs\node.exe`
• Config location: `%APPDATA%\Claude\`
• Uses backslashes (\\)
• Case-insensitive

Command Execution

MacOS

# Package execution
npx @modelcontextprotocol/server-sequential-thinking

# Global installation
sudo npm install -g @package-name

# Permission setting
chmod +x ./script.sh

Windows 10

# Package execution
node "C:\Users\Username\AppData\Roaming\npm\node_modules\@package-name\dist\index.js"

# Global installation (as Administrator)
npm install -g @package-name

# Permission setting
# Run CMD as Administrator

Configuration File Format

MacOS

{
  "mcpServers": {
    "sequential-thinking": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sequential-thinking"
      ]
    }
  }
}

Windows 10

{
  "mcpServers": {
    "sequential-thinking": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": [
        "C:\\Users\\Username\\AppData\\Roaming\\npm\\node_modules\\@modelcontextprotocol\\server-sequential-thinking\\dist\\index.js"
      ]
    }
  }
}

Key Differences Summary

1. Path Handling

2. Package Management

3. Permissions

4. Environment Variables

5. Configuration Requirements

Converting Between Platforms

1. Path Conversion

2. Command Conversion

3. Configuration Conversion

Common Issues and Solutions

1. Windows Specific

2. Conversion Pitfalls