Claude Desktop Phoenix operational_context unpaid canary get_operational_context
How to: Claude Desktop Phoenix operational_context unpaid canary get_operational_context
Add Phoenix operational_context unpaid canary to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"operational-context": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something get_operational_context does. Claude Desktop 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.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop 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.