About Claude MCP Get
Claude MCP Get is a set of scripts, configuration templates, and guides for installing MCP servers with Claude Desktop on Windows. It focuses on resolving connection and path issues involving npx and multiple Node.js installations.
Key features
- 01Detects Node.js installations
- 02Installs MCP servers with scripts
- 03Provides absolute-path configuration templates
- 04Guides troubleshooting of connection errors
- 05Addresses NVM and Node.js path issues
Use cases
- 01Find Node.js installations on Windows
- 02Install an MCP server for Claude Desktop
- 03Configure servers with absolute paths
- 04Diagnose npx connection or path problems
MCP support
Helps Windows users install and configure MCP servers for Claude Desktop; it does not itself expose an MCP server.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEClaude MCP Get
A comprehensive toolkit for installing and configuring Model Context Protocol (MCP) servers with Claude Desktop on Windows systems.
Overview
This repository contains scripts, configurations, and documentation to help Windows users successfully install and use Model Context Protocol (MCP) servers with Claude Desktop. It focuses on overcoming the common issues that prevent MCP connections on Windows, particularly problems with npx commands, path resolution, and multiple Node.js installations.
Key Features
- Diagnostic tools to identify Node.js installations
- Installation scripts that avoid common pitfalls
- Configuration templates with absolute paths
- Troubleshooting guides for "Could not attach to MCP server" errors
- Solutions for NVM and Node.js path issues
Quick Start
- Clone this repository
- Run
find-nodejs.batto identify your Node.js installations - Run
cleanup-nodejs.batif you have multiple installations - Run
install-mcp.batto install the MCP server of your choice - Follow the configuration instructions displayed
Common Windows Issues & Solutions
NPX Connection Failures
The most common issue on Windows is MCP servers failing to connect when using npx commands in claude_desktop_config.json. This is due to how Claude Desktop launches subprocesses on Windows.
Solution: Use direct node execution with absolute paths, like:
{
"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 with NVM) causes path resolution issues.
Solution: Use the standard Node.js installation in the default location and specify absolute paths.
Task Manager Restart Required
Simply closing and reopening Claude Desktop often doesn't fully reload configurations.
Solution: End all Claude Desktop processes in Task Manager before restarting.
Documentation
Scripts
find-nodejs.bat- Identifies all Node.js installations on your systemcleanup-nodejs.bat- Cleans npm cache and fixes common installation issuesinstall-mcp.bat- Installs MCP servers globally with proper pathsrun-server.bat- Runs MCP servers for testing outside Claude Desktop
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License
Acknowledgments
- Model Context Protocol team
- Contributors to the MCP servers GitHub issue #40
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.