tidewave-integration

# Tidewave MCP Integration Runtime intelligence for Phoenix apps via MCP. Prefer Tidewave tools over Bash when available. ## Iron Laws — Never Violate These 1. **DEV ONLY** — Never use Tidewave tools in production contexts. Avoid on shared dev servers with production data copies 2. **PREFER TIDEWAVE OVER BASH** — `mcp__tidewave__get_docs` > `web_fetch`, `execute_sql_query` > `psql` 3. **CHECK AVAILABILITY FIRST** — Use `/mcp` command or detect `mcp__tidewave__` tools 4. **SQL IS READ-HEAVY** — Use `execute_sql_query` for SELECT, be careful with mutations 5. **EXACT VERSIONS** — `get_docs` returns docs for YOUR mix.lock versions, not latest ## Quick Reference | Task | Tidewave Tool | Fallback | |------|---------------|----------| | Get docs | `mcp__tidewave__get_docs Module.func/3` | `web_fetch hexdocs.pm/...` | | Run code | `mcp__tidewave__project_eval` | `mix run -e "code"` | | SQL query | `mcp__tidewave__execute_sql_query` | `psql $DATABASE_URL` | | Find source | `mcp__tidewave__get_source_location` | `grep -rn "defmodule"` | | Inspect DOM | `mcp__Tidewave-Web__browser_eval` | Manual browser inspection | | List schemas | `mcp__tidewave__get_ecto_schemas` | Read `lib/*/schemas/` | | Read logs | `mcp__tidewave__get_logs level: :error` | `tail -f log/dev.log` | ## Detection ```bash # Check endpoint curl -s http://localhost:4000/tidewave/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"ping"}' ``` Or use `/mcp` in Claude Code to see ...