GOPEAK TOOLS

33 tools from the Gopeak MCP Server, categorised by risk level.

View the Gopeak policy →

READ TOOLS

17
class-info [compact alias of query_class_info] Get detailed information about a specific Godot class: methods, properties, signals, enums. Use to discover ava... class-query [compact alias of query_classes] Query available Godot classes from ClassDB with filtering. Use to discover node types, resource types, or any clas... dap-output [compact alias of dap_get_output] Get captured Godot DAP console output lines editor-debug-output [compact alias of get_debug_output] Retrieves console output and errors from the currently running Godot project. Use after run_project to check lo... editor-status [compact alias of get_editor_status] Returns the connection status of the Godot Editor Plugin bridge. Use to check if the editor is connected befor... editor-version [compact alias of get_godot_version] Returns the installed Godot engine version string. Use to check compatibility (e.g., Godot 4.4+ features like ... lsp-diagnostics [compact alias of lsp_get_diagnostics] Get GDScript diagnostics from Godot Language Server for a script file. project-info [compact alias of get_project_info] Returns metadata about a Godot project including name, version, main scene, autoloads, and directory structure.... project-list [compact alias of list_projects] Scans a directory for Godot projects (folders containing project.godot). Use to discover projects before using oth... 2/5 project-search [compact alias of search_project] Searches for text or regex patterns across project files. Use to find function usages, variable references, or TO... 2/5 project-setting-get [compact alias of get_project_setting] Reads a value from project.godot settings. Use to check game name, window size, physics settings, etc. resource-dependencies [compact alias of get_dependencies] Analyzes resource dependencies and detects circular references. Use to understand what a scene/script depends o... runtime-status [compact alias of get_runtime_status] Checks if a Godot game instance is running and connected for live debugging. Use before other runtime tools. scene-node-properties [compact alias of get_node_properties] Returns all properties of a specific node in a scene. Use to inspect current values before modifying. Return... scene-nodes [compact alias of list_scene_nodes] Returns complete scene tree structure with all nodes, types, and hierarchy. Use to understand scene organizatio... script-info [compact alias of get_script_info] Analyzes a GDScript and returns its structure: functions, variables, signals, class_name, extends. Use before mo... tool-catalog [compact alias of tool_catalog] Discover available tools including hidden legacy tools. Use query to search by capability keywords. Results include... 2/5

WRITE TOOLS

10
export-presets [compact alias of list_export_presets] Lists all export presets defined in export_presets.cfg. Use before export_project to see available targets (... 2/5 export-run [compact alias of export_project] Exports the project to a distributable format. Use to build final game executables. Requires export templates ins... 2/5 project-setting-set [compact alias of set_project_setting] Writes a value to project.godot settings. Use to configure game name, window size, physics, etc. 2/5 scene-create [compact alias of create_scene] Creates a new Godot scene file (.tscn) with a specified root node type. Use to start building new game levels, UI s... 3/5 scene-node-add [compact alias of add_node] Adds ANY node type to an existing scene. This is the universal node creation tool — replaces all specialized create_* n... 2/5 scene-node-set [compact alias of set_node_properties] Sets multiple properties on a node in a scene. Prerequisite: scene and node must exist (use create_scene and... 2/5 scene-save [compact alias of save_scene] Saves changes to a scene file or creates a variant at a new path. Most scene modification tools save automatically, b... 2/5 script-create [compact alias of create_script] Creates a new GDScript (.gd) file with optional templates. Use to generate scripts for game logic. Templates: "sin... 2/5 script-modify [compact alias of modify_script] Adds functions, variables, or signals to an existing GDScript. Use to extend scripts without manual editing. Suppo... 3/5 signal-connect [compact alias of connect_signal] Creates a signal connection between nodes in a scene. Prerequisite: source and target nodes must exist. Use to wi... 2/5

DESTRUCTIVE TOOLS

2

EXECUTE TOOLS

4
How many tools does the Gopeak MCP server have? +

The Gopeak MCP server exposes 33 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Gopeak tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Gopeak server.

What risk categories do Gopeak tools fall into? +

Gopeak tools are categorised as Read (17), Write (10), Destructive (2), Execute (4). Each category has a recommended default policy.

Enforce policies on Gopeak

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.