Remote Coding Runtime
Provides Git repository inspection tools (git_status and git_diff) for workspaces, allowing clients to review repository status and changes with bounded output.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Remote Coding RuntimeCheck the git state in workspace zero and show uncommitted changes."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Runmesh is provided under the PolyForm Noncommercial License 1.0.0. Commercial use requires separate written authorization. SeeCommercial License.
See Runmesh in 60 seconds
Runmesh connects ChatGPT, Claude, Cursor and other MCP-compatible clients to approved Linux, macOS or Windows computers. Machines may be behind NAT or on a private network; the AI can use only the content and permissions you grant.
https://github.com/user-attachments/assets/49488721-4a41-40af-a0a6-5482f71b937c
Download MP4 · Overview and subtitles
Related MCP server: cloud-to-local
What you can do
Let an AI inspect files, propose edits or run approved commands in selected workspaces.
Run tests, builds and other long-running work while following progress in the control panel.
Connect MCPs and install Skills in one place, then share them with several AI clients.
Give each client shared content only, or add access to approved computers.
A Runner is installed on each computer that performs work. Administrators choose its workspaces and the capabilities each client may use. The default restricted service-account mode is dedicated_user; computer permissions start with Read selected.
Get started
If an administrator has given you a Runmesh address:
Paste the complete address into an MCP-compatible AI client.
Refresh the client's Runmesh connection to load the shared MCPs and Skills.
When computer access is available, choose the intended computer and open an approved workspace.
Start by viewing files; use edit, command or job actions only when the client shows that permission.
A Runmesh address is a credential. Store and share it only through a secure channel. See the user guide for the complete workflow.
Administrator quick setup
Deploy the current stable version listed in release status.
Open Runner, add a computer, copy the one-time installation command and run it on that machine.
Add approved workspaces and permissions in the Runner details page.
Open MCP & Skill to connect shared services and install Skills.
Open AI connections, create a connection, choose shared content or computer access, and share the displayed address with its intended user.
Use the relevant page to update, pause, rotate or revoke access.
Installation commands and client addresses are credentials; keep them private. For an existing installation, preserve its credentials and Runner settings and follow the upgrade guide.
Permissions
Permission | Use |
View | Browse files and directories in approved workspaces |
Edit | Apply changes in workspaces that allow writing |
Execute | Run commands on a Runner |
Jobs | Follow or cancel long-running work |
Shared content | Use the instance's enabled MCPs and Skills |
The client, Runner and workspace settings together determine what is available. Administrators can pause shared content, rotate a client address or revoke access at any time.
Operate safely
Share client addresses, installation commands and Runner profiles only with their intended users.
Rotate or revoke credentials as soon as they are exposed.
Use a dedicated account, container or virtual machine for untrusted code.
Review a Skill's source and content before sharing it.
Read the release notes before upgrades and use troubleshooting when a task fails.
Documentation
Report security issues privately through .github/SECURITY.md; use Issues for ordinary problems.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.
Develop, manage, and debug Railway projects, services, and deployments from within agents.
Securely control computers you explicitly pair through files, terminals, processes, screenshots, desktop UI/input, clipboard, browser automation, diagnostics, and document tools.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables remote MCP clients to access local filesystem and shell commands by deploying a Cloudflare Worker relay and a local daemon, providing tools like read/write files, exec commands, git status, etc.320 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables cloud agents to securely operate local machine resources (files, commands, screenshots) via standard MCP protocol.MIT
- FlicenseNot gradedqualityBmaintenanceEnables a standard authenticated MCP client to dispatch three controlled operations — command execution and scoped file reads/writes — to a remote lightweight agent through Vercel, with encrypted relaying, atomic writes, and Redis-backed audit logging.-
- AlicenseNot gradedqualityAmaintenanceConnects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.19MIT