Cursor IDE

🚀 Cursor MCP - Desktop Application Integrated with Claude Desktop

An implementation of the Model Context Protocol (MCP) that enables seamless integration between Claude AI and desktop applications through the Cursor IDE. This tool serves as a bridge between Claude's capabilities and desktop software, enhancing AI-driven development workflows.

🚀 Quick Start (Windows)

Prerequisites

• Node.js v18 or higher
• Cursor IDE
• Windows 10 or higher

Installation

# Global installation
npm install -g mcp-cursor

# Or local installation
git clone https://github.com/yourusername/cursor-mcp.git
cd cursor-mcp
npm install

Configuration

• Create a .env file in the project root directory:

# Example Windows path
DEFAULT_WORKSPACE_PATH=C:/Users/YourUsername/Documents/cursor-workspaces

Add to Claude's MCP Configuration

Add the following content 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 globally installed
mcp-cursor

# If locally installed
npm start

✨ Features

• Real-time AI-assisted development workflows
• Context-aware code suggestions and autocompletion
• Seamless integration with Cursor IDE
• Windows automation for increased productivity

📚 Documentation

Set Up a Local Development Environment

1. Clone and install:

git clone https://github.com/yourusername/cursor-mcp.git
cd cursor-mcp
npm install

2. Create environment configuration:

cp .env.example .env

Edit the .env file and set your workspace path:

DEFAULT_WORKSPACE_PATH=C:/Users/YourUsername/Documents/cursor-workspaces

3. Build and run:

# Development mode with hot reloading
npm run dev

# Production mode
npm run build
npm start

Troubleshooting

Window Detection Issues

• Ensure that the Cursor IDE is running.
• Try restarting the MCP server.
• Check if the workspace path is correct.

Permission Issues

• Run the terminal as an administrator for the initial setup.
• Ensure that the workspace directory has appropriate file permissions.

Node Version Issues

• Use nvm to switch to Node.js v18 or higher:

nvm install 18
nvm use 18

🔧 Technical Details

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 TypeScript
• npm start - Run the production server
• npm run dev - Start the development server with hot reloading

🤝 Contribution Guidelines

1. Fork and clone the repository.
2. Create a feature branch (git checkout -b feature/amazing-feature).
3. Commit your changes (git commit -m 'Add feature').
4. Push to the branch (git push origin feature/amazing-feature).
5. Open a Pull Request.

📄 License

MIT License - See the LICENSE file for details.

🛠️ Support

If you have any issues:

• Open an issue in the GitHub repository.
• Join our Discord community.
• Check the FAQ.