roblox-logics-mcp
Related Servers
Alternatives to roblox-logics-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceBridges AI assistants to Roblox Studio with 51 tools for exploring, editing, and automating game development, all locally via HTTP polling.800 npm6MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI agents to intelligently search and retrieve Roblox documentation through semantic search and vector embeddings, providing natural language access to complete Roblox Creator Documentation.-
- AlicenseAqualityAmaintenanceGive your AI coding agent the Roblox DevForum and official creator docs — check if a bug is already known, read the accepted answer, and verify APIs before writing Luau.11496 npm4MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants like Claude and Gemini to Roblox Studio, enabling game structure exploration, script editing, UI generation, style extraction, and bulk changes locally and safely.7 npmMIT
- AlicenseBqualityAmaintenanceRoBridge is a free, open-source local MCP server that lets AI agents drive Roblox Studio—DataModel, scripts, terrain, lighting, UI, and playtests—with 24 free tools and a local dashboard.242MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to explore Roblox Studio game structure, read and edit scripts, and perform bulk changes locally and safely.MIT
TDQS
Scored across 6 tools
Most tools are cleanly separated: get_logic fetches, search_code does literal code matching, and find_related traverses links. The only friction is the trio list_categories / list_logics / search_logics, which all touch browsing, but the descriptions explicitly state when to use each, largely resolving the overlap.
Every tool is snake_case with a predictable verb_noun shape (list_categories, search_logics, get_logic, search_code, find_related). No camelCase or vague single-word names, so the pattern is fully consistent.
Six tools is well-scoped for a read-only knowledge base: browse, search, code-search, fetch, and relate. Each tool earns its place with no redundant or filler operations.
The surface covers the full read lifecycle: discover categories, search concepts, search code, fetch full detail, and explore related entries. Minor gaps like tag-based filtering or citation export exist, but core workflows have no dead ends.