The first open-source MCP server that enables AI to fully control remote macOS systems.

A direct alternative to OpenAI Operator, optimized specifically for autonomous AI agents with complete desktop capabilities, requiring no additional software installation.

Showcases

• Research Twitter and Post Twitter(https://www.youtube.com/watch?v=--QHz2jcvcs)

• Use CapCut to create short highlight video(https://www.youtube.com/watch?v=RKAqiNoU8ec)

• AI Recruiter: Automated candidate information collection, qualifying applications and sending screening sessions using Mail App
• AI Marketing Intern: LinkedIn engagement - automated following, liking, and commenting with relevant users
• AI Marketing Intern: Twitter engagement - automated following, liking, and commenting with relevant users

1. Performance Optimization - Match speed of Ubuntu desktop alternatives
2. Apple Scripts Generation - Reduce execution time while maintaining flexibility
3. VNC Cursor Visibility - Improve debugging and demo experience

We welcome contributions!

• No Extra API Costs: Free screen processing with your existing Claude Pro plan
• Minimal Setup: Just enable Screen Sharing on the target Mac – no additional software needed
• Universal Compatibility: Works with all macOS versions, current and future

The macOS native ecosystem remains unmatched in user experience today and will continue to be the gold standard for years to come. This is where human capabilities truly thrive, and now your AI can operate in this environment with the same fluency.

• Universal LLM Compatibility: Work with any MCP Client of your choice
• Model Flexibility: Seamlessly integrate with OpenAI, Anthropic, or any other LLM provider
• Future-Proof Integration: Designed to evolve with the MCP ecosystem

• Zero Setup on Target Machines: No background applications or agents needed on macOS
• Screen Sharing is All You Need: Control any Mac with Screen Sharing enabled
• Eliminate Backend Complexity: Unlike other solutions that require running Python applications or background services

• Leverage Claude Desktop's Polished UI: No need for developer-style Python interfaces
• Intuitive User Experience: Interact with your AI-controlled Mac through a familiar, user-friendly interface
• Instant Productivity: Start working immediately without configuration hassles

• Enable Screen Sharing on MacOs If you rent a mac from macstadium.com, you can skip this step
• Connect to your remote MacOs
• Install Docker Desktop for local Mac
• Add this MCP server to Claude Desktop You can configure Claude Desktop to use the Docker image by adding the following to your Claude configuration:

{
  "mcpServers": {
    "remote-macos-use": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "-e",
        "MACOS_USERNAME=your_macos_username",
        "-e",
        "MACOS_PASSWORD=your_macos_password",
        "-e",
        "MACOS_HOST=your_macos_hostname_or_ip",
        "--rm",
        "buryhuang/mcp-remote-macos-use:latest"
      ]
    }
  }
}

This server now includes WebRTC support through LiveKit integration, enabling:

• Low-latency real-time screen sharing
• Improved performance and responsiveness
• Better network efficiency compared to traditional VNC
• Automatic quality adaptation based on network conditions

To use WebRTC features, you'll need to:

1. Set up a LiveKit server or use LiveKit Cloud
2. Configure the LiveKit environment variables as shown in the configuration example above

# Clone the repository
git clone https://github.com/yourusername/mcp-remote-macos-use.git
cd mcp-remote-macos-use

# Build the Docker image
docker build -t mcp-remote-macos-use .

To publish the Docker image for multiple platforms, you can use the docker buildx command. Follow these steps:

1. Create a new builder instance (if you haven't already):

   docker buildx create --use

2. Build and push the image for multiple platforms:

   docker buildx build --platform linux/amd64,linux/arm64 -t buryhuang/mcp-remote-macos-use:latest --push .

3. Verify the image is available for the specified platforms:

   docker buildx imagetools inspect buryhuang/mcp-remote-macos-use:latest

The server provides Remote MacOs functionality through MCP tools.

The server provides the following tools for remote macOS control:

Connect to a remote macOS machine and get a screenshot of the remote desktop. Uses environment variables for connection details.

Send keyboard input to a remote macOS machine. Uses environment variables for connection details.

Move the mouse cursor to specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.

Perform a mouse click at specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.

Perform a mouse double-click at specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.

Perform a mouse scroll at specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.

Opens/activates an application and returns its PID for further interactions.

Perform a mouse drag operation from start point and drop to end point on a remote macOS machine, with automatic coordinate scaling.

All tools use the environment variables configured during setup instead of requiring connection parameters.

• Authentication Support:
  • Only Apple Authentication (protocol 30) is supported

https://support.apple.com/guide/remote-desktop/encrypt-network-data-apdfe8e386b/mac https://cafbit.com/post/apple_remote_desktop_quirks/

We only support protocol 30, which uses the Diffie-Hellman key agreement protocol with a 512-bit prime. This protocol is used by macOS 11 to macOS 12 when communicating with OS X 10.11 or earlier clients.

Here's the information converted to a markdown table:

Always use secure, authenticated connections when accessing remote remote MacOs machines. This tool should only be used with servers you trust and have permission to access.

See the LICENSE file for details.