leafwright_auth_status — leafwright MCP Tool
leafwright_auth_status
(leafwright auth status) is one of 3 tools on the
leafwright
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call leafwright_auth_status from your client
- Claude Code leafwright leafwright_auth_status run in your project directory
- Claude Desktop leafwright leafwright_auth_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor leafwright leafwright_auth_status ~/.cursor/mcp.json
- VS Code leafwright leafwright_auth_status .vscode/mcp.json
- Zed leafwright leafwright_auth_status ~/.config/zed/settings.json
- Windsurf leafwright leafwright_auth_status ~/.codeium/windsurf/mcp_config.json
- Cline leafwright leafwright_auth_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI leafwright leafwright_auth_status ~/.gemini/settings.json
- Grok leafwright leafwright_auth_status .mcp.json (in your project root)
- ChatGPT leafwright leafwright_auth_status Settings → Connectors → Advanced → Developer mode
- Claude.ai leafwright leafwright_auth_status Settings → Connectors → Add custom connector
- LangChain leafwright leafwright_auth_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http leafwright https://leafwright.co/mcpOther tools on this server
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.