Skip to content
Back to search

mcp-remote-macos-use

The only general AI agent that does NOT requires extra API key, giving you full control on your local and remote MacOs from Claude Desktop App

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/baryhuang--mcp-remote-macos-use/badge.svg)](/listings/baryhuang--mcp-remote-macos-use)

HTML

<a href="/listings/baryhuang--mcp-remote-macos-use"><img src="/api/listings/baryhuang--mcp-remote-macos-use/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

- [Enable Screen Sharing on MacOs](https://support.apple.com/guide/remote-desktop/set-up-a-computer-running-vnc-software-apdbed09830/mac) **If you rent a mac from macstadium.com, you can skip this step** - [Connect to your remote MacOs](https://support.apple.com/guide/mac-help/share-the-screen-of-another-mac-mh14066/mac) - [Install Docker Desktop for local Mac](https://docs.docker.com/desktop/setup/install/mac-install/) - [Add this MCP server to Claude Desktop](https://modelcontextprotocol.io/quickstart/user) 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"
      ]
    }
  }
}

WebRTC Support via LiveKit

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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 192 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # MCP Server - Remote MacOs Use
  2. **The first open-source MCP server that enables AI to fully control remote macOS systems.**
  3. **A direct alternative to OpenAI Operator, optimized specifically for autonomous AI agents with complete desktop capabilities, requiring no additional software installation.**
  4. [![Docker Pulls](https://img.shields.io/docker/pulls/buryhuang/mcp-remote-macos-use)](https://hub.docker.com/r/buryhuang/mcp-remote-macos-use)
  5. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
  6. **Showcases**
  7. - Research Twitter and Post Twitter(https://www.youtube.com/watch?v=--QHz2jcvcs)
  8. <img width="400" alt="image" src="https://github.com/user-attachments/assets/bfe6e354-3d59-4d08-855b-2eecdaaeb46f" />
  9. - Use CapCut to create short highlight video(https://www.youtube.com/watch?v=RKAqiNoU8ec)
  10. <img width="400" alt="image" src="https://github.com/user-attachments/assets/3b4d07c5-cd25-4dae-b9a1-a373bf7492aa" />
  11. - AI Recruiter: Automated candidate information collection, qualifying applications and sending screening sessions using Mail App
  12. - AI Marketing Intern: LinkedIn engagement - automated following, liking, and commenting with relevant users
  13. - AI Marketing Intern: Twitter engagement - automated following, liking, and commenting with relevant users
  14. ## To-Do List (Prioritized)
  15. 1. **Performance Optimization** - Match speed of Ubuntu desktop alternatives
  16. 2. **Apple Scripts Generation** - Reduce execution time while maintaining flexibility
  17. 3. **VNC Cursor Visibility** - Improve debugging and demo experience
  18. *We welcome contributions!*
  19. ## Features
  20. * **No Extra API Costs**: Free screen processing with your existing Claude Pro plan
  21. * **Minimal Setup**: Just enable Screen Sharing on the target Mac – no additional software needed
  22. * **Universal Compatibility**: Works with all macOS versions, current and future
  23. ## Why We Built This
  24. ### Native macOS Experience Without Compromise
  25. 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.
  26. ### Open Architecture By Design
  27. * **Universal LLM Compatibility**: Work with any MCP Client of your choice
  28. * **Model Flexibility**: Seamlessly integrate with OpenAI, Anthropic, or any other LLM provider
  29. * **Future-Proof Integration**: Designed to evolve with the MCP ecosystem
  30. ### Effortless Deployment
  31. * **Zero Setup on Target Machines**: No background applications or agents needed on macOS
  32. * **Screen Sharing is All You Need**: Control any Mac with Screen Sharing enabled
  33. * **Eliminate Backend Complexity**: Unlike other solutions that require running Python applications or background services
  34. ### Streamlined Bootstrap Process
  35. * **Leverage Claude Desktop's Polished UI**: No need for developer-style Python interfaces
  36. * **Intuitive User Experience**: Interact with your AI-controlled Mac through a familiar, user-friendly interface
  37. * **Instant Productivity**: Start working immediately without configuration hassles
  38. ## Architecture
  39. <img width="912" alt="remote_macos_use_system_architecture" src="https://github.com/user-attachments/assets/75ece060-90e2-4ad3-bb52-2c69427001dd" />
  40. ## Installation
  41. - [Enable Screen Sharing on MacOs](https://support.apple.com/guide/remote-desktop/set-up-a-computer-running-vnc-software-apdbed09830/mac) **If you rent a mac from macstadium.com, you can skip this step**
  42. - [Connect to your remote MacOs](https://support.apple.com/guide/mac-help/share-the-screen-of-another-mac-mh14066/mac)
  43. - [Install Docker Desktop for local Mac](https://docs.docker.com/desktop/setup/install/mac-install/)
  44. - [Add this MCP server to Claude Desktop](https://modelcontextprotocol.io/quickstart/user)
  45. You can configure Claude Desktop to use the Docker image by adding the following to your Claude configuration:
  46. ```json
  47. {
  48. "mcpServers": {
  49. "remote-macos-use": {
  50. "command": "docker",
  51. "args": [
  52. "run",
  53. "-i",
  54. "-e",
  55. "MACOS_USERNAME=your_macos_username",
  56. "-e",
  57. "MACOS_PASSWORD=your_macos_password",
  58. "-e",
  59. "MACOS_HOST=your_macos_hostname_or_ip",
  60. "--rm",
  61. "buryhuang/mcp-remote-macos-use:latest"
  62. ]
  63. }
  64. }
  65. }
  66. ```
  67. ### WebRTC Support via LiveKit
  68. This server now includes WebRTC support through LiveKit integration, enabling:
  69. - Low-latency real-time screen sharing
  70. - Improved performance and responsiveness
  71. - Better network efficiency compared to traditional VNC
  72. - Automatic quality adaptation based on network conditions
  73. To use WebRTC features, you'll need to:
  74. 1. Set up a LiveKit server or use LiveKit Cloud
  75. 2. Configure the LiveKit environment variables as shown in the configuration example above
  76. ## Developer Instruction
  77. ### Clone the repo
  78. ```bash
  79. # Clone the repository
  80. git clone https://github.com/yourusername/mcp-remote-macos-use.git
  81. cd mcp-remote-macos-use
  82. ```
  83. ### Building the Docker Image
  84. ```bash
  85. # Build the Docker image
  86. docker build -t mcp-remote-macos-use .
  87. ```
  88. ## Cross-Platform Publishing
  89. To publish the Docker image for multiple platforms, you can use the `docker buildx` command. Follow these steps:
  90. 1. **Create a new builder instance** (if you haven't already):
  91. ```bash
  92. docker buildx create --use
  93. ```
  94. 2. **Build and push the image for multiple platforms**:
  95. ```bash
  96. docker buildx build --platform linux/amd64,linux/arm64 -t buryhuang/mcp-remote-macos-use:latest --push .
  97. ```
  98. 3. **Verify the image is available for the specified platforms**:
  99. ```bash
  100. docker buildx imagetools inspect buryhuang/mcp-remote-macos-use:latest
  101. ```
  102. ## Usage
  103. The server provides Remote MacOs functionality through MCP tools.
  104. ### Tools Specifications
  105. The server provides the following tools for remote macOS control:
  106. #### remote_macos_get_screen
  107. Connect to a remote macOS machine and get a screenshot of the remote desktop. Uses environment variables for connection details.
  108. #### remote_macos_send_keys
  109. Send keyboard input to a remote macOS machine. Uses environment variables for connection details.
  110. #### remote_macos_mouse_move
  111. Move the mouse cursor to specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.
  112. #### remote_macos_mouse_click
  113. Perform a mouse click at specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.
  114. #### remote_macos_mouse_double_click
  115. Perform a mouse double-click at specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.
  116. #### remote_macos_mouse_scroll
  117. Perform a mouse scroll at specified coordinates on a remote macOS machine, with automatic coordinate scaling. Uses environment variables for connection details.
  118. #### remote_macos_open_application
  119. Opens/activates an application and returns its PID for further interactions.
  120. #### remote_macos_mouse_drag_n_drop
  121. Perform a mouse drag operation from start point and drop to end point on a remote macOS machine, with automatic coordinate scaling.
  122. All tools use the environment variables configured during setup instead of requiring connection parameters.
  123. ## Limitations
  124. - **Authentication Support**:
  125. - Only Apple Authentication (protocol 30) is supported
  126. ## Security Note
  127. https://support.apple.com/guide/remote-desktop/encrypt-network-data-apdfe8e386b/mac
  128. https://cafbit.com/post/apple_remote_desktop_quirks/
  129. 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.
  130. Here's the information converted to a markdown table:
  131. | macOS version running Remote Desktop | macOS client version | Authentication | Control and Observe | Copy items or install package | All other tasks | Protocol Version |
  132. |--------------------------------------|----------------------|----------------|---------------------|-------------------------------|----------------|----------------|
  133. | macOS 13 | macOS 13 | 2048-bit RSA host keys | 2048-bit RSA host keys | 2048-bit RSA host keys to authenticate, then 128-bit AES | 2048-bit RSA host keys | 36 |
  134. | macOS 13 | macOS 10.12 | Secure Remote Password (SRP) protocol for local only. Diffie-Hellman (DH) if bound to LDAP or macOS server is version 10.11 or earlier | SRP or DH,128-bit AES | SRP or DH to authenticate, then 128-bit AES | 2048-bit RSA host keys | 35 |
  135. | macOS 11 to macOS 12 | macOS 10.12 to macOS 13 | Secure Remote Password (SRP) protocol for local only, Diffie-Hellman if bound to LDAP | SRP or DH 1024-bit, 128-bit AES | 2048-bit RSA host keys macOS 13 to macOS 10.13 | 2048-bit RSA host keys macOS 10.13 or later | 33 |
  136. | macOS 11 to macOS 12 | OS X 10.11 or earlier | DH 1024-bit | DH 1024-bit, 128-bit AES | Diffie-Hellman Key agreement protocol with a 512-bit prime | Diffie-Hellman Key agreement protocol with a 512-bit prime | 30 |
  137. 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.
  138. ## License
  139. See the LICENSE file for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.