Claude MCP Get
About
A comprehensive toolkit for installing and configuring Model Context Protocol (MCP) servers on Windows systems
Details
- Author
- PWereh
- Downloads
- 121
- Categories
- AI
Jump to
- Diagnostic tools to identify Node.js installations
- Installation scripts that avoid common pitfalls
- Configuration templates with absolute paths
- Troubleshooting guides for MCP server errors
- Solutions for NVM and Node.js path issues
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:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Claude MCP GetCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Clone the repository, then run find-nodejs.bat to identify Node.js installations, cleanup-nodejs.bat if needed, and install-mcp.bat to install an MCP server. Follow the displayed configuration instructions.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"claude mcp get": {
"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"
}
}
}
}
}
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"
}
}
}
Claude 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
1. Clone this repository
2. Run find-nodejs.bat to identify your Node.js installations
3. Run cleanup-nodejs.bat if you have multiple installations
4. Run install-mcp.bat to install the MCP server of your choice
5. 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
- Installation Guide
- Troubleshooting Guide
- MCP Server Reference
- Configuration Templates
Scripts
- find-nodejs.bat - Identifies all Node.js installations on your system
- cleanup-nodejs.bat - Cleans npm cache and fixes common installation issues
- install-mcp.bat - Installs MCP servers globally with proper paths
- run-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
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
