Hermes integration
Give the Hermes agent persistent AliasMode browser profiles.
AliasMode registers as a local stdio MCP server in the Hermes agent. The agent gets profile lifecycle, browser control, and 31 Playwright page actions on the Windows machine that holds the profiles.
Direct answer
Run aliasmode-mcp setup --yes --client hermes in the AliasMode install directory, restart the agent, and confirm the aliasmode tool list (40 tools on the beta.47 installer).
Set up Hermes
Install AliasMode on Windows
Download the installer, install CloakBrowser, and create at least one profile. Keep the desktop app available; the MCP helper starts it in the background when needed.
Locate the MCP helper
The Windows installer places aliasmode-mcp.exe next to AliasMode.exe, by default in %LOCALAPPDATA%\AliasMode.
Register the server automatically
Run the setup from the install directory. It detects Hermes, removes any older aliasmode registration, and writes the new one.
cd "%LOCALAPPDATA%\AliasMode" aliasmode-mcp setup --yes --client hermesOr register manually
The manual command matches what the setup writes:
hermes mcp add aliasmode --command "%LOCALAPPDATA%\AliasMode\aliasmode-mcp.exe" --args serveRestart the agent
Restart the Hermes agent so the new MCP server loads, then confirm the aliasmode tools appear in the tool list.
Run a browser test
Give the agent a small end-to-end task:
List my AliasMode profiles. Open the profile named Ops headless, load the dashboard URL, and report the page title. Close the browser.
Verify the connection
- The Hermes tool list shows the aliasmode server with its tools loaded.
- The tool list includes aliasmode_profiles_list plus 31 Playwright actions — 40 tools on the beta.47 installer.
- A headless browser opens from a named profile and browser_snapshot returns real page content.
- GET /api/v1/status on 127.0.0.1:50400 responds on the same machine while the desktop app is open.
Troubleshooting
| Symptom | Fix |
|---|---|
| Hermes does not show the aliasmode tools | Rerun aliasmode-mcp setup --yes --client hermes, then restart the agent so the MCP server reloads. Confirm the helper path points inside the AliasMode install directory. |
| Tool calls fail with a runtime readiness error | The helper starts AliasMode in the background and waits briefly. Open the desktop app manually, wait for the dashboard to load, then retry. |
| Playwright tools return a selection error | Open a profile with aliasmode_browser_open or select an open browser with aliasmode_browser_select before page actions. |
| Two agents fight over the same profile | Give one agent ownership of an active profile at a time. aliasmode_browser_status shows whether a profile is already open before a second agent starts it. |
What the Hermes agent gets
- Profile lifecycle: list, create, and delete profiles through the agent
- Browser control: open headful or headless, select an open browser, check status, close safely
- Page actions: 31 Playwright tools for navigation, forms, screenshots, and verification
- Local-first operation: AliasMode Local mode needs no account and no Cloud connection
Generic JSON alternative
If you configure Hermes MCP servers through a JSON settings file, the standard stdio shape below is equivalent to what the setup command writes.
{
"mcpServers": {
"aliasmode": {
"command": "C:\\Users\\<you>\\AppData\\Local\\AliasMode\\aliasmode-mcp.exe",
"args": [
"serve"
]
}
}
}Sources and verification
- Model Context Protocol · MCP specification — stdio transport and server lifecycle (checked September 2026)
- AliasMode repository · agent/setup.ts — generated Hermes registration command (checked September 2026)
- AliasMode · Generated MCP tool catalog for the released 0.1.0-beta.47 installer (checked September 2026)
Public product details can change after the check date. Facts are re-checked on a monthly cycle.