Tidewave Phoenix
About
Tidewave MCP provides runtime-level tools to develop Elixir Phoenix apps. Your agent will be able to talk to your running application: execute code in your running app (like an IEx console), read logs, read version-accurate docs of your deps, query the database, and get the sourc
Details
- Author
- tidewave-ai
- Downloads
- 320
- Categories
- Developer Tools
Jump to
- Execute code in the running app (like IEx console)
- Read logs from the running application
- Read version-accurate docs of your dependencies
- Query the database directly
- Get the source location of modules and functions
—
Better agentic Phoenix development, runtime-level tools for your agent to talk to your running app.
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 ofTidewave, the agentic development environment for Phoenix and Rails.
You can use this project as a standalone MCP server or integrated with theTidewave productby following the installation instructions below.
1. Add the Tidewave hex package to your app
Add thetidewavepackage to yourmix.exs:
def deps do [ {:tidewave, "~> 0.6", only: :dev}, {:phoenix, ...}, ] end
Then, for Phoenix applications, go to yourlib/my_app_web/endpoint.exand right above theif code_reloading? doblock, add:
+ 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 yourconfig/dev.exs:
config :phoenix_live_view, debug_heex_annotations: true, debug_attributes: true
Those are enabled by default for Phoenix v1.8+ apps.
Alternatively, you can useigniterto automatically install Tidewave MCP into an existing Phoenix application:
# install igniter_new if you haven't already mix archive.install hex igniter_new # install tidewave mix igniter.install tidewave
For umbrella projects, you can follow the manual steps above in the application that defines your Phoenix endpoint (typicallyapps/your_app_web).
Tidewave can be used as a MCP in any Elixir project. For example, you can usebandit(andtidewave) in dev mode in yourmix.exs:
{:tidewave, "~> 0.6", only: :dev}, {:bandit, "~> 1.0", only: :dev},
And then adding an alias in yourmix.exs:
aliases: [ tidewave: "run --no-halt -e 'Agent.start(fn -> Bandit.start_link(plug: Tidewave, port: 4000) end)'" ]
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/mcppath and port your web application is running at. For example,http://localhost:4000/tidewave/mcp.
- Claude Code
- Codex
- Cursor
- Neovim
- OpenCode
- VS Code
- Others
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.
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.
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.
Executes a SQL query within your app's development database.
Your agent can use it to run any SQL against your development database. Useful for the agent to verify the result of an action.
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.
Your agent can use it to see what happened after a request. For example, reading the request log and backtrace when something misbehaves.
Get the source location for a given module/function, across both your app and its dependencies.
Your agent can use it to jump straight to where a module/function is defined, by file and line, instead of grepping for it, including when the definition lives in a hex dependency.
If you are using multiple hosts/subdomains during development, you must use.localhost, as such domains are considered secure by browsers. Additionally, add the following immediately@session_optionsdefinition in yourlib/your_app_web/endpoint.ex:
@session_options [ # ... your configuration ] if code_reloading? do @session_options Keyword.merge(@session_options, same_site: "None", secure: true) end
The above will allow your application to run embedded within Tidewave across multiple subdomains, as long as it is using a secure context (such asadmin.localhost,www.foobar.localhost, etc).
If you have enabled Content-Security-Policy, Tidewave will automatically enable "unsafe-eval" underscript-srcin order for contextual browser testing to work correctly. It also disables theframe-ancestorsdirective. This is done only in the environments that Tidewave is loadead (development by default).
You may configure theTidewaveplug using the following syntax:
-
:allow_remote_access- Tidewave only allows requests from localhost by default, even if your server listens on other interfaces, for security purposes. Readour security guidelines for more information and when to allow remote access(if you know what you are doing)
:allowed_origins- a list of values matched against theOriginheader to prevent cross origin and DNS rebinding attacks. Each value must be a string of shape[scheme:]//host[:port], where both scheme and port are optional. The host may also start with "". Example:["//localhost:8000", "//*.test"]
:inspect_opts- custom options passed toKernel.inspect/2when formatting some tool results. Defaults to:[charlists: :as_lists, limit: 50, pretty: true]
:team- set your Tidewave Team configuration, such asteam: [id: "my-company"]
:toolbar- controls whether the Tidewave toolbar is injected into your HTML pages. Defaults totrue
tmp_dir- temporary directory Tidewave uses for screenshots and recordings. It must be a relative directory to the current application root. Defaults totmp, storing files undertmp/tidewave/screenshotsandtmp/tidewave/recordings
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Create crafted UI components inspired by the best 21st.dev design engineers.
Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent
ALAPI MCP Tools,Call hundreds of API interfaces via MCP
AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform
MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.
APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.
One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.
Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
