In-depth architectural comparison of the UI5 MCP Server 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
UI5 MCP Server
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Tidewave Phoenix
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose UI5 MCP Server 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 UI5 MCP Server 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).
UI5 MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Tidewave Phoenix belongs to Developer Tools using local stdio subprocess. Select UI5 MCP Server when you need capabilities focused on developer tools and Tidewave Phoenix when you require tools for developer tools.
Extracts metadata and configuration from a UI5 project.
get_typescript_conversion_guidelines
Provides guidelines for converting UI5 applications and controls from JavaScript to TypeScript.
get_version_info
Retrieves version information for the UI5 framework.
run_manifest_validation
Validates the manifest against the UI5 Manifest schema.
run_ui5_linter
Integrates with [`@ui5/linter`](https://github.com/UI5/linter) to analyze and report issues in the UI5 code.
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.