list_nodes — EvaFarm — GPU render nodes MCP Tool Read-only
list_nodes
(list nodes) is one of 5 tools on the
EvaFarm — GPU render nodes
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_nodes from your client
- Claude Code EvaFarm — GPU render nodes list_nodes run in your project directory
- Claude Desktop EvaFarm — GPU render nodes list_nodes ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EvaFarm — GPU render nodes list_nodes ~/.cursor/mcp.json
- VS Code EvaFarm — GPU render nodes list_nodes .vscode/mcp.json
- Zed EvaFarm — GPU render nodes list_nodes ~/.config/zed/settings.json
- Windsurf EvaFarm — GPU render nodes list_nodes ~/.codeium/windsurf/mcp_config.json
- Cline EvaFarm — GPU render nodes list_nodes ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EvaFarm — GPU render nodes list_nodes ~/.gemini/settings.json
- Grok EvaFarm — GPU render nodes list_nodes .mcp.json (in your project root)
- ChatGPT EvaFarm — GPU render nodes list_nodes Settings → Connectors → Advanced → Developer mode
- Claude.ai EvaFarm — GPU render nodes list_nodes Settings → Connectors → Add custom connector
- LangChain EvaFarm — GPU render nodes list_nodes pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http evafarm https://evafarmstore.ru/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 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.