A side-by-side look at the MCP Server Commands and Hermes Agent MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Commands for coding agents work as a local process; choose Hermes Agent MCP for coding agents as a local process. You can also run both side by side in one mcpServers block.
run_process.HERMES_HOME, HERMES_MCP_BIN, HERMES_MCP_ALLOW_WRITE, HERMES_MCP_ALLOW_SHELL, HERMES_MCP_TIMEOUT, HERMES_MCP_ASK_TIMEOUT, HERMES_MCP_MAX_OUTPUT, HERMES_MCP_CALLER.hermes_status, hermes_ask, doctor.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 65/100 · Great | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | HERMES_HOMEHERMES_MCP_BINHERMES_MCP_ALLOW_WRITEHERMES_MCP_ALLOW_SHELLHERMES_MCP_TIMEOUTHERMES_MCP_ASK_TIMEOUTHERMES_MCP_MAX_OUTPUTHERMES_MCP_CALLER |
| Verified owner | Community listing | Community listing |
| GitHub stars | 235 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | 12 |
| Full listing | View MCP Server Commands | View Hermes Agent MCP |
run_processRun a process on this linux machinehermes_statusServer config, whether the CLI answers, which tools are enabledhermes_askHand the agent a task and get its reply (one non-interactive turn)doctorhermes doctor` health reportgateway_statusMessaging gateway state and restartcron_listScheduled jobs, including per-job model and reasoning effortconfig_getTyped reads and writes against `config.yamlskills_listInstalled skillssessions_listRecent sessionsmodel_infoDefault model, provider and Nous Portal statusshellRun a shell command on the host — **off by defaultbridge_setupPoint the bridge at a chat (Telegram by default)bridge_askAsk through the **gateway** and mirror prompt + reply into that chatPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"g0t4-mcp-server-commands": {
"command": "npx",
"args": [
"mcp-server-commands"
]
}
}
}
{
"mcpServers": {
"hermes-agent-mcp": {
"command": "uvx",
"args": [
"hermes-agent-mcp"
],
"env": {
"HERMES_HOME": "YOUR_HERMES_HOME_HERE",
"HERMES_MCP_BIN": "YOUR_HERMES_MCP_BIN_HERE",
"HERMES_MCP_ALLOW_WRITE": "YOUR_HERMES_MCP_ALLOW_WRITE_HERE",
"HERMES_MCP_ALLOW_SHELL": "YOUR_HERMES_MCP_ALLOW_SHELL_HERE",
"HERMES_MCP_TIMEOUT": "YOUR_HERMES_MCP_TIMEOUT_HERE",
"HERMES_MCP_ASK_TIMEOUT": "YOUR_HERMES_MCP_ASK_TIMEOUT_HERE",
"HERMES_MCP_MAX_OUTPUT": "YOUR_HERMES_MCP_MAX_OUTPUT_HERE",
"HERMES_MCP_CALLER": "YOUR_HERMES_MCP_CALLER_HERE"
}
}
}
}