Windows-MCP-Server-Installation-Verification-Guide

Created By
trevorwilkersona year ago
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.
Overview

Windows MCP Server Installation Verification Guide

This project provides a comprehensive guide for setting up and verifying a Microsoft MCP server on Windows, focusing on distinct requirements compared to Mac setups.

how to use the guide?

Follow the step-by-step instructions outlined in the guide, starting with prerequisites checks through to execution tests.

key features of the guide?

  • Detailed prerequisites verification
  • Step-by-step installation and package checks
  • Execution tests with complete paths
  • Troubleshooting section for common installation issues

use cases of the guide?

  1. Verifying MCP server installations on Windows
  2. Understanding differences in node package management between Windows and MacOS
  3. Troubleshooting common installation problems quickly

FAQ from the guide?

  • What are the main installation differences between Windows and MacOS?

Windows requires absolute file paths and the explicit use of node.exe, unlike Mac which can use npx commands.

  • How do I check if npm is installed?

Open Command Prompt as administrator and run npm --version to verify.

  • What should I do if I encounter a MODULE_NOT_FOUND error?

Verify your installation and ensure all paths match exactly. Run npm install -g @modelcontextprotocol/server-sequential-thinking if needed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
trevorwilkerson
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago