In-depth architectural comparison of the Andrea9293 MCP 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
Andrea9293 MCP
Developer Tools · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Tidewave Phoenix
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Andrea9293 MCP 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 Andrea9293 MCP 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).
Andrea9293 MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Tidewave Phoenix belongs to Developer Tools using local stdio subprocess. Select Andrea9293 MCP when you need capabilities focused on developer tools and Tidewave Phoenix when you require tools for developer tools.
Lists files in the uploads folder with size and format info
get_ui_url
Returns the Web UI URL (e.g. http://localhost:3080) — useful to open the dashboard or to locate the uploads folder from the browser
search_documents
Semantic vector search within a specific document
search_all_documents
Hybrid (full-text + vector) cross-document search
get_context_window
Returns a window of chunks around a given chunk index
search_documents_with_ai
🤖 AI-powered search using Gemini (requires `GEMINI_API_KEY`)
Tidewave Phoenix Tools (5)
project_eval
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.