LangChain Phoenix operational_context unpaid canary get_operational_context
How to: LangChain Phoenix operational_context unpaid canary get_operational_context
Add Phoenix operational_context unpaid canary to LangChain
-
01
Open pip install langchain-mcp-adapters and merge this in. Keep any servers already there.
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient({
"operational-context": {
"transport": "streamable_http",
"url": "https://phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context/mcp",
}
})
tools = await client.get_tools()
-
02
Save the file and restart LangChain.
-
03
Ask for something get_operational_context does. LangChain 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.
get_tools() returns the server's tools as LangChain tools, ready for an agent. LangChain 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.