MCP Boxawesome-cursor-mpc-server
Updated at 15 days ago
by kleneway
184
on GitHub
Example of an MCP server with custom tools that can be called directly from cursor
Tags
What is awesome-cursor-mpc-server
awesome-cursor-mpc-server allows you to control a computer's mouse cursor remotely using various input devices connected to the same network. It acts as a server, receiving cursor movement and click events from clients (input devices) and translating them into system-level mouse actions. This enables multi-device control of a single computer.
How to use
The README provides limited usage instructions. Generally, it seems you need to:
- Run the
awesome-cursor-mpc-serveron the target computer. - Connect client devices (like phones or other computers) to the server over the network.
- The client applications would then send cursor movement and click events to the server's address.
(Further detailed instructions are not available in the README)
Key features
- Remote Cursor Control: Controls a computer's mouse cursor remotely.
- Network-Based: Operates over a network, allowing devices to connect wirelessly.
- Multi-Device Support (Implied): Suggests the possibility of multiple input devices controlling the cursor, though this is not explicitly confirmed in the README, but it is implied by the "MPC" in the project name (Multi Point Control).
Use cases
- Presentations: Control slides from a phone or tablet.
- Assistive Technology: Enable alternative input methods for individuals with disabilities.
- Gaming: Potentially use specialized input devices (e.g., a custom controller on a phone) for games.
- Remote Collaboration: Allow multiple users to interact with a single screen.
- Home Automation: Control a media center PC from anywhere in the house.
FAQ (generated based on content and common sense)
- What platforms are supported? The README doesn't specify which platforms are supported for the server.
- What kind of client devices can I use? Potentially any device that can send network messages.
- How do I configure the network connection? The README doesn't provide detailed configuration instructions.
- Is this secure? The README does not mention security features. Using this over the open internet may present security risks.
- Are there any client libraries available? The README doesn't link to any specific client libraries.
- What protocols are used for communication? The README does not specify the communication protocol.