Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
MCP server with runtime-level tools for Phoenix development
| Date | Stars |
|---|---|
| 2026-07-31 | 838 |
| 2026-08-03 | 839 |
| 2026-08-06 | 839 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Tidewave Phoenix
Tidewave Phoenix is an MCP server that provides runtime-level tools for developing Phoenix apps using coding agents.
Your agent will be able to use this MCP server to talk to your running Phoenix app in development to:
- execute code in the context of the running app (like an IEx session for agents)
- read the app's live logs
- query your development database
- get source locations of modules and functions
- read documentation pinned to the exact hex package versions your project depends on
This MCP server is an open-source component of [Tidewave](https://tidewave.ai), the agentic development environment for Phoenix and Rails.
You can use this project as a standalone MCP server or integrated with the [Tidewave product](https://tidewave.ai) by following the installation instructions below.
## Installation
### 1. Add the Tidewave hex package to your app
#### Option 1: Manually
Add the `tidewave` package to your `mix.exs`:
```elixir
def deps do
[
{:tidewave, "~> 0.6", only: :dev},
{:phoenix, ...},
]
end
```
Then, for Phoenix applications, go to your `lib/my_app_web/endpoint.ex` and right above the `if code_reloading? do` block, add:
```diff
+ if Mix.env() == :dev do
+ plug Tidewave
+ end
if code_reloading? do
```
> [!TIP]
> Tidewave works best with Phoenix LiveView v1.1 or later. Once you update it,
> make sure to enable the following options in your `config/dev.exs`:
>
> ```elixir
> config :phoenix_live_view,
> debug_heex_annotations: true,
> debug_attributes: true
> ```
>
> Those are enabled by default for Phoenix v1.8+ apps.
#### Option 2: Using Igniter
Alternatively, you can use `igniter` to automatically install Tidewave MCP into an existing Phoenix application:
```sh
# install igniter_new if you haven't already
mix archive.install hex igniter_new
# install tidewave
mix igniter.install tidewave
```
#### Umbrella projects
For umbrella projects, you can follow the manual steps above in the application that defines your Phoenix endpoint (typically `apps/your_app_web`).
#### In non-Phoenix applications
Tidewave can be used as a MCP in any Elixir project. For example, you can use `bandit` (and `tidewave`) in dev mode in your `mix.exs`:
```elixir
{:tidewave, "~> 0.6", only: :dev},
{:bandit, "~> 1.0", only: :dev},
```
And then adding an alias in your `mix.exs`:
```elixir
aliases: [
tidewave:
"run --no-halt -e 'Agent.start(fn -> Bandit.start_link(plug: Tidewave, port: 4000) end)'"
]
```
Now run `mix tidewave`
### 2. Add the Tidewave MCP to your agent/editor
Add the Tidewave MCP server to your editor or MCP client configuration as the type "http" (streamable), pointing to the `/tidewave/mcp` path and port your web application is running at. For example, `http://localhost:4000/tidewave/mcp`.
We also have specific instructions for:
- [Claude Code](https://tidewave.hexdocs.pm/mcp_claude_code.html)
- [Codex](https://tidewave.hexdocs.pm/mcp_codex.html)
- [Cursor](https://tidewave.hexdocs.pm/mcp_cursor.html)
- [Neovim](https://tidewave.hexdocs.pm/mcp_neovim.html)
- [OpenCode](https://tidewave.hexdocs.pm/mcp_opencode.html)
- [VS Code](https://tidewave.hexdocs.pm/mcp_vscode.html)
- [Others](https://tidewave.hexdocs.pm/mcp.html)
## Usage
As with any other MCP server, your agent will call the tools exposed by the Tidewave MCP whenever it sees fit. But you can also prompt it to call them explicitly.
## Available MCP tools
### `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.
[](https://asciinema.org/a/1260494)
Your agent can use it when it would rather run code than assume behavior, grounding its next step in what the running app actually does. For example, calling a function to see what comes back or reproducing a failing code path against live app state to debug it.
### `execute_sqExcerpt of 8,670 characters
Read on GitHub
José Valim · Poland
313
Steffen Deusch
60
Jonatan Kłosko · @dashbitco
15
8
4
3
3
Ang · Malaysia
2
2
2
1
1
1
1
1
1
1
1
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:dba7848483cf275e, desc:mcp server