Hermes Action Bridge vs Tidewave Phoenix | AllMCPs
Side-by-Side Model Context Protocol Comparison
Hermes Action Bridge vs Tidewave Phoenix
In-depth architectural comparison of the Hermes Action Bridge and Tidewave Phoenix 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
Hermes Action Bridge
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Tidewave Phoenix
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Hermes Action Bridge if you need specialized Developer Tools tools running via a local process. Choose Tidewave Phoenix 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?
Choose Hermes Action Bridge 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).
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.
hermes_presets
list configured presets.
hermes_status
check the configured Hermes runtime command.
Tidewave Phoenix Tools (5)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Hermes Action Bridge is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Tidewave Phoenix belongs to Developer Tools using local stdio subprocess. Select Hermes Action Bridge when you need capabilities focused on developer tools and Tidewave Phoenix when you require tools for developer tools.
Evaluates Elixir code within your running application, giving the agent access to your runtime, dependencies, and in-memory data. It's like an IEx for the agent.
execute_sql_query
Executes a SQL query within your app's development database.
get_docs
Get the documentation for a given module/function. It consults the exact versions locked in your project's mix.lock, ensuring you get correct information.
get_logs
Reads logs written by the server.
get_source_location
Get the source location for a given module/function, across both your app and its dependencies.