LangChain leafwright leafwright_auth_status
How to: LangChain leafwright leafwright_auth_status
Add leafwright 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({
"leafwright": {
"transport": "streamable_http",
"url": "https://leafwright.co/mcp",
}
})
tools = await client.get_tools()
-
02
Save the file and restart LangChain.
-
03
Ask for something leafwright_auth_status does. LangChain lists the server's tools on connect and calls leafwright_auth_status itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that leafwright'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
Set these first
leafwright will not start until these are set, so leafwright_auth_status never becomes available.
-
LEAFWRIGHT_API_KEY -
LEAFWRIGHT_MCP_TOKEN -
LEAFWRIGHT_PROJECT_ID -
LEAFWRIGHT_MCP_READ_ONLY
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.