Windows-MCP-Server-Installation-Verification-Guide

by trevorwilkerson

19 stars
761 downloads
Not rated
GitHub

About

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 c

Details

Author
trevorwilkerson
GitHub stars
19
Downloads
761
Categories
Other

- Prerequisites check for npm and Node.js.
- Global package installation verification commands.
- Directory structure validation steps.
- Execution test with absolute paths.
- Troubleshooting for common Windows errors.
- Comparative guide between MacOS and Windows 10 setup.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Windows-MCP-Server-Installation-Verification-Guide
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

What are the main differences between MacOS and Windows 10 MCP server setup?

MacOS uses relative paths and npx commands, while Windows requires absolute file paths and explicit references to node.exe. MacOS global packages reside in /usr/local/lib/node_modules; Windows stores them in %APPDATA%\npm\node_modules. Configuration files on Windows must use double backslashes (\\) in paths.

Why does the server need absolute paths on Windows?

Windows does not resolve npm global modules via npx reliably in the MCP context. The guide instructs to use the full path to node.exe and the full path to the server’s dist/index.js file to ensure execution.

What should I do if I get a MODULE_NOT_FOUND error?

Verify the package is installed globally with npm list -g @modelcontextprotocol/server-sequential-thinking. If missing, reinstall with npm install -g @modelcontextprotocol/server-sequential-thinking. Ensure the file paths in your configuration match exactly, including case and backslashes.

How do I check if Node.js and npm are installed on Windows?

Open Command Prompt as administrator and run npm --version and where node. The where node command should output the path to node.exe, typically C:\Program Files\nodejs\node.exe. If not found, install Node.js and add it to your PATH.

What is the expected directory structure after installation?

The global modules folder should contain @modelcontextprotocol\server-sequential-thinking\dist\index.js. You can verify by navigating to %APPDATA%\npm\node_modules\@modelcontextprotocol and running dir commands to confirm the subdirectories exist.

sequentialthinking

A detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens. When to use this tool: - Breaking down complex problems into steps - Planning and design with room for revision - Analysis that might need course correction - Problems where the full scope might not be clear initially - Problems that require a multi-step solution - Tasks that need to maintain context over multiple steps - Situations where irrelevant information needs to be filtered out Key features: - You can adjust total_thoughts up or down as you progress - You can question or revise previous thoughts - You can add more thoughts even after reaching what seemed like the end - You can express uncertainty and explore alternative approaches - Not every thought needs to build linearly - you can branch or backtrack - Generates a solution hypothesis - Verifies the hypothesis based on the Chain of Thought steps - Repeats the process until satisfied - Provides a correct answer Parameters explained: - thought: Your current thinking step, which can include: * Regular analytical steps * Revisions of previous thoughts * Questions about previous decisions * Realizations about needing more analysis * Changes in approach * Hypothesis generation * Hypothesis verification - nextThoughtNeeded: True if you need more thinking, even if at what seemed like the end - thoughtNumber: Current number in sequence (can go beyond initial total if needed) - totalThoughts: Current estimate of thoughts needed (can be adjusted up/down) - isRevision: A boolean indicating if this thought revises previous thinking - revisesThought: If is_revision is true, which thought number is being reconsidered - branchFromThought: If branching, which thought number is the branching point - branchId: Identifier for the current branch (if any) - needsMoreThoughts: If reaching end but realizing more thoughts needed You should: 1. Start with an initial estimate of needed thoughts, but be ready to adjust 2. Feel free to question or revise previous thoughts 3. Don't hesitate to add more thoughts if needed, even at the "end" 4. Express uncertainty when present 5. Mark thoughts that revise previous thinking or branch into new paths 6. Ignore information that is irrelevant to the current step 7. Generate a solution hypothesis when appropriate 8. Verify the hypothesis based on the Chain of Thought steps 9. Repeat the process until satisfied with the solution 10. Provide a single, ideally correct answer as the final output 11. Only set nextThoughtNeeded to false when truly done and a satisfactory answer is reached

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "windows-mcp-server-installation-verification-guide": {
            "Windows-MCP-Server-Installation-Verification-Guide": {
                "command": "npx",
                "args": [
                    "@modelcontextprotocol/server-sequential-thinking"
                ]
            }
        }
    }
}

McpServers

{
    "Windows-MCP-Server-Installation-Verification-Guide": {
        "command": "npx",
        "args": [
            "@modelcontextprotocol/server-sequential-thinking"
        ]
    }
}

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.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.