# Runtime Cloud [Health: Active]

**Category:** 👨‍💻 Code Execution  
**Repository:** https://github.com/withruntime/runtime  
**GitHub Stars:** 2  
**npm Downloads (last month):** 26809  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/runtime-cloud-2

## Description
Linux microVM sandboxes for AI agents: run commands, files, processes, pause and wake.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "runtime-cloud": {
    "command": "npx",
    "args": ["-y","withruntime"]
  }
}
```

## Documentation

## What Runtime Cloud does

Runtime Cloud connects MCP-compatible agents to isolated Runtime sandboxes. Each sandbox runs as a Firecracker microVM with its own Linux kernel, giving agents an environment for command execution and related runtime operations.

The MCP interface exposes Runtime product capabilities as tools. These cover running commands, working with files, controlling processes, and changing sandbox state by pausing or waking it. A typical use case is an AI coding or automation agent that needs to execute code without using the host machine directly.

## How it works

The local MCP server is provided by the `withruntime` npm package. An MCP client starts it with `npx -y withruntime mcp`, and the server initially provides `runtime_connect`. The agent uses that tool to begin authorization; Runtime presents a link and code, and the user approves “Connect agent” in a browser. Once connected, the Runtime tools become available.

Machines already authenticated with `npx withruntime login` can skip the first-time connection flow. For automated environments, the client can use the `RUNTIME_API_KEY` environment variable instead of interactive browser approval.

Clients that support MCP Streamable HTTP can connect directly to `https://api.withruntime.com/mcp`. Runtime is also listed in the official MCP Registry as `com.withruntime/runtime`.

## Setup and configuration

The MCP server requires Node.js 22.12 or later. Install the package through npm, or let `npx` fetch it when the client starts the server.

For Claude Code, run:

```bash
claude mcp add --scope user runtime -- npx -y withruntime mcp
```

Clients using JSON-based stdio configuration can use:

```json
{
  "mcpServers": {
    "runtime": {
      "command": "npx",
      "args": ["-y", "withruntime", "mcp"]
    }
  }
}
```

Use `npx withruntime login` for an interactive machine-level connection. Set `RUNTIME_API_KEY` in CI or other noninteractive environments. The MCP server itself does not require an API key when browser-based connection is available.

## Tools and capabilities

- Connect an agent to Runtime with `runtime_connect`.
- Run commands inside Linux microVM sandboxes.
- Read and work with sandbox files.
- Manage processes running in a sandbox.
- Pause and wake sandboxes.
- Expose Runtime functionality through local stdio or Streamable HTTP MCP connections.

## Limitations and notes

The local server depends on Node.js 22.12 or newer. Browser authorization is interactive unless the machine has already been connected or an API key is supplied. Sandbox execution uses Runtime's hosted Firecracker microVM environment rather than the local operating system.

_Full upstream README: https://allmcps.com/mcp/runtime-cloud-2/readme_

