Skip to content

The TerraMCP directory

Find your next source.

Ranked by evidence. Filter by discipline, region and format to find sources for your project.

Reset filters

1254 sources

Sponsored placements first · Organic quality score ↓

mcp
85/100Currency A

tidewave_phoenix ↗

MCP server with runtime-level tools for Phoenix development

What's in it

Data offered docs-verified
runtime code execution in the running Phoenix app (project_eval) · live app logs (get_logs) · development database SQL queries (execute_sql_query) · module/function source locations, including hex dependencies (get_source_location) · documentation pinned to mix.lock versions (get_docs)
Formats docs-verified
MCP streamable HTTP · MCP stdio
Access docs-verified
Open source under Apache License 2.0; installed as a dev-only hex dependency (tidewave ~> 0.9, only: :dev); no credentials documented in DOCS

Useful for

Use cases llm-inferred
Debug a failing code path in a Phoenix data or asset app against live dev state using project_eval · Read request logs and backtraces with get_logs when a Phoenix app misbehaves during development · Verify records written by a Phoenix app in the dev database with execute_sql_query · Jump to the definition of a function in a hex dependency with get_source_location instead of grepping
Audience llm-inferred
Elixir/Phoenix developers · web developers building internal Phoenix tools · GIS and data developers maintaining Phoenix apps

Limitations

Constraints docs-verified
Phoenix applications only · development-only: the plug is intended for Mix.env() == :dev · tools execute arbitrary Elixir and SQL against the running dev app and dev database · localhost-only by default; remote access needs the allow_remote_access option · works best with Phoenix LiveView v1.1 or later · worktrees need mix tidewave.proxy as a STDIO MCP · no geographic or hosted dataset; output reflects only the local app's state
environmenthydrology

Globalhealthy