roblox-devforum-mcp
Related Servers
Alternatives to roblox-devforum-mcp
No user-submitted related servers found.
Related Servers
- -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.-
- AlicenseAqualityCmaintenanceGives AI assistants sourced, up-to-date Roblox game-development knowledge: engine changes, pitfalls and libraries, each linked to DevForum, Creator Docs or GitHub. Free edition: 50 logics. Full hosted edition (600+): brickwise.dev62MIT
- AlicenseNot gradedqualityDmaintenanceHelps ground AI agents in reality by fact-checking responses against official documentation and reading project files to prevent hallucinations during coding sessions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and edit Roblox Studio places by inspecting, generating terrain, geometry, and code, with validation and iteration.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to inspect, create, edit, debug, and playtest projects inside the Roblox editor via 29 lean tools, with push-based SSE transport, editor-safe script edits, and batched undoable writes.351,036 npm14MIT
- AlicenseNot gradedqualityCmaintenanceBridges coding agents with Roblox Studio, enabling inspection, generation, editing, and validation of Roblox places through natural language.MIT
TDQS
Scored across 11 tools
Most tools target clearly distinct intents: official docs vs. DevForum search vs. bug reports vs. thread reading vs. API lookup vs. recap browsing. There are some overlaps — search_bugs is a constrained form of search_devforum, get_whats_new overlaps with get_weekly_recap and list_recent, and check_api_health overlaps with get_engine_api — but the descriptions make the intended boundaries fairly clear.
All tool names use snake_case and follow a predictable verb-first pattern: search_*, list_*, get_*, and check_*. The naming is consistent throughout and each name maps cleanly to a resource or action.
Eleven tools is well-scoped for a Roblox documentation/community/API research server. Each tool appears to earn its place, covering search, browsing, thread retrieval, API verification, and release tracking without excessive surface area.
The surface covers the apparent domain comprehensively: official docs search/read, DevForum category discovery, full-text and bug-specific search, thread and reply retrieval, recent browsing, API existence/signature checks, and weekly recap/what's-new history. No obvious lifecycle gap or dead end is apparent.