Cursor MCP - Claude Desktop Integration
A Model Context Protocol (MCP) implementation that enables seamless integration between Claude AI and desktop applications through Cursor IDE. This tool serves as a bridge between Claude's capabilities and desktop software, allowing for enhanced AI-powered development workflows.
Quick Start (Windows)
Installing via Smithery
To install Cursor for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install cursor-mcp-tool --client claude
Installing Manually
-
Prerequisites
- Node.js v18 or higher
- Cursor IDE
- Windows 10 or higher
-
Installation
# Install globally npm install -g mcp-cursor # Or install locally git clone https://github.com/yourusername/cursor-mcp.git cd cursor-mcp npm install -
Configuration
- Create a
.envfile in your project root:# Windows path example DEFAULT_WORKSPACE_PATH=C:/Users/YourUsername/Documents/cursor-workspaces
- Create a
-
Add to Claude's MCP Configuration Add the following to your Claude configuration:
{ "name": "cursor", "type": "mcp", "config": { "server": "https://glama.ai/mcp/servers/4fg1gxbcex", "capabilities": ["cursor_control", "window_management"] } } -
Start the Server
# If installed globally mcp-cursor # If installed locally npm start
Features
- Real-time AI assistance in your development workflow
- Context-aware code suggestions and completions
- Seamless integration with Cursor IDE
- Windows automation for enhanced productivity
Detailed Setup
Local Development Setup
-
Clone and install:
git clone https://github.com/yourusername/cursor-mcp.git cd cursor-mcp npm install -
Create environment config:
cp .env.example .envEdit
.envand set your workspace path:DEFAULT_WORKSPACE_PATH=C:/Users/YourUsername/Documents/cursor-workspaces -
Build and run:
# Development mode with hot reload npm run dev # Production mode npm run build npm start
Troubleshooting
-
Window Detection Issues
- Ensure Cursor IDE is running
- Try restarting the MCP server
- Check if your workspace path is correct
-
Permission Issues
- Run terminal as administrator for first-time setup
- Ensure proper file permissions in workspace directory
-
Node Version Issues
- Use
nvmto switch to Node.js v18 or higher:nvm install 18 nvm use 18
- Use
Project Structure
cursor-mcp/
├── src/ # Source code
│ ├── services/ # Core services
│ ├── handlers/ # Event handlers
│ └── types/ # TypeScript definitions
├── build/ # Compiled JavaScript
└── .env # Environment configuration
Scripts
npm run build- Compile TypeScriptnpm start- Run production servernpm run dev- Start development server with hot-reload
Contributing
- Fork the repository
- Create feature branch (
git checkout -b feature/amazing-feature) - Commit changes (
git commit -m 'Add feature') - Push to branch (
git push origin feature/amazing-feature) - Open a Pull Request
License
MIT License - see LICENSE file for details.
Running evals
The evals package loads an mcp client that then runs the index.ts file, so there is no need to rebuild between tests. You can load environment variables by prefixing the npx command. Full documentation can be found here.
OPENAI_API_KEY=your-key npx mcp-eval src/evals/evals.ts src/tools/cursor-tools.ts
Support
For support:
- Open an issue in the GitHub repository
- Join our Discord community
- Check the FAQ