Claude Code Phoenix operational_context unpaid canary get_operational_context
How to: Claude Code Phoenix operational_context unpaid canary get_operational_context
Add Phoenix operational_context unpaid canary to Claude Code
-
01
Run this in your project directory.
claude mcp add --transport http operational-context https://phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context/mcp-
02
Restart your session so the server is picked up.
-
03
Ask for something get_operational_context does. Claude Code lists the server's tools on connect and calls get_operational_context itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Phoenix operational_context unpaid canary's identifier in your config matches the one above exactly.
Adds it for this project only. Append --scope user to make it available everywhere. Claude Code docs
Same tool, other clients
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.