view-sim MCP Server

What the code does

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

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.

vm.runInNewContext(readFileSync(path.join(EXTENSION_DIR, "shared/devices.js"), "utf8"), catalog);

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  const file = path.join(storeDir, name);

        document.write(`<script src="../extension/shared/devices.js?v=${version}"><\/script><script src="../extension/simulator/simulator.js?v=${version}"><\/script>`);

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 view-sim -- npx -y view-sim-mcp

{
  "mcpServers": {
    "view-sim": {
      "command": "npx",
      "args": [
        "-y",
        "view-sim-mcp"
      ]
    }
  }
}

[mcp_servers.view-sim]
command = "npx"
args = ["-y", "view-sim-mcp"]

{
  "mcpServers": {
    "view-sim": {
      "command": "npx",
      "args": [
        "-y",
        "view-sim-mcp"
      ]
    }
  }
}

{
  "servers": {
    "view-sim": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "view-sim-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: VIEW_SIM_EXTENSION_IDS (Comma-separated extension ids allowed to connect to the bridge (Chrome id and/or view-sim@itelo). Unset allows any extension).