Qatouch vs Hermes Action Bridge — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Qatouch vs Hermes Action Bridge
In-depth architectural comparison of the Qatouch and Hermes Action Bridge MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Qatouch
Developer Tools · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Hermes Action Bridge
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Qatouch if you need specialized Developer Tools tools running via a local process. Choose Hermes Action Bridge if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Q
Choose Qatouch when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Qatouch is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Hermes Action Bridge belongs to Developer Tools using local stdio subprocess. Select Qatouch when you need capabilities focused on developer tools and Hermes Action Bridge when you require tools for developer tools.
Get the total number of test cases available for a QA Touch project
count_test_runs
Get the total number of test runs available for a QA Touch project
create_bulk_test_cases
Create multiple QA Touch test cases from a scenario
create_defect
Create a QA Touch defect with priority and issue summary
create_exploratory_test_case
Create a QA Touch exploratory-session test case without structured steps
create_module
Create a module in a QA Touch project
create_project
Create a new QA Touch project
+32 more tools listed on main page
Hermes Action Bridge Tools (5)
hermes_run
delegate a request to Hermes. Optional overrides: `mode`, `preset`, `contextFiles`, `yolo`, `dryRun`, and — to trade cost for speed on simple tasks — `model`, `provider`, `maxTurns`, `timeoutSeconds`. Any effective `execute` request opens an interactive confirmation form first.
hermes_plan
shortcut for `hermes_run` with `mode=plan`.
hermes_capabilities
report configured presets, skills, toolsets, runtime, and policy without inventing live integrations.