computer-use-mcp

💻 A Model Context Protocol server for Claude to control your computer. This is very similar to computer use, but easy to set up and use locally.

Here's Claude Haiku 4.5 changing my desktop background (4x speed):

https://github.com/user-attachments/assets/cd0bc190-52c4-49db-b3bc-4b8a74544789

[!WARNING]

At time of writing, models make frequent mistakes and are vulnerable to prompt injections. As this MCP server gives the model complete control of your computer, this could do a lot of damage. You should therefore treat this like giving a hyperactive toddler access to your computer - you probably want to supervise it closely, and consider only doing this in a sandboxed user account.

Installation

Follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).

Tips

This should just work out of the box.

However, to get best results:

• Use a model good at computer use - I recommend the latest Claude models.
• Use a small, common resolution - 720p works particularly well. On macOS, you can use displayoverride-mac to do this. If you can't use a different resolution, try zooming in to active windows.
• Install and enable the Rango browser extension. This enables keyboard navigation for websites, which is far more reliable than Claude trying to click coordinates. You can bump up the font size setting in Rango to make the hints more visible.

How it works

We implement a near identical computer use tool to Anthropic's official computer use guide, with some more nudging to prefer keyboard shortcuts.

This talks to your computer using nut.js

Contributing

Pull requests are welcomed on GitHub! To get started:

1. Install Git and Node.js

2. Clone the repository

3. Install dependencies with npm install

4. Run npm run test to run tests

5. Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

1. Use npm version to bump the version

2. Run git push --follow-tags to push with tags

3. Wait for GitHub Actions to publish to the NPM registry.