info_get_node_version — Avalanche AVAX MCP MCP Tool

info_get_node_version (info get node version) is one of 48 tools on the Avalanche AVAX MCP MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call info_get_node_version from your client

Claude Code Avalanche AVAX MCP info_get_node_version run in your project directory
Claude Desktop Avalanche AVAX MCP info_get_node_version ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Avalanche AVAX MCP info_get_node_version ~/.cursor/mcp.json
VS Code Avalanche AVAX MCP info_get_node_version .vscode/mcp.json
Zed Avalanche AVAX MCP info_get_node_version ~/.config/zed/settings.json
Windsurf Avalanche AVAX MCP info_get_node_version ~/.codeium/windsurf/mcp_config.json
Cline Avalanche AVAX MCP info_get_node_version ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Avalanche AVAX MCP info_get_node_version ~/.gemini/settings.json
Grok Avalanche AVAX MCP info_get_node_version .mcp.json (in your project root)
ChatGPT Avalanche AVAX MCP info_get_node_version Settings → Connectors → Advanced → Developer mode
Claude.ai Avalanche AVAX MCP info_get_node_version Settings → Connectors → Add custom connector
LangChain Avalanche AVAX MCP info_get_node_version pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http avalanche-docs https://build.avax.network/api/mcp

Other 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.

Avalanche AVAX MCP MCP server