update_node — Chainstack MCP Tool Mutating

update_node (update node) is one of 18 tools on the Chainstack MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call update_node from your client

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

Fastest route

claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp

Other tools on this server

get_organization
get_deployment_options
list_projects
create_project
list_nodes
get_node
create_node
get_project
update_project
delete_project
delete_node
search_docs
get_doc_page
get_platform_status
contact_chainstack
request_testnet_funds
get_chainstack_pricing

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.

Chainstack MCP server