Claude-skill-registry godot-mcp-dap-start

Start or restart the Godot editor MCP server and debugger/DAP ports for this project. Use when MCP tools are missing, handshake fails, or the debug port is absent; includes a single-editor restart workflow and command checks.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/godot-mcp-dap-start" ~/.claude/skills/majiayu000-claude-skill-registry-godot-mcp-dap-start && rm -rf "$T"

manifest: skills/data/godot-mcp-dap-start/SKILL.md

Godot MCP + Debug Start

Overview

Ensure a single Godot editor instance is running, MCP is reachable, and the debug port is available for HPV and runtime inspection.

Workflow (Option A: clean restart)

Run the start script to ensure MCP is up:

powershell -ExecutionPolicy Bypass -File scripts/ensure_godot_mcp.ps1

If MCP handshake fails or multiple editors are running, rerun with a forced restart:
- ```
powershell -ExecutionPolicy Bypass -File scripts/ensure_godot_mcp.ps1 -ForceRestart
```

If you need the debug port for runtime inspection, rerun with:

powershell -ExecutionPolicy Bypass -File scripts/ensure_godot_mcp.ps1 -StartGameForDebug

Success Criteria

Port 9080 is listening and
```
godot-mcp-cli --list-tools
```
succeeds.
When
```
-StartGameForDebug
```
is used, port 6007 is listening.

Notes

Do not ask the user to click the MCP panel. Use the script first.
Use a single Godot editor instance to avoid MCP conflicts.
See
```
references/commands.md
```
for CLI and port checks.