Tidewave Phoenix
Open-source MCP server giving coding agents runtime access to Phoenix dev apps
- Pricing
- Open source
- Platforms
- CLI, self-hosted, API
- Version
- 0.8.0
- Listing updated
- today
Similar MCP servers
About Tidewave Phoenix
Tidewave Phoenix is an open-source MCP server for developer tools. It is available on CLI, self-hosted and API.
The README describes Tidewave Phoenix as a server that lets a coding agent talk to a Phoenix application while it is running in development. Instead of guessing how the app behaves, the agent can evaluate Elixir inside the live process, read recent logs, and run SQL against the development database.
Setup is done by adding the tidewave hex package as a dev-only dependency and plugging it into the Phoenix endpoint, or by using Igniter to install it automatically. The MCP client then connects over streamable HTTP to the /tidewave/mcp path on the local web server port. The README also notes a stdio proxy option through mix tidewave.proxy for projects that run servers on several ports, such as git worktrees.
The project is Apache-2.0 licensed and is part of the wider Tidewave environment for Phoenix and Rails. It is aimed at Phoenix developers who already use an AI coding agent and want it to verify changes against their running app.
Tools this server provides (5)
Taken from the project documentation; the running server may differ.
- project_eval
- Evaluates Elixir code within the running application.
- execute_sql_query
- Executes a SQL query within the development database.
- get_docs
- Gets documentation for a module or function at locked dependency versions.
- get_logs
- Reads logs written by the server.
- get_source_location
- Gets the source location of a module or function.
What it does
- Run code in app
- Evaluates Elixir inside the running application so the agent can inspect runtime state and dependencies.
- Live log reading
- Lets the agent read server logs to trace what happened after a request.
- Development database queries
- Executes SQL against the development database to check the effects of changes.
- Version-pinned documentation
- Fetches module and function docs matching the exact hex package versions in mix.lock.
- Source location lookup
- Finds where a module or function is defined, including inside hex dependencies.
- Localhost-only access by default
- Accepts requests only from localhost unless remote access is explicitly enabled.
Good for
- Reproducing a failing code path against live application state
- Checking what a function returns before changing code
- Reading request logs and backtraces after a bug appears
- Verifying a data change by querying the development database
- Looking up docs for a dependency at the version the project uses
Pricing
Open source
Open-source Apache-2.0 MCP server; the wider Tidewave product is separate.
Tidewave Phoenix FAQ
How do I connect an MCP client to it?
Add the Tidewave MCP server as an HTTP (streamable) type pointing to /tidewave/mcp on your running app, for example http://localhost:4000/tidewave/mcp.
Is it open source?
The README says it is an open-source component licensed under Apache License 2.0.
Does it work with multiple ports or worktrees?
The README suggests running mix tidewave.proxy as a stdio MCP server, which adds a port parameter to tool definitions.
Is Tidewave Phoenix free?
Yes. Tidewave Phoenix is open source, so you can use and self-host it for free.
What are the best alternatives to Tidewave Phoenix?
The closest alternatives to Tidewave Phoenix are Tidewave Rails, tesserai, Kodelyth ECC, Weavatrix and Mcphost.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.