Geargrafx MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

geargrafx-2.replay ▶ prêt

0/0

Installer

Choisissez votre 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"
      ]
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

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

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

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : Geargrafx

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

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

Quand l'utiliser : You're developing or analyzing a PC Engine ROM and need to debug runtime behavior.

Prérequis

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

Déroulement

Connect and inspect

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

→ CPU registers and disassembled instructions
Analyze sprite system

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

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

Résultat : Understanding of ROM execution and VDC hardware state for debugging.

Pièges

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

Combiner avec : filesystem

Learn PC Engine hardware architecture interactively

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

Quand l'utiliser : You want to understand the HuC6280 CPU, VDC graphics, and PSG audio systems.

Prérequis

Geargrafx with MCP server — Build from source

Déroulement

Explore the VDC

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

→ Annotated explanation of VDC register writes and their effects

Résultat : Hands-on understanding of PC Engine hardware internals.

Pièges

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

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

geargrafx-2 + filesystem

Export debug data and memory dumps for documentation

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

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
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

Coût et limites

Coût d'exécution

Quota d'API: N/A — fully local
Tokens par appel: 100–500 tokens per debug command
Monétaire: Free and open source (MIT license)
Astuce: Use targeted reads instead of full memory dumps.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : N/A

Sortie de données : Fully local — no network calls

Dépannage

Erreurs courantes et correctifs

MCP server not responding

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

Vérifier : Test the HTTP endpoint

CD-ROM game won't load

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

Vérifier : 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.

Vérifier : Check ROM header

Alternatives

Geargrafx vs autres

Alternative	Quand l'utiliser	Compromis
Gearboy	You want to debug Game Boy ROMs instead of PC Engine	Different console, same MCP-enabled emulator approach

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills