Skip to main content
Glama
nschneir

pet-tools-mcp

by nschneir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pet-tools-mcp

No user-submitted related servers found.

    Related Servers

    • C64 Debug MCP

      henols
      A
      license
      A
      quality
      D
      maintenance
      Enables AI-powered control and debugging of Commodore 64 programs via the VICE emulator, supporting memory operations, breakpoints, register access, and program loading.
      18
      26 npm
      MIT

    • MSXLab

      Andrey-Dymov
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control an MSX emulator for debugging and reverse-engineering, including memory and code inspection, execution control, and saving annotations via MCP.
      -

    • C64 Bridge

      chrisgleissner
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI clients control and program a Commodore 64, including running programs, reading/writing memory, rendering graphics, playing sound, and switching between C64 Ultimate hardware and VICE emulation.
      211 npm
      37
      GPL 2.0

    • 80mcp

      avwohl
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run CP/M, MP/M, and DOS packages on Z80/x86 emulators, inspect byte-exact results and files, and debug the emulators themselves over the Model Context Protocol.
      7
      GPL 3.0

    • CoCo 3 MCP Bridge

      dbowlin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI assistant to drive a Color Computer 3 emulated in MAME, including entering BASIC commands, mounting disk images, capturing screen snapshots, and peeking/poking memory.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 44 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose with detailed descriptions. Tools like pet_session_start and pet_session_ensure are differentiated by idempotency, and pet_key_type vs pet_key_hold are clearly separate. There is no ambiguity or overlap.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'pet_' + domain + verb_noun (e.g., pet_break_add, pet_mem_read, pet_disk_ls). The naming is uniform and predictable across all 44 tools.

    Tool Count3/5

    44 tools is on the high side, but the domain of PET emulation and debugging is complex, justifying many specific operations. However, it exceeds the 25+ threshold indicated in calibration, making it borderline.

    Completeness5/5

    The tool surface covers the full lifecycle: session management, memory/register access, break/watchpoints, stepping, waiting, disk operations, ROM analysis, and testing. Only a minor gap (no watchpoint list) is present, but overall very comprehensive.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources