Shadcn Ui MCP Server vs Tidewave Phoenix | AllMCPs
Side-by-Side Model Context Protocol Comparison
Shadcn Ui MCP Server vs Tidewave Phoenix
In-depth architectural comparison of the Shadcn Ui 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
Shadcn Ui MCP Server
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Tidewave Phoenix
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Shadcn Ui 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 Shadcn Ui MCP Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST, MCP_CORS_ORIGINS, GITHUB_PERSONAL_ACCESS_TOKEN, UI_LIBRARY.
Shadcn Ui 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 Shadcn Ui MCP Server 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.