All plugins

dosbox-full-auto

All-in-one solution for controlling DOSBox apps with your agent. Self-contained DOSBox-automation with built-in MCP server, registers in Hermes and exposes 55 tools via the dosbox-full-auto skill such as vision based mouse movement, live process memory reading and more. Disclosure — Downloads the author's prebuilt DOSBox-automation emulator and MCP server binaries (GitHub release, sha256-pinned per tag) into plugin-data and registers them as an MCP server; the emulator exposes an unauthenticated HTTP API on 127.0.0.1:8387 that any local process can use to type into DOS and read/write emulator memory; host folders can be mounted only under the plugin's drives folder and the roots you list as mount_allowed_bases in the emulator's own config; the optional visual check sends screenshots to decision.vllm-sr.ai with a key minted after the user accepts that service's terms.

EternalNoobletAutomationv0.5.0Updated 3 hours ago

About

All-in-one solution for controlling DOSBox apps with your agent. Self-contained DOSBox-automation with built-in MCP server, registers in Hermes and exposes 55 tools via the dosbox-full-auto skill such as vision based mouse movement, live process memory reading and more. Disclosure — Downloads the author's prebuilt DOSBox-automation emulator and MCP server binaries (GitHub release, sha256-pinned per tag) into plugin-data and registers them as an MCP server; the emulator exposes an unauthenticated HTTP API on 127.0.0.1:8387 that any local process can use to type into DOS and read/write emulator memory; host folders can be mounted only under the plugin's drives folder and the roots you list as mount_allowed_bases in the emulator's own config; the optional visual check sends screenshots to decision.vllm-sr.ai with a key minted after the user accepts that service's terms.

dosbox-full-auto

One-directory DOSBox full automation for Hermes Agent (Linux x86_64, Windows x86_64).

https://github.com/user-attachments/assets/fd7eee46-4801-45e0-a56f-bfe11b9b0dc4

Downloads the self-contained release bundle from
dosbox-full-auto
releases, extracts it into the plugin data dir, registers it as the
dosbox-full-auto MCP server on port 8387, and ships the merged driving skill.

Use

hermes plugins install <path-or-git-url>   # from this directory or a pushed repo

In a session:

/dosbox-full-auto status        bundle + MCP entry + VLLM key state
/dosbox-full-auto install       download bundle, register MCP server
/dosbox-full-auto reinstall     force a fresh download
/dosbox-full-auto create-key    mint new VLLM key (1st run shows terms, re-run accepts)
/dosbox-full-auto key-status    show VLLM key status (verifies with API)

Or: hermes dosbox-full-auto status|install|reinstall|create-key|key-status.

After install, tools appear as mcp_dosbox_full_auto__* in the same session
(a new mcp_servers entry is discovered mid-session). Restart only if the
server binary itself was rebuilt.

What it downloads and runs (read this before installing)

Setup (install) fetches ONE native bundle — about 16.5 MB — for the current
platform from the official GitHub Releases of the upstream project
dosbox-full-auto
(tag v1.0.3), verifies its SHA256 against the pinned digest in
src/install.py (PINNED_DIGESTS, the digest GitHub publishes for the asset),
and only then extracts and executes it. Unpinned release tags are refused —
nothing installs unless its checksum is in the table. The bundle contains
native executables (dosbox-full-auto-mcp, dosbox-automation), resources/ (shaders,
fonts, webserver assets) and libiir.so (Linux) / equivalent DLLs (Windows).
Nothing is bundled in the plugin repo itself — this is a setup-time fetch, not
a shipped payload (Hermes catalog rule 17), disclosed here per rule 13:

  • Network: GitHub API + release asset download at install time; Decision API
    (decision.vllm-sr.ai) for visual checks. VLLM API key is never created
    automatically     — only an explicit create-key mints one: the first run shows
    the terms of use (https://decision.vllm-sr.ai/terms), a second run accepts
    (accept_terms: true) and creates via PoW. Key creation respects strict rate
    limits: 5 keys/IP/hour, 20/day (12 min cooldown between creations).
  • Files: writes only under <hermes home>/plugin-data/dosbox-full-auto/
    (binaries, VERSION, plugin_db). No reads outside the plugin's own data and
    the one MCP config entry it registers via hermes mcp add.
  • Processes: registers a local stdio MCP server on port 8387; Hermes spawns
    it on demand and it spawns the emulator as its child. No background
    daemons, no telemetry.
  • Credentials: VLLM_API_KEY read via the Hermes secret scope (get_secret only —
    there is no setter), never stored by the plugin: created ONLY by an explicit
    create-key (terms URL shown before any key is minted; nothing is auto-created),
    which tells the user to persist it via hermes config set or their profile .env;
    sent as bearer token to Decision API only.

Why a bundle, not loose binaries

v1.0.0 shipped loose binaries and aborted twice over: libiir.so.1: cannot open shared object file, then ABORT: RENDER: Error setting fallback shaders. The tarball ships dosbox-full-auto-mcp, dosbox-automation, resources/
(shaders/mapping/fonts/webserver) and _deps/iir1-build/libiir.so* together;
the emulator resolves resources from its cwd (hence --working-dir) and the
launcher sets LD_LIBRARY_PATH from the bundle dir.

Requirements

  • Linux x86_64 or Windows x86_64.
  • VLLM API key is never auto-created — mint it explicitly with /dosbox-full-auto create-key (first run shows https://decision.vllm-sr.ai/terms, re-run accepts); NOT stored by the plugin (Hermes has no secret-scope setter) — persist it yourself via hermes config set or your profile .env, otherwise every create-key run mints a fresh one. Strict rate limits: 5 keys/IP/hour, 20/day.
  • Ports: MCP on 8387 (the dev pair keeps 8386).

README from the reviewed commit 9ef9456; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section