sims4-tc-mcp
Related Servers
Alternatives to sims4-tc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides MCP tools to validate ROMs, extract and pack N64 game assets, export code/headers, import modded assets, and render audio sequences via HarbourMasters/Torch.12MIT
- AlicenseBqualityBmaintenanceLets MCP clients browse vanilla data, add or override table rows, edit asset properties, check Blueprint symbols, and validate mods before packaging.21MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to explore a local War Selection installation by reading mod code, game JSON data, logs, and Lua API indexes, while also linting mods, parsing Lua log errors, diffing mod and game versions, generating scaffolds, and watching logs in real time.26MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP toolkit that gives coding agents bounded, provenance-backed evidence about Minecraft projects, including declared project facts, version-aware mapping and source references, and classified build or runtime diagnostics. It also exposes opt-in tools for permitted Gradle tasks, bounded client launches, and configured external providers, with modular skills for Java, client, server, Mixin debugging, and anti-cheat compatibility work.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to locate game save files, identify their engines, compute unlock plans for gallery/recollection flags, diff saves, and safely dry-run, apply, verify, or roll back reversible byte patches with automatic backups.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to research game mods by searching documentation and definitions, inspecting dependencies and playsets, validating saved files with structural and Tiger checks, and preparing or editing mod content with preview and write controls. It also supports starting or previewing the game through a local stdio connection.8 npmGPL 3.0
TDQS
Scored across 17 tools
Most tools map to a unique resource+action (package inspect/extract/build, tuning search/read, STBL creation, script build, live bridge, exception analysis). A few boundaries blur: `build_package` already handles .stbl.json while `create_stbl_dictionary` also writes STBL resources, and `compile_tuning_with_simdata` overlaps conceptually with package building and `query_tdesc_schema`'s starter XML. `hash_fnv` also partially duplicates the hashing inside `create_stbl_dictionary`, but descriptions make the intended split workable.
Nearly all tools follow a snake_case verb_noun pattern (inspect_package, build_package, search_vanilla_tuning, validate_and_build_ts4script). The main deviation is `bridge_send_command`, which uses noun_verb ordering, plus the short `hash_fnv` which names the algorithm rather than a clear object. Still highly readable and predictable overall.
At 17 tools this is on the heavy side, but the surface spans genuinely different workflows (package I/O, tuning index/search, STBL, SimData compile, Python API exploration, live bridge, crash triage). Each tool appears to earn its place rather than being a near-duplicate, though a few could conceivably be folded together.
The modding lifecycle is well covered: index building, vanilla tuning discovery, schema lookup, XML validation, SimData compile, STBL creation, package build/extract, script bundling, and crash analysis. Gaps remain around mutating existing packages (only inspect/extract, no add/remove/replace resource), and `bridge_send_command` has no companion for reading bridge responses, which limits round-trip debugging.