MCP Server

The isorun package ships an MCP server CLI, isorun-mcp, that any Model Context Protocol client can drive: Claude Desktop, Cursor, Zed, or anything else that speaks MCP. It exposes the canonical Isorun primitives as MCP tools over stdio.

Install

npm install -g isorun @modelcontextprotocol/sdk zod

This puts isorun-mcp on your PATH. (Install locally instead and reference the binary by path if you prefer.)

Tools

Tools take a sandboxId, so the model can create_sandbox once, run several exec calls against that ID, then destroy_sandbox when done.

Wire into Claude Desktop

Add the server to claude_desktop_config.json:

{
  "mcpServers": {
    "isorun": {
      "command": "isorun-mcp",
      "env": {
        "ISORUN_API_KEY": "isorun_live_..."
      }
    }
  }
}

Restart Claude. The model now has isorun:create_sandbox, isorun:exec, isorun:hibernate, and the rest as native tools.

Wire into Cursor

Add to ~/.cursor/mcp.json (or your project's .cursor/mcp.json):

{
  "mcpServers": {
    "isorun": {
      "command": "isorun-mcp",
      "env": { "ISORUN_API_KEY": "isorun_live_..." }
    }
  }
}

Wire into Zed

Add to settings.json:

{
  "context_servers": {
    "isorun": {
      "source": "custom",
      "command": {
        "path": "isorun-mcp",
        "env": { "ISORUN_API_KEY": "isorun_live_..." }
      }
    }
  }
}

Embed the server in your own host

buildServer() returns a configured MCP server without binding it to stdio, so you can compose Isorun's tools with your own inside one process.

import { buildServer } from 'isorun/mcp'
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'

const server = await buildServer()
// register your own tools on `server` here, then:
await server.connect(new StdioServerTransport())

Next steps

• TypeScript SDK, the client the server wraps.
• Create and execute, what create_sandbox and exec do under the hood.
• Lifecycle and hibernation, the hibernate and resume tools.