Geargrafx MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Embedded MCP server for AI-assisted debugging via stdio or HTTP transport
Full debugger: JIT disassembler, CPU/memory breakpoints, code navigation
Supports HuCard, SuperGrafx, and CD-ROM² formats (pce, sgx, cue, zip, chd)
Multi Tap support for up to 5 players with various controller types
VGM recording and save states with preview images

Live-Demo

In der Praxis

geargrafx-2.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "geargrafx-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/drhelius/Geargrafx"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "geargrafx-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/drhelius/Geargrafx"
      ]
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "geargrafx-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/drhelius/Geargrafx"
      ]
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "geargrafx-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/drhelius/Geargrafx"
      ]
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "geargrafx-2",
      "command": "TODO",
      "args": [
        "See README: https://github.com/drhelius/Geargrafx"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "geargrafx-2": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/drhelius/Geargrafx"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add geargrafx-2 -- TODO 'See README: https://github.com/drhelius/Geargrafx'

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Geargrafx

How to debug a PC Engine ROM with AI assistance using Geargrafx

👤 PC Engine homebrew developers and retro game researchers ⏱ ~30 min intermediate

Wann einsetzen: You're developing or analyzing a PC Engine ROM and need to debug runtime behavior.

Voraussetzungen

Geargrafx built with MCP support — Build from source following the GitHub README
A PC Engine ROM file (.pce or .sgx) — Your own homebrew ROM or a ROM you legally own

Ablauf

Connect and inspect

Connect to the Geargrafx MCP server. Show me the current HuC6280 CPU state and disassembly at the program counter.✓ Kopiert

→ CPU registers and disassembled instructions
Analyze sprite system

Inspect the VDC sprite table. How many sprites are active and what tiles do they reference?✓ Kopiert

→ Sprite attribute table with positions, tile indices, and flags

Ergebnis: Understanding of ROM execution and VDC hardware state for debugging.

Fallstricke

CD-ROM games require proper CUE/BIN setup — Ensure your CUE file paths are correct and all BIN tracks are present

Kombinieren mit: filesystem

Learn PC Engine hardware architecture interactively

👤 Students and enthusiasts learning retro console hardware ⏱ ~45 min advanced

Wann einsetzen: You want to understand the HuC6280 CPU, VDC graphics, and PSG audio systems.

Voraussetzungen

Geargrafx with MCP server — Build from source

Ablauf

Explore the VDC

Step through the VBlank interrupt and explain how the PC Engine's VDC handles background scrolling and sprite rendering.✓ Kopiert

→ Annotated explanation of VDC register writes and their effects

Ergebnis: Hands-on understanding of PC Engine hardware internals.

Fallstricke

SuperGrafx has two VDCs which complicates analysis — Start with regular PC Engine games before tackling SuperGrafx titles

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

geargrafx-2 + filesystem

Export debug data and memory dumps for documentation

Dump the VDC sprite table and tile data to files for analysis.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
pause/resume/step	none / step_count?	Control emulator execution
read_memory	address: int, size: int	Read emulator memory at any address
set_breakpoint	address: int	Set a CPU breakpoint
disassemble	address: int, count: int	Disassemble HuC6280 instructions
get_hardware_status	none	Get VDC, VCE, and PSG register states

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: N/A — fully local
Tokens pro Aufruf: 100–500 tokens per debug command
Kosten in €: Free and open source (MIT license)
Tipp: Use targeted reads instead of full memory dumps.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: N/A

Datenabfluss: Fully local — no network calls

Fehlerbehebung

Häufige Fehler und Lösungen

MCP server not responding

Ensure Geargrafx was built with MCP support. Check the default port is available.

Prüfen: Test the HTTP endpoint

CD-ROM game won't load

Verify CUE file references correct BIN paths. Try converting to CHD format.

Prüfen: Check CUE file contents match actual BIN filenames

SuperGrafx ROM crashes

Only a handful of SuperGrafx games exist. Verify the ROM is actually an SGX title, not a regular PCE ROM.

Prüfen: Check ROM header

Alternativen

Geargrafx vs. andere

Alternative	Wann stattdessen	Kompromiss
Gearboy	You want to debug Game Boy ROMs instead of PC Engine	Different console, same MCP-enabled emulator approach

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen