Skip to main content
Glama
computercraft-mcp
by slashracer5

Related Servers

Alternatives to computercraft-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets an AI agent run CC:Tweaked Lua programs inside a faithful ComputerCraft emulator with no Minecraft install, reading back the terminal and every monitor as text or images. The agent can also type keys, tap monitors, advance the clock, change the world around the computer (players, turtles, trains, reactors) and run its own test files until the code works.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a local Minecraft mod bridge as 50+ Model Context Protocol tools, letting AI agents observe the running game (blocks, entities, players, chat, screenshots) and act in it — moving, mining, building, fighting, managing inventory, and running commands — on Fabric and NeoForge for 1.21.1 and later. Connections stay loopback-only with bearer authentication and per-capability gates so clients like Claude Desktop can play or administer a world under controlled access.
      23
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to drive a running Roblox Studio in real time over a single WebSocket, executing whole Luau programs, installing in-engine controllers, hot-patching scripts during live playtests, and receiving errors, assertions and other events as pushes. It also reaches Roblox Open Cloud for the open place and answers visual questions via a vision sidecar, exposing all of this through nine MCP tools.
      9
      2
      MIT

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a distinct action/resource (exec Lua vs shell command, call vs batch, push vs pull), and descriptions clarify the boundaries. Two pairs overlap somewhat: cc_peripherals vs cc_network (both enumerate peripherals, one direct-only, one networked) and cc_write vs cc_push (both write remote files, inline vs local upload). These are resolvable from descriptions but still invite occasional misselection.

    Naming Consistency4/5

    All names use a uniform lowercase snake_case with the `cc_` prefix, which is highly predictable. Minor deviation is that some are action verbs (exec, ping, cancel, read) while others are resource nouns (computers, peripherals, network, log), though this remains readable and consistent in style.

    Tool Count4/5

    15 tools sits at the upper edge of the well-scoped range for a ComputerCraft relay bridge. Each tool covers a genuinely distinct capability (discovery, execution, file transfer, peripheral I/O, logs, cancellation), though the file-transfer and peripheral-inventory tools could arguably be consolidated.

    Completeness4/5

    The surface covers discovery, code/shell execution, file read/write plus local push/pull, peripheral inspection and batch calling, logging, and cancellation — a solid lifecycle for the domain. Gaps remain: no file delete/move or directory creation, and no explicit reboot/shutdown/reset-computer operation beyond cc_exec's reset flag.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues