In-depth architectural comparison of the Tidewave Phoenix and MCP Language Server 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
Tidewave Phoenix
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
MCP Language Server
Developer Tools · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Tidewave Phoenix if you need specialized Developer Tools tools running via a local process. Choose MCP Language Server 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?
T
Choose Tidewave Phoenix 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).
Runtime-level MCP server for Phoenix development: run code, read logs, query the DB, read docs.
MCP Language Server helps MCP enabled clients navigate codebases more easily by giving them access to semantic tools like get definition, references, rename, and diagnostics.
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.
MCP Language Server Tools (6)
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).
Tidewave Phoenix is categorized under Developer Tools and uses a local stdio subprocess. In contrast, MCP Language Server belongs to Developer Tools using local stdio subprocess. Select Tidewave Phoenix when you need capabilities focused on developer tools and MCP Language Server when you require tools for developer tools.
Retrieves the complete source code definition of any symbol (function, type, constant, etc.) from your codebase.
references
Locates all usages and references of a symbol throughout the codebase.
diagnostics
Provides diagnostic information for a specific file, including warnings and errors.
hover
Display documentation, type hints, or other hover information for a given location.
rename_symbol
Rename a symbol across a project.
edit_file
Allows making multiple text edits to a file based on line numbers. Provides a more reliable and context-economical way to edit files compared to search and replace based edit tools.