tmodloader-mcp
Related Servers
Alternatives to tmodloader-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables controlling a real Minecraft Bedrock client by injecting input and reading frames through the launcher's agent socket, including launching, stopping, screenshotting, sending chat, and managing multiple bot instances.2-
- AlicenseAqualityBmaintenanceEnables AI assistants to interact with running games in real time — introspecting game state, simulating keyboard and mouse input to actually play, capturing screenshots, executing Lua code, hot-reloading files, and receiving push notifications when state changes.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables an agent to drive a running Unreal Engine game via UE4SS by reading/writing UObject properties and calling UFunction, with verdicts that verify whether the requested state change actually happened.MIT
- AlicenseNot gradedqualityBmaintenanceProvides external AI agents with reliable, observable tools to inspect, navigate, and act in a Minecraft world, enabling autonomous playthroughs such as beating the game.MIT
- FlicenseAqualityCmaintenanceEnables an agent to drive a real Ragnarok Online client session against a local rAthena server, allowing it to log in, walk, talk to NPCs, and fight in order to test server content end to end.17-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and streamers to monitor and control Oxygen Not Included gameplay through MCP, including world editing, colony alerts, building orders, navigation, dupe management, and game speed control.MIT
TDQS
Scored across 24 tools
Each tool has a clearly distinct purpose, even those sharing a domain like logging (log_files lists, logs tails, log_since increments, log_watch waits). The descriptions are exceptionally detailed, leaving no ambiguity about which tool to select.
Naming is inconsistent: some tools use verb_noun with underscores (log_watch, read_capture, prune_captures), others are single verbs (launch, join, stop), and some are plain nouns (captures, commands, status). There is no uniform convention.
24 tools is on the high side but justifiable for a complex development workflow covering building, launching, monitoring, capturing, logging, and snapshot management. It borders the heavy range but each tool serves a distinct function.
The tool surface covers the full mod development lifecycle: build, launch, observe, capture, restore, and log analysis. Minor gaps exist (e.g., no direct world editing or mod config tools) but core workflows are well-supported.