Sai by Simular

Give OpenClaw a cloud computer to automate websites and desktop apps.

Install

openclaw plugins install clawhub:simular-sai-claude-plugin

Sai by Simular

Give Claude a computer. This plugin lets Claude Code hand tasks to Sai, Simular's computer-use agent, #1 on OSWorld 2.0. Sai uses apps and websites the way a person does, by seeing the screen, clicking and typing, so Claude can get work done where there is no API: web apps behind a login, admin consoles, desktop software, forms with no import. Sai runs on a cloud computer Simular hosts; the free plan includes one.

Compatibility

The Sai tools run in Claude Code and Cowork through a local stdio MCP server. They do not run in claude.ai chat. See Claude's plugin compatibility documentation.

Install

Sign in at platform.simular.ai and create an API key under API Keys.
Install the plugin from /plugin in Claude Code (it is listed as Sai by Simular, with plugin ID simular-sai). When asked, paste the API key. It is stored in Claude Code's secure storage, not in a settings file.

Then ask Claude something like: "Use Sai to open Notepad on my cloud computer, type Hello from Sai, and tell me the window title."

Install in OpenClaw

OpenClaw loads this repository as a Claude bundle (skill and MCP server). It does not support Claude Code's API key prompt, so the key comes from the SAI_API_KEY environment variable instead.

Install the bundle:

bash

openclaw plugins install git:github.com/simular-ai/sai-claude-plugin

Put your API key where the OpenClaw Gateway can read it, for example in ~/.openclaw/.env:
bash
```
SAI_API_KEY=sapi_YOUR_KEY
```
Point the sai MCP server at that variable. A server in your OpenClaw config replaces the bundle's server of the same name:
bash
```
openclaw mcp set sai '{"command":"npx","args":["-y","@simular-ai/sai-mcp@0.4.0"],"env":{"SAI_API_KEY":"${SAI_API_KEY}"}}'
```
Keep the single quotes so your shell does not expand ${SAI_API_KEY}; OpenClaw resolves it when it loads the config. Without this step the server starts without a usable key and every call is rejected.

Check it with openclaw plugins inspect sai and openclaw mcp status.

Install in Hermes

See hermes/README.md. The hermes/ folder is a portable Agent Plugins package with the same skill and MCP server.

What it contains

MCP server sai: the open-source @simular-ai/sai-mcp package, pinned to an exact version in package-lock.json (with registry hashes) and started with node. Claude Code installs it when it installs the plugin, with install scripts off. Tools: start a task, wait for it, answer permission requests, stop it, upload a file, list computers and models, and hand the screen to a person with a link.
Skill sai (/simular-sai:sai): tells Claude when to hand a task to Sai and how to run it to the end, including permission requests and sign-in links.

Each host reads its own files from the same repository:

Host	Manifest	MCP config	API key from
Claude Code	`.claude-plugin/plugin.json`	`.mcp.json`	the install prompt (`userConfig`)
OpenClaw	`.claude-plugin/plugin.json`	`.mcp.json`, overridden in your OpenClaw config	`SAI_API_KEY`
Hermes	`hermes/plugin.json`	`hermes/mcp.json`	Settings > Plugins or `SAI_API_KEY`

All three run the same pinned @simular-ai/sai-mcp version and the same skill (hermes/skills/sai/SKILL.md is a copy of skills/sai/SKILL.md). When you bump the version or edit the skill, change it in package.json, hermes/mcp.json, both skill files and the OpenClaw command above.

Data and network

The MCP server sends your tasks, the files you ask it to upload and your API key to the Sai API at https://api.simular.ai, which runs the task on your Sai cloud computer and returns its text result. Usage is billed to your Sai account.
It serves a live view of the task on 127.0.0.1 on your own computer, linked as watch_url. Your API key never reaches the browser.
Claude Code downloads the locked @simular-ai/sai-mcp package and its dependencies from the npm registry when it installs the plugin.
The plugin stores nothing itself and has no hooks.

Directory review notes

The listing uses Sai by Simular to distinguish it from similarly named connectors. Its plugin ID remains simular-sai, so the skill command is still /simular-sai:sai. A name or publisher hold must be cleared by the directory reviewer; changing the display name does not itself grant approval.

The server is launched with node, not npx. Keep both package.json and package-lock.json: together they pin @simular-ai/sai-mcp and its dependency tree. The directory's suggestion to bundle files smaller than 256 KiB is an optional alternative to installing dependencies, not a requirement to delete the lockfile from this package.

The icon field is for the directory listing; Claude Code ignoring it at load time is expected. The scanner's notice that it accepted .claude-plugin/icon.png as an image is informational.

ClawHub listing metadata

ClawHub reads the listing title from package.json.displayName and the summary from package.json.description. Keep those fields user-facing. Its logo must be at assets/icon.png; keep that file identical to .claude-plugin/icon.png when updating the Sai logo.

Publish with clawhub package publish . --family bundle-plugin --bundle-format claude --wait. The release version comes from package.json.version; keep the lockfile and Claude plugin manifest version in sync. Run the same command with --dry-run before publishing to check the title, version, and source attribution.

License

MIT