phoenix_relink_check — phoenix screen MCP Tool
phoenix_relink_check
(phoenix relink check) is one of 1 tool on the
phoenix screen
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call phoenix_relink_check from your client
- Claude Code phoenix screen phoenix_relink_check run in your project directory
- Claude Desktop phoenix screen phoenix_relink_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor phoenix screen phoenix_relink_check ~/.cursor/mcp.json
- VS Code phoenix screen phoenix_relink_check .vscode/mcp.json
- Zed phoenix screen phoenix_relink_check ~/.config/zed/settings.json
- Windsurf phoenix screen phoenix_relink_check ~/.codeium/windsurf/mcp_config.json
- Cline phoenix screen phoenix_relink_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI phoenix screen phoenix_relink_check ~/.gemini/settings.json
- Grok phoenix screen phoenix_relink_check .mcp.json (in your project root)
- ChatGPT phoenix screen phoenix_relink_check Settings → Connectors → Advanced → Developer mode
- Claude.ai phoenix screen phoenix_relink_check Settings → Connectors → Add custom connector
- LangChain phoenix screen phoenix_relink_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http phoenix-screen https://phoenix.dropwatchhq.com/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.