Wick
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WICK_GROUPS | No | Comma-separated tool pillars to enable | core |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tool_catalogA | Returns every known Wick tool with its group assignment and whether it is active in this process. Use to discover available functionality. |
| tool_resetA | Placeholder for future dynamic group activation. Not functional in v1: Wick resolves groups once at startup from --groups or WICK_GROUPS. This tool is retained for forward compatibility. |
| detect_languageB | Determines the language context for a given file path (GDScript, C#, or Godot resource). |
| godot_statusB | Returns Godot Engine provider status and capabilities. |
| script_createB | Generates a GDScript file template for a node type with proper structure: extends, class_name, lifecycle functions, and signals. |
| gd_lsp_connectA | Explicitly connects and initializes the GDScript Language Server. (Most other LSP tools will automatically connect if needed). |
| gd_script_statusA | Returns GDScript provider status and capabilities. |
| tool_groupsA | Returns the resolved active tool groups for this Wick process along with descriptions of every available group. |
| gd_lsp_hoverB | Simulates hovering over a symbol at a specific line and character to get documentation and type info. |
| gd_lsp_symbolsB | Gets the document symbols (functions, variables, classes) for a given GDScript file. |
| script_infoA | Parses a GDScript file and returns its structure: class_name, extends, functions, signals, variables, exports, constants, and enums. |
| scene_nodesA | Parses a .tscn scene file and returns the node tree structure, properties, and external resources. |
| project_listB | Discovers Godot projects under a given root directory. Returns project names, paths, C# support status, and scene/script counts. |
| gd_lsp_definitionA | Finds the definition (source file and line) of the symbol at the given position. |
| scene_listB | Lists all scenes (.tscn files) in a Godot project directory. |
| script_listB | Lists all scripts (.gd and .cs files) in a Godot project directory with language detection. |
| project_infoA | Reads detailed info about a specific Godot project from its project.godot file path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose, from language detection and LSP features to project and script analysis. No overlap or ambiguity among the 17 tools.
Tools use snake_case and are grouped by domain (e.g., gd_lsp_, project_, scene_, script_, tool_). Minor inconsistencies like 'detect_language' vs. verb-noun pattern in others, but overall predictable.
17 tools is well-scoped for a Godot development MCP server, covering project discovery, script analysis, LSP features, and administrative functions without being excessive.
The tool set covers core workflows: project listing, scene/script inspection, LSP support, and script creation. Missing scene editing or saving, but sufficient for analysis and code assistance.