simular-box

Give Hermes a computer of its own: box is a cloud Linux desktop with Chrome and a shell that the agent drives over MCP, around the clock, while your own machine stays free. Agent Plugins v1 package (plugin.json + mcp.json + skills/), configuration only, no code: one remote MCP server (https://mcp.box.simular.ai/mcp, streamable HTTP) and one skill. Needs a box personal key from box.simular.ai/keys, set in Settings > Plugins or as MCP_BOX_API_KEY in the profile .env. Disclosure — every tool call and the MCP_BOX_API_KEY go to mcp.box.simular.ai (Simular); the agent can run shell commands, read, write and delete files, browse sites, and hibernate, save, upgrade or delete the user's box on Simular's cloud computer; the package marks the box server trust: untrusted, so Hermes asks before each tool that is not read-only until the user approves it; box use counts against the account's box plan; the user can watch and take over the box at box.simular.ai/box. Nothing runs or is stored on the local machine.

SimularToolsv0.2.0Updated 5 hours ago

About

box for Hermes Agent

Give your Hermes agent a computer of its own: a cloud Linux desktop with Chrome and a shell that it drives over MCP, around the clock.

This folder is a portable Agent Plugins v1 package (plugin.json, mcp.json, skills/). It reaches box with a personal key, which suits a Hermes agent running on a server with no browser.

Create a personal key at https://box.simular.ai/keys (name it "hermes"). It is shown once.
Add it to ~/.hermes/.env:
```
MCP_BOX_API_KEY=cb_your_key
```
MCP_BOX_API_KEY is the name Hermes's own hermes mcp add --auth header uses, and the same one npx @simular-ai/box connect --client hermes --auth key writes, so one key serves either install.
Install the plugin into your profile's plugin folder, enable it, and restart the gateway so it picks up the key:
```
git clone https://github.com/simular-ai/box-plugin /tmp/box-plugin
cp -R /tmp/box-plugin/hermes ~/.hermes/plugins/simular-box     # per profile: ~/.hermes/profiles/<name>/plugins/simular-box
hermes plugins enable simular-box
hermes gateway restart
```
hermes plugins install takes a catalog name, a Git URL or owner/repo, not a folder inside a repo, so until box is in the Hermes plugin catalog the folder is copied by hand. Check it with hermes plugins validate ~/.hermes/plugins/simular-box. The plugin is named simular-box so it isn't confused with Box, the cloud-files company. box's tools show up from the box server, and the box skill tells the agent how to use them.

Hermes asks you the first time the agent uses each box tool that can change something (clicking, typing, running a command, writing or deleting a file). Answer Always and it won't ask for that tool again; screenshots and other read-only tools never ask. A scheduled or unattended run can't answer, so approve the tools once in a chat first.

If you change the key later, run hermes gateway restart: a running gateway keeps the old value and parks the server.

To update, copy the folder again the same way and restart the gateway. Version 0.2.0 renamed the plugin from box to simular-box: if you installed an earlier version, run hermes plugins disable box, delete ~/.hermes/plugins/box, then install as above. Version 0.1.1 moved box to https://mcp.box.simular.ai/mcp.

On a desktop with a browser, you can sign in instead of using a key: hermes mcp add box --url https://mcp.box.simular.ai/mcp --auth oauth, then hermes mcp login box. A server you add this way overrides the plugin's entry of the same name. On a server, prefer the key: when an OAuth refresh token expires, Hermes parks the server until someone signs in again by hand.

Watch the box live, and take over when needed, at https://box.simular.ai/box.

README from the reviewed commit 62cc5dd; it updates when the author re-pins.

More by Simular

2 plugins by Simular in the catalog.

Simularsimular-saiGive Hermes a computer: hand tasks that need a screen (web apps behind a login, admin consoles, desktop software, forms with no import) to Sai, Simular's computer-use agent, which does them on a cloud computer Simular hosts and reports back in text. Agent Plugins v1 package (plugin.json + mcp.json + skills/), configuration only; the MCP server runs as npx @simular-ai/sai-mcp@0.4.0 over stdio, so Node.js 22.12+ and npm are required. Needs a Sai API key (from platform.simular.ai), set in Settings > Plugins or as SAI_API_KEY in the profile .env. Disclosure — Runs the npm package @simular-ai/sai-mcp@0.4.0 through npx; every task, its results and the SAI_API_KEY go to api.simular.ai and spend the account's Sai credit or free computer time; the agent can upload any local file it chooses (up to 25 MB) to Simular with sai_upload, run code on the Simular cloud computer (sai_control_exec), and approve Sai's own permission requests, without a Hermes prompt; a local task view is served on 127.0.0.1 with a per-run token, and sai_live_link returns a link that lets whoever holds it control the cloud computer until it expires.Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section