get_instance_usage_history — Nodecraft MCP Tool Read-only
get_instance_usage_history
(get instance usage history) is one of 67 tools on the
Nodecraft
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_instance_usage_history from your client
- Claude Code Nodecraft get_instance_usage_history run in your project directory
- Claude Desktop Nodecraft get_instance_usage_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nodecraft get_instance_usage_history ~/.cursor/mcp.json
- VS Code Nodecraft get_instance_usage_history .vscode/mcp.json
- Zed Nodecraft get_instance_usage_history ~/.config/zed/settings.json
- Windsurf Nodecraft get_instance_usage_history ~/.codeium/windsurf/mcp_config.json
- Cline Nodecraft get_instance_usage_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nodecraft get_instance_usage_history ~/.gemini/settings.json
- Grok Nodecraft get_instance_usage_history .mcp.json (in your project root)
- ChatGPT Nodecraft get_instance_usage_history Settings → Connectors → Advanced → Developer mode
- Claude.ai Nodecraft get_instance_usage_history Settings → Connectors → Add custom connector
- LangChain Nodecraft get_instance_usage_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.nodecraft.com/mcpOther tools on this server
- get_auth_status
- list_instances
- recommend_plan
- get_account_usage_summary
- get_available_slots
- get_dedicated_server_info
- get_subscription_info
- get_upgrade_link
- list_services
- list_locations
- get_game
- search_game_files
- list_file_releases
- create_instance
- deploy_instance
- start_instance
- stop_instance
- restart_instance
- wake_instance
- get_instance_info
- get_instance_metrics
- manage_instance
- get_connection_info
- search_player
- search_knowledgebase
- get_settings
- set_settings
- list_instance_users
- set_user_permissions
- remove_user_access
- copy_user_access
- get_jit_share
- set_jit_share
- regenerate_jit_share_url
- add_port
- update_port
- delete_port
- create_database
- delete_database
- get_database_info
- reset_database_password
- list_backups
- restore_backup
- list_tasks
- create_task
- update_task
- delete_task
- list_tickets
- get_ticket
- create_ticket
- reply_to_ticket
- list_files
- search_files
- read_file
- write_file
- edit_file
- create_directory
- copy_path
- move_path
- delete_path
- compress_paths
- extract_archive
- create_backup
- send_console_command
- get_console_output
- list_online_players
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.