Geargrafx MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

geargrafx-2.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/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"
      ]
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: Geargrafx

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

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

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

Pré-requisitos

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

Fluxo

Connect and inspect

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

→ CPU registers and disassembled instructions
Analyze sprite system

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

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

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

Armadilhas

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

Combine com: filesystem

Learn PC Engine hardware architecture interactively

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

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

Pré-requisitos

Geargrafx with MCP server — Build from source

Fluxo

Explore the VDC

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

→ Annotated explanation of VDC register writes and their effects

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

Armadilhas

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

Combinações

Combine com outros MCPs para 10× de alavancagem

geargrafx-2 + filesystem

Export debug data and memory dumps for documentation

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

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar
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

Custo e limites

O que custa rodar

Cota de API: N/A — fully local
Tokens por chamada: 100–500 tokens per debug command
Monetário: Free and open source (MIT license)
Dica: Use targeted reads instead of full memory dumps.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: N/A

Saída de dados: Fully local — no network calls

Solução de problemas

Erros comuns e correções

MCP server not responding

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

Verificar: Test the HTTP endpoint

CD-ROM game won't load

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

Verificar: 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.

Verificar: Check ROM header

Alternativas

Geargrafx vs. outros

Alternativa	Quando usar	Troca
Gearboy	You want to debug Game Boy ROMs instead of PC Engine	Different console, same MCP-enabled emulator approach

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills