Gearlynx
github.com
What it is
Gearlynx is a free, open-source Atari Lynx emulator and debugger written in C++. It supports the commercial Lynx catalog and most homebrew and demo software, with Lynx I or Lynx II emulation selectable. Supported ROM formats include lnx, lyx, o, bin, and zip, including compressed and homebrew files. Gaming tools include save states with previews, rewind, run-ahead to reduce input latency, audio emulation, VGM recording, and EEPROM and NVRAM save files. ComLynx multiplayer connects up to eight emulator instances on one computer. The debugger provides disassembly, CPU and memory breakpoints, debug symbols, memory editing and search, hardware register views, and cartridge and video inspectors. An embedded MCP server supports AI-assisted debugging, with execution controls, memory inspection, breakpoints, screenshots, and rewind over STDIO or HTTP. Standalone builds are listed for Windows, Linux, BSD, and macOS; libretro includes Android and iOS. Gearlynx requires a BIOS. Concurrent HTTP clients control the same emulator instance and may interfere with one another.
Spec sheet
- Product
- Gearlynx is an open-source Atari Lynx emulator and debugger written in C++.Read 29 Sep 2026 · github.com
- Intended users
- The project describes its MCP server as supporting Atari Lynx game development, ROM hacking, reverse engineering, and debugging.Read 29 Sep 2026 · github.com
- Security
- For HTTP mode, authentication is optional on loopback binds and required for wildcard or other non-loopback binds; the server also checks Host and browser Origin against the connection address.Read 29 Sep 2026 · github.com
- Support
- The project asks users to report bugs or request features by opening a GitHub issue.Read 29 Sep 2026 · github.com
- License
- The repository states that Gearlynx is licensed under GNU GPL version 3.0.Read 29 Sep 2026 · github.com
- AI integration
- Its embedded MCP server supports AI-assisted debugging with GitHub Copilot, Claude, Codex, and similar AI agents.Read 29 Sep 2026 · github.com
- BIOS requirement
- Gearlynx requires a BIOS to work; the README recommends the original BIOS identified by its MD5 hash.Read 29 Sep 2026 · github.com
- Connections
- The MCP server supports STDIO and HTTP transports, and the project documents setup with VS Code, Claude Desktop, and Claude Code.Read 29 Sep 2026 · github.com
- Debugger
- The debugger includes a disassembler, CPU and memory breakpoints, debug symbols, memory tools, and Suzy and Mikey hardware inspectors.Read 29 Sep 2026 · github.com
- Emulation
- It supports the commercial Atari Lynx catalog and most homebrew games and demos, with selectable Lynx I or Lynx II emulation.Read 29 Sep 2026 · github.com
- Game features
- Features include save states, rewind, run-ahead, audio emulation, VGM recording, and ComLynx multiplayer for up to eight emulator instances on one machine.Read 29 Sep 2026 · github.com
- MCP concurrency limit
- Connected HTTP clients control the same emulator instance, so concurrent debugging workflows can interfere with one another.Read 28 Sep 2026 · github.com
- MCP security
- MCP HTTP mode requires a token for wildcard or other non-loopback binds and checks Host and browser Origin against the connection address.Read 28 Sep 2026 · github.com
- MCP tools
- The MCP server provides execution control, memory inspection, breakpoints, disassembly, hardware status, screenshots, and rewind.Read 29 Sep 2026 · github.com
- Mobile platforms
- The libretro build lists Android and iOS among its supported platforms.Read 29 Sep 2026 · github.com
- Multiplayer
- ComLynx multiplayer supports up to eight emulator instances on the same computer.Read 28 Sep 2026 · github.com
- Other integrations
- A separate VS Code source-level debugger connects to Gearlynx through its debug-monitor protocol.Read 28 Sep 2026 · github.com
- ROM support
- It supports compressed and homebrew ROM formats including lnx, lyx, o, bin, and zip.Read 28 Sep 2026 · github.com
- Save and latency features
- Features include save states with previews, rewind, run-ahead to reduce input latency, and EEPROM and NVRAM save files.Read 28 Sep 2026 · github.com
- Supported systems
- Standalone downloads are provided for Windows, macOS, and Linux, with BSD and RetroArch also listed as supported platforms.Read 29 Sep 2026 · github.com
Strong points and limits
Strong points
- Supports Lynx I and Lynx II emulation
- Save states, rewind, and run-ahead are included
- ComLynx connects up to eight instances on one computer
- Debugger includes memory tools and hardware inspectors
Limits
- A BIOS is required
- Concurrent HTTP clients share one emulator instance
- Netplay is not supported
Who it suits
Gearlynx suits Atari Lynx players and developers working on game development, ROM hacking, reverse engineering, or debugging. Its debugger and MCP tools provide inspection and control features for those workflows.
Gearlynx in depth
Read the full write-up
Overview
Gearlynx is an Atari Lynx emulator with a built-in debugger, suited to players who also want to examine games and developers working on Lynx software. Its emulation and debugging tools are unusually broad for a free project, though it will not run without a BIOS.
Key features
Emulation and play
Gearlynx covers the commercial Lynx catalog and most homebrew and demo software, with separate Lynx I and Lynx II modes. It accepts lnx, lyx, o, bin, and zip ROMs, including compressed files. Save states with previews, rewind, and run-ahead make it useful for play as well as development; run-ahead aims to reduce input latency. EEPROM and NVRAM saves, audio emulation, VGM recording, controller support, and video filters round out the player-facing features.
ComLynx link-cable emulation supports up to eight emulator instances on one computer. That enables local multiplayer and link testing, but it is not online netplay. A BIOS is mandatory; the project recommends the original BIOS, MD5 fcd403db69f54290b51035d82f835e7b.
Debugging and AI workflows
The debugger combines a disassembler, CPU and memory breakpoints, debug symbols, a memory editor and search, hardware-register viewers, and cartridge and video inspectors. A separate VS Code source-level debugger connects through Gearlynx’s debug-monitor protocol. Together these tools make Gearlynx a particularly capable choice for ROM development, reverse engineering, and debugging—not merely a way to launch games.
An embedded MCP server exposes execution control, memory inspection, breakpoints, disassembly, hardware status, screenshots, and rewind to AI agents such as GitHub Copilot, Claude, and Codex. It supports STDIO and HTTP, with documented setup for VS Code, Claude Desktop, and Claude Code. HTTP authentication is optional on loopback, but required for wildcard or other non-loopback binds; Host and browser Origin checks add safeguards. All connected HTTP clients control the same emulator instance, so simultaneous debugging workflows can interfere. That shared state makes coordinated or single-client use a better fit than parallel agent sessions.
Pricing
Gearlynx is free, with no trial or paid plan described. It is open source under the GNU General Public License version 3.0, so there is no subscription tier to weigh against the debugging or emulation features. The practical cost is obtaining a compatible BIOS before use.
Platforms
Standalone builds are available for Windows, Linux, BSD, and macOS. The libretro core adds platforms including Android, iOS, and Emscripten, with webOS and other libretro systems also supported. Android and iOS support therefore comes through the libretro build rather than the listed standalone releases.
Who it's for
Choose Gearlynx if you want Lynx I and II emulation alongside detailed inspection tools, or if you develop, hack, or reverse-engineer Lynx ROMs. Local ComLynx support and latency-reduction features also suit players who want more than basic playback. Look elsewhere if you need netplay, cannot provide a BIOS, or need multiple HTTP-connected agents to debug independently against separate emulator instances.
Pros and cons
Pro: The debugger’s breakpoints, memory tools, symbols, and hardware inspectors support substantial investigation without relying on a play-only emulator.
Pro: ComLynx links as many as eight instances on one machine, a useful option for local multiplayer and link testing.
Pro: MCP and a separate VS Code debugger extend the project into AI-assisted and source-level workflows.
Con: A BIOS is required, so the emulator is not ready to run on its own.
Con: ComLynx is local only; it does not provide netplay.
Con: HTTP MCP clients share one emulator instance, which can make concurrent debugging workflows conflict.
Alternatives
For a different Atari system, Virtual Jaguar is a free, open-source emulator core for users willing to run it through a libretro frontend such as RetroArch. Javatari is a free online Atari 2600 emulator; choose it when that console and browser access matter more than Lynx emulation. Atari800 is a free, GPL version 2 project for Atari 5200 and 8-bit computer emulation. BigPEmu offers a free emulator download for Windows and Linux if those listed platforms suit your setup. EMU7800 focuses on non-commercial Atari 2600 and 7800 emulation, while kat5200 covers Atari 5200 and 8-bit computers. For Atari 2600 VCS emulation, Stella is free, with voluntary donations. Teller is an open-source universal secret manager for developers, rather than an emulator.
Browse Atari Emulators for more Atari options, or compare systems through Sega Master System Emulators, Game Gear Emulators, TurboGrafx-16 Emulators, and Game Boy Emulators.
Verdict
Gearlynx is the right pick for Lynx players who want serious debugging tools, and especially for developers who can use its VS Code and MCP integrations. Its breadth comes at no software price, but the BIOS requirement is a real prerequisite, and shared HTTP state limits parallel debugging. Choose it for focused Lynx work; look elsewhere for netplay or a separate emulator session per HTTP client.
Verdict
Gearlynx combines Atari Lynx emulation with detailed debugging and AI-assisted workflows. It is free and open source, but requires a BIOS and simultaneous HTTP debugging workflows can interfere.
Where Specifiction places it
- Atari Emulators#12 of 257.5