Code execution · MCP server
Tidewave Phoenix: MCP server, setup and security
Tidewave Phoenix is an open-source MCP server published on GitHub that lets an AI agent run Phoenix code, read logs, query databases and consult documentation. Its repository has 858 stars and its last commit is from October 23, 2026 and it is licensed under Apache-2.0.
| Adoption (stars) | 29/40 | |
|---|---|---|
| Maintenance | 30/30 | |
| Framework (licence, registry, official) | 15/30 |
What Tidewave Phoenix does
According to its repository: “Runtime-level MCP server for Phoenix development: run code, read logs, query the DB, read docs.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Tidewave Phoenix is listed under Code execution, a category of 32 servers in the directory, where it ranks #4 by stars.
Installing and connecting Tidewave Phoenix
No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Elixir.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
Points found for Tidewave Phoenix:
- System access: the Code execution category gives the agent control over files, a terminal, code or a browser. A booby-trapped instruction in content the agent reads (prompt injection) can then turn into an action.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on April 17, 2025, the tidewave-ai/tidewave_phoenix repository has 858 stars and 74 forks, with 3 open issues. It has more stars than 91% of the servers in the directory. It received changes this month. Version published in the registry: 0.8.0 (July 24, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Tidewave Phoenix is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Widely followed: 858 stars
- Listed in the official MCP registry
- Permissive licence (Apache-2.0)
Limitations
- Install from source
Avoid if…
- You cannot isolate the agent (sandbox, container)
Alternatives
- Container use4.1K ★
- LLM Sandbox1.1K ★
- Superserve466 ★
- OrcaReplay281 ★
- Mailtrap66 ★
- MCP v862 ★
Learn more
Frequently asked questions
How do I install Tidewave Phoenix?
No package is declared in the MCP registry: clone the tidewave-ai/tidewave_phoenix repository, follow its README, then declare the start command in your client's MCP configuration.
Is Tidewave Phoenix free?
The code is published under the Apache-2.0 licence and can be used free of charge.
Is Tidewave Phoenix safe?
Points to watch: system access. Give it minimum rights and approve sensitive actions.
Is it an official server?
Nothing says so: it is a project published by tidewave-ai on GitHub. Check who maintains it before giving it access.
What are the alternatives to Tidewave Phoenix?
In the same category: Container use, LLM Sandbox, Superserve, and OrcaReplay.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score