Bowmark vs Tidewave Rails — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Bowmark vs Tidewave Rails
In-depth architectural comparison of the Bowmark and Tidewave Rails 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
Bowmark
Developer Tools · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Tidewave Rails
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Bowmark if you need specialized Developer Tools tools running via a local process. Choose Tidewave Rails 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 Bowmark 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).
Read the typed function library for a task or a site. Read-only, touches no site, and an unrecognized query returns the index rather than an error.
run
Execute a short async JavaScript script against the live sites and return `{ ok, result, logs, error, ms }`.
register
Create a free Bowmark account and return an API key. Every argument is optional; `register({})` is a complete call.
Tidewave Rails Tools (5)
project_eval
Evaluates Ruby code in the context of your running application, with access to its runtime, loaded dependencies, and in-memory data, returning the result plus anything printed to standard output. It's like a Rails console for the agent.
execute_sql_query
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).
Bowmark is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Tidewave Rails belongs to Developer Tools using local stdio subprocess. Select Bowmark when you need capabilities focused on developer tools and Tidewave Rails when you require tools for developer tools.