simulator-use MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

      const child = spawn("xcrun", ["simctl", "io", device.udid, "recordVideo", "--codec=h264", "--force", file], { detached: true, stdio: "ignore" });

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    execFile(file, args, { timeout: options.timeoutMs ?? 30_000, maxBuffer: options.maxBytes ?? 64 * 1024 * 1024, encoding: "utf8", ...(options.env ? { env: options.env } : {}) }, (error, stdout, stderr) => {

    let process = Process()

import { createReadStream, lstatSync, readdirSync, realpathSync, type Stats } from "node:fs";

    const s = document.createElement("span"); s.className = "ln"; s.innerHTML = html;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add simulator-use -- npx -y simulator-use

{
  "mcpServers": {
    "simulator-use": {
      "command": "npx",
      "args": [
        "-y",
        "simulator-use"
      ]
    }
  }
}

[mcp_servers.simulator-use]
command = "npx"
args = ["-y", "simulator-use"]

{
  "mcpServers": {
    "simulator-use": {
      "command": "npx",
      "args": [
        "-y",
        "simulator-use"
      ]
    }
  }
}

{
  "servers": {
    "simulator-use": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "simulator-use"
      ]
    }
  }
}