Claude MCP Get

🚀 Comprehensive Toolkit for Installing and Configuring Model Context Protocol (MCP) Server and Claude Desktop on Windows

This toolkit is designed to assist Windows users in successfully installing and utilizing the Model Context Protocol (MCP) server and Claude Desktop. It focuses on overcoming common issues encountered when connecting to MCP on Windows, particularly those related to the npx command, path resolution, and multiple Node.js installations.

✨ Features

• Diagnostic tools to identify Node.js installations.
• Installation scripts to avoid common pitfalls.
• Configuration templates using absolute paths.
• Troubleshooting guides to resolve the "Unable to connect to MCP server" error.
• Solutions for NVM and Node.js path issues.

🚀 Quick Start

1. Clone this repository.
2. Run find-nodejs.bat to identify your Node.js installations.
3. If you have multiple installations, run cleanup-nodejs.bat.
4. Run install-mcp.bat to install your chosen MCP server.
5. Follow the displayed configuration instructions.

📚 Documentation

• Installation Guide
• Troubleshooting Guide
• MCP Server Reference
• Configuration Templates

💻 Usage Examples

Basic Usage

Common issues and solutions on Windows:

NPX Connection Failure

The most common issue on Windows is the inability to connect to the MCP server when using the npx command. This is due to the way Claude Desktop launches child processes on Windows.

Solution: Use a direct node execution command with an absolute path, for example:

{
  "mcpServers": {
    "server-name": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": [
        "C:\\Users\\Username\\AppData\\Roaming\\npm\\node_modules\\@modelcontextprotocol\\server-name\\dist\\index.js",
        "parameter1", "parameter2"
      ],
      "env": {
        "APPDATA": "C:\\Users\\Username\\AppData\\Roaming\\",
        "PATH": "C:\\Program Files\\nodejs",
        "NODE_PATH": "C:\\Users\\Username\\AppData\\Roaming\\npm\\node_modules"
      }
    }
  }
}

Multiple Node.js Installations

Having multiple Node.js installations (especially when using NVM) can lead to path resolution issues.

Solution: Use a standard Node.js installation in the default location and specify an absolute path.

Task Manager Restart Requirement

Simply closing and reopening Claude Desktop often does not fully reload the configuration.

Solution: Terminate all Claude Desktop processes in the Task Manager before restarting.

📦 Installation

• find-nodejs.bat - Identify all Node.js installations on the system.
• cleanup-nodejs.bat - Clean up the npm cache and fix common installation issues.
• install-mcp.bat - Globally install the MCP server with the correct path.
• run-server.bat - Test and run the MCP server outside of Claude Desktop.

🤝 Contribution

Contributions are welcome! Please feel free to submit pull requests.

📄 License

MIT License

🙏 Acknowledgments

• The Model Context Protocol team.
• Contributors to MCP Server GitHub Issue #40.